|
YOUR FEEDBACK
Did you read today's front page stories & breaking news?
SYS-CON.TV
|
TOP THREE LINKS YOU MUST CLICK ON Real-World AJAX Book Preview Real-World AJAX Book Preview: AjaxWord: An Open Source Web Word Processor
Real-World AJAX Book Preview: AjaxWord: An Open Source Web Word Processor
By: Coach Wei
May. 20, 2007 10:00 AM
This content is reprinted from Real-World AJAX: Secrets of the Masters published by SYS-CON Books. To order the entire book now along with companion DVDs for the special pre-order price, click here for more information. Aimed at everyone from enterprise developers to self-taught scripters, Real-World AJAX: Secrets of the Masters is the perfect book for anyone who wants to start developing AJAX applications. AjaxWord: An Open Source Web Word Processor AjaxWord (www.ajaxword.com) is an open source Web-based word processor. It closely mimics Microsoft Word in both look-and-feel and functionality. The application was initially written between 1997 and 1999 using JavaScript/DHTML on the client side with ASP on the server side. It was released on the Web in 2000. In 2005, the application's server-side logic was migrated to Java and released as open source code. On the client side, the application looks and feels like a typical desktop application, e.g., Microsoft Word. The design features the kind of rich graphical user interface that Microsoft Word users are familiar with, such as hierarchical menus, toolbars, wizards, file dialogs, and a multiple document interface (MDI).
On the server side, the application is a typical Java-based Web application. It features:
Document Templates and "New File" Wizard
In many ways, AjaxWord exhibits the characteristics of AJAX applications:
AjaxWord is a distributed application that has a client-side component and server-side component: the AjaxWord client and the AjaxWord server. The AjaxWord client is written using JavaScript and HTML. It leverages an AJAX engine that contains a DHTML user interface toolkit and a way of doing asynchronous communications. The AjaxWord client also contains the application's client-side business logic. The AjaxWord server is written as a Java Web application. It contains a Java servlet called "ControllerServlet." This servlet gets AjaxWord client requests and dispatches them to different modules for processing. The AjaxWord server handles the following requests:
Launching AjaxWord Figure 15.7 shows how AjaxWord handles this. When the user launches the application, AjaxWord shows a loading page with a progress bar. In the background, it sends a request to the server to download the JavaScript files of the AJAX engine. When a file is downloaded, the progress bar is updated. After the AJAX engine finishes downloading, the application user interface is downloaded and displayed. In the meantime, requests are sent to the server in the background to download the application logic. When the application user interface is rendered, the application has been downloaded and is ready for user interaction.
Running AjaxWord
If the event requires server-side resources, the application client-side logic will call the AJAX engine to send a request to the server in the background without freezing the user interface. The request will go to the server-side "ControllerServlet," which can route the request to different service modules for processing. The processing result will be sent back to the client as part of the response. The AJAX engine will get the response and return it to the application logic. The client logic will then process the response and update the user interface. While the server request is being processed, the user interface is still "live" and the user can still interact with the application. This "asynchronous" behavior is another reason why AJAX is attractive to developers and users. Exiting AjaxWord
Most Web applications don't require any special handling on the browser side to exit. If a session is inactive for a certain amount of time, the application is considered to have hit a "session time-out" and the server will terminate it automatically. Since most Web applications don't keep state on the client side, the client-side exit isn't a concern. The situation can be different for AJAX applications. AJAX applications tend to keep state on the client side and so the client-side exit has to be handled. AjaxWord is a good example. When the user is closing the browser window, there may be unsaved documents on the client side. If the exit event isn't handled, the unsaved document will be lost. When a user issues an exit command (by clicking the "close" button on the browser window to close the browser), the event is captured by AjaxWord's client logic. The client logic first determines whether there are any opened documents to be saved. If so, it will call the AJAX engine to save these documents to the server, then it will display a confirmation dialog asking the user to confirm the exit. If the user clicks "cancel," the exit event is ignored and the session will continue. If the user clicks "ok," the session will terminate and the browser window will be closed. This content is reprinted from Real-World AJAX: Secrets of the Masters published by SYS-CON Books. To order the entire book now along with companion DVDs, click here to order. LATEST AJAXWORLD RIA STORIES
SUBSCRIBE TO THE WORLD'S MOST POWERFUL NEWSLETTERS SUBSCRIBE TO OUR RSS FEEDS & GET YOUR SYS-CON NEWS LIVE!
|
SYS-CON FEATURED WHITEPAPERS MOST READ THIS WEEK |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||