Thesis full text PDF - Politecnico di Milano

More documents

Recommendations

Info

developers as a “serious programming language,” despite the fact that, in reality, it’s a fullyfeatured, dynamic language capable of supporting object-oriented programming methodologies.The misperception of JavaScript as a “toy language” is now changing rapidly as AJAXdevelopment techniques expand the power and functionality of browser based applications. As aresult of the advent of AJAX, JavaScript now seems to be undergoing something of arenaissance, and the explosive growth in the number of JavaScript toolkits and libraries availablefor AJAX development is proof of the fact.Server-Side ScriptingThe server is still required to perform tasks like data persistence and input validation. However,in some Ajax architectures, it no longer performs any duty of display or application logic, leavingthose things for the browser script to handle.Event Model (“DHTML”)The event model allows JavaScript to respond to events such as mouse clicks. This is the key tomake interactive a conversation between the user and the web site, within the browser.Web RemotingWeb Remoting is the ability of JavaScript to talk directly with the server, no page refresh isrequired. XMLHttpRequest dominates most of the headlines, but there are actually several viableremoting technologies.2.2.4. Ajax versus the Traditional approachWith Ajax, instead of having to send everything to the server in a single, huge mass, then waitfor the server to send back a new page for rendering, web developers can communicate with theserver in smaller chunks, and selectively update specific areas of the page based on the server’sresponses to those requests. This is where the word asynchronous in the AJAX acronymoriginated. It’s probably easiest to understand the idea of an asynchronous system byconsidering its opposite, a synchronous system. In a synchronous system, everything occurs inorder. If a car race was a synchronous system, it would be a very dull affair. The car that startedfirst on the grid would be the first across the finish line, followed by the car that started second,and so on. There would be no overtaking, and if a car broke down, the traffic behind would beforced to stop and wait while the mechanics made their repairs.Traditional web apps use a synchronous system: you must wait for the server to send you thefirst page of a system before you can request the second page, as shown in Figure 1.1.14
Figure 2.3 – Traditional interactionAn asynchronous car race would be a lot more exciting. The car in pole position could beovertaken on the first corner, and the car that starts from the back of the grid could weave itsway through the field and cross the finish line in third place. The HTTP requests from the browserin an AJAX application work in exactly this way. It’s this ability to make lots of small requests tothe server on a needs-basis that makes AJAX development so cool. Figure 2.4 shows an AJAXapplication making asynchronous requests to a web server. The end result is an application thatfeels much more responsive, as users spend significantly less time waiting for requests toprocess, and don’t have to wait for an entire new web page to come across the wire, and berendered by their browsers, before they can view the results.15
Page 1 and 2: POLITECNICO DI MILANOFacoltà di In
Page 4 and 5: INDEX1. Introduction and problem pr
Page 6 and 7: 1. Introduction and problem present
Page 8 and 9: 2.2. Ajax Web Applications2.2.1. Wh
Page 11 and 12: development, nor as easy as old-sch
Page 13: AJAX application development possib
Page 19 and 20: frameworks. They allow you to map J
Page 21 and 22: Figure 3.2 - Draw2D shapes exampleT
Page 23 and 24: Possibility to use dynamic windows
Page 25 and 26: The PropertyWindow is maybe the mos
Page 27 and 28: Win 98 Win 2000 Win XP Win Vista Ma
Page 29 and 30: YAHOO.example.container.panel2.setB
Page 31 and 32: Tab One ContentTab Two ContentTab T
Page 33 and 34: We offer an online design tool that
Page 35 and 36: The Struts ControllerAlthough Strut
Page 37 and 38: many of the connections between the
Page 39 and 40: Table 1. Primitives of the MVC-Webf
Page 41 and 42: a JSP page can contain more than on
Page 43 and 44: Form property typeParameter name Pa
Page 45 and 46: 5. MVC-WebFlow Ajax tool5.1. Object
Page 47 and 48: 5.2. Business requirements and func
Page 49 and 50: the view needs the possibility for
Page 51 and 52: The state diagram in Figure shows a
Page 53 and 54: of the unit but also add and modify
Page 55 and 56: 5.5. Interface requirementsThe grap
Page 57 and 58: We can see in depth all the technol
Page 59 and 60: 5.7. Data schema designThe data sch
Page 61 and 62: Figure 5.15 - Logical view of the a
Page 63 and 64: ApplicationFiles packageThis packag
Page 65 and 66:
its navigation flow. At the top the
Page 67 and 68:
The developer has to define each el
Page 69 and 70:
6. Conclusions and future developme
Page 71 and 72:
7. Appendix A: Ajax open source and
Page 73 and 74:
Avoid traditional approaches proble
Page 75 and 76:
e updated as the result of one Ajax
Page 77 and 78:
complete JavaScript parser which op
Page 79 and 80:
http://www.zimbra.com7.2. JavaScrip
Page 81 and 82:
Build for reliability Stable commun
Page 83 and 84:
Powered by BindowsoooooStrength of
Page 85 and 86:
Possibility to use images in the di
Page 87 and 88:
An SVG DOM implementation A set of
Page 89 and 90:
It’s fast, reliable, more stable
Page 91 and 92:
• ProxyingProxy requests to remot
Page 93 and 94:
WindowsEventAppender: send log mess
Page 95 and 96:
XML form binding for easily copying
Page 97:
24. Guida JavaScript di base - http
show all

Thesis full text PDF - Politecnico di Milano

Create successful ePaper yourself

Delete template?

Save as template?