Tài liệu ColdFusion MX Components, Web Services, and Flash Integration

By now, you probably get the basic idea that, at its most basic level, a component is like a
container for related functions, and invoking component functions is much like invoking local
functions except that you must also specify the name of the component that contains the
function.
So . big deal? You bet! Even the most basic use of the simplest components changes your
approach to ColdFusion development, because you’re now completely separating logic from
presentation; you’re exposing logic as a set of simple, yet formal function calls available to
any part of your application (even remote applications, as you see in Chapters 25 and 26);
and you’re encapsulating the functions related to a single entity into a single component.
And if you think components are just a substitute for a bunch of CFINCLUDEs, keep reading
Separating logic from presentation
The need to separate logic from presentation is more important now than it has ever been for
a number of reasons, as outlined in the following list:
✦ The ever-increasing array of handheld devices and their widely varying display formats.
✦ The renewed interest in syndicated content that must form-fit various Web layouts.
✦ The trend away from delivering plain-text streams and HTML and toward delivering
generalized XML, XHTML, WML, and other “pivot” formats (i.e, formats that acts as
intermediate steps in a data conversion process) that are further processed into finished
content on target devices.
✦ The desire to easily expand very large corporate applications while minimizing new
errors or anomalies into the software