Senin, 24 Oktober 2011
One major rationale behind "effective separation" is the need for maximum flexibility in the code and resources dedicated to the presentation logic.[2] Client demands, changing customer preferences and desire to present a "fresh face" for pre-existing content often result in the need to dramatically modify the public appearance of web content while disrupting the underlying infrastructure as little as possible.
The distinction between "presentation" (front end) and "business logic" (infrastructure) is usually an important one, because:
- the presentation source code language may differ from other code assets;
- the production process for the application may require the work to be done at separate times and locations;
- different workers have different skill sets, and presentation skills do not always coincide with skills for coding business logic;
- code assets are easier to maintain and more readable when disparate components are kept separate and loosely coupled;[2
Langganan:
Posting Komentar (Atom)
0 komentar:
Posting Komentar