In this context, ???scale??? refers to added functionality in
the application, not simultaneous request-handling capability (although it is quite possible
that is in play, too). If things do not work as smoothly, or if breakages result in too much lost,
or if perceived speed is diminished, then the approach didn??™t scale well.
The classic model will continue to serve us well for some time to come in the realm of
web sites, but in the realm of webapps, the realm you are likely interested in if you are reading
this book, its demise is at hand, and its slayer is the hero of our tale: Ajax!
Enter Ajax
Ajax (see Figure 1-6 . . . now you??™ll always know what code and architectures would look like
personified as a plucky super hero!) came to life, so to speak, at the hands of one Jesse James
Garrett of Adaptive Path (www.adaptivepath.com). I am fighting my natural urge to make the
obvious outlaw jokes here! Mr. Garrett wrote an essay in February 2005 (you can see it here:
www.adaptivepath.com/publications/essays/archives/000385.php) in which he coined the
term Ajax.
Figure 1-6. Ajax to the rescue!
In Figures 1-7 through 1-9, you can see some examples of Ajax-enabled applications.
Pages:
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68