Types of AJAX Toolkit and Framework Solutions of Today • Clients-side JavaScript Libraries (ex: Dojo toolkit) • RMI-like remoting via proxy (ex: DWR) • AJAX-enabled JSF components (ex: NetBeans VWP) • Dynamic Faces (DynaFaces) • Wrapper (ex: jMaki) • Java to JavaScript/HTML translator (ex: GWT) • Port lets and Ajax (ex: JSR 168 portlets) • MVC server-side scripting (ex: Phobos) • Web Application Frameworks with AJAX extension (ex: Shale or Echo2 or Wicket) Client Side Client Side JavaScript Libraries JavaScript Libraries 4 Client Side JavaScript Libraries Java Script, DOM Utilities HTMP, JSP Pages, JavaScript Event Handlers UI Widgets & Components Remoting Abstraction Layer XMLHttpRequest iF ram e 5 Characteristics of Client Side JavaScript Libraries • Server side technology agnostic > The server side technology can be Java EE, . Net, PHP, Ruby on Rails, etc. • You can use them in combination in a single app > You might want to use widgets and JavaScript utilities from multiple sources 6 Technical Reasons for using Client- side JavaScript Libraries • Handles remote asynch. communication (remoting) > Hides low-level XMLHttpRequest operation • Handles browser incompatibilities > No need to clutter your code with if/else’s • Handles graceful degradation > Uses IFrame if the browser does not support XMLHttpRequest • Provides page navigation hooks over Ajax > Back and forward buttons > Book marking 7 Technical Reasons for using Client- side JavaScript Libraries • Provides ready-to-use widgets > Tree, Calendar, Textfield, Button, Split panes, Fisheye, etc. • Provides easy-to-use DOM utility > Easier to use than original DOM APIs • Provides useful JavaScript utilities > Example: Table management, Timer, etc • Provides error handling hook > Easier to add error handler • Provides more flexible event handling > DOM node based, Function call based, AOP style…
Download Ajax Frameworks and Toolkits.Pdf
0 comments:
Post a Comment