Part of the problem with this approach is that it doesn??™t provide a clean separation of
the presentation and the business logic. The server that manages the data also generates
the UI, and the presentation layer (e.g., the browser) dumbly inserts what the server dispatches
to it. For example, the server could generate HTML markup for a table that
displays data for the company selected by the user. Of course, the server could simply
send the data instead of the HTML markup, but it is generally more onerous to have
JavaScript parse data and generate the HTML than it is to generate the HTML on the
server side where you can use the power of Visual Studio and C# or VB .NET??”or indeed
Java and any Java IDE.
ASP.NET AJAX follows the model in which the data is managed on the server, where it
belongs, and the presentation, after the initial rendering, is handled by the components
and controls that run within the browser. Controls and components are higher-level
abstractions that fall into two categories:
??? Components are reusable building blocks that can be created programmatically
using client-side script.
Pages:
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71