NET because it was a multilanguage, singleruntime
platform that provided great flexibility.
The .NET Framework was revolutionary because it united the client-application
experience and connected-application experience with a common runtime that ActiveX
had tried but ultimately failed to accomplish. Because the same platform was used to
write both types of applications, the result was that the user experience would be similar
across both (see Figure 1-3). Coupled with the emergence of Extensible Markup Language
(XML), a language similar to HTML but specialized for handling data instead of
presentation, web application development was finally coming of age.
CHAPTER 1 ?– INTRODUCING AJAX 5
Figure 1-3. The .NET Framework provides consistent browser, desktop, and server
application programming interfaces (APIs).
Thus, the pendulum has swung back toward the thin client/fat server approach.
Ironically, the thin client is probably fatter than the original servers because it??™s an
operating system that can support a browser that is extended to support XML (through
parsers), scripting (through interpreters), and other plug-ins, as well as Java and .
Pages:
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44