|
|
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: Some Classic Examples
What Is AJAX?
Feb. 20, 2007 10:00 AM
Digg This!
Real-World AJAX: Some Classic Examples
AJAX Chat Applications
Gabbly: Live Chat for Any Web Site Gabbly uses IFrame to display the target Web site. Then in a separate IFrame, it displays the chat window. The chat window uses an XmlHttpRequest object to communicate chat messages with the server asynchronously. Figure 1.19 shows how Gabbly works with CNN.com.
Gabbly is a great Web 2.0 application that can add significant value to various Web sites. For instance, it could let all CNN.com readers interact with each other in real-time. Such real-time interaction between random Web visitors changes the Web from a static passive medium into an interactive social environment.
AJAX IM: The AJAX Instant Messenger
AJAX IM is an AJAX instant messaging client. It has a clean rich interface with multiple windows that feels like a normal desktop application.
AJAX+PHP CSS Popup Chat
Meebo: Connecting All Popular IM Systems Twelve weeks after its launch, Meebo had 236,000 successful logins, 6,534,948 messages sent, and approximately 13,069,896 total messages carried. By the end of 2005, Meebo averaged about 250,000 logins a day.
AJAX Office Applications
AJAX Word Processors: Writely and AJAXWord
AJAXWord (http://www.AJAXword.com) is an open source word processor mimicking Microsoft Word’s look-and-feel, but written using JavaScript and DHTML. It features dedicated server-side file storage for each user, who uses a familiar file dialog to open or save files. When creating a new file, the user is prompted to select from a list of templates. Unlike other Web-based word processors, AJAXWord features a multiple windows interface (MDI) that enables a user to work on multiple documents at the same time.
AJAX Spreadsheet: NumSum
Mashups Mashup technology sounds like traditional “application integration.” Application integration developers have been assembling data from multiple sources and presenting it in one integrated application for years. The main difference between mashups and traditional application integration is where the “integration” takes place. Traditional application integration integrates data on the server side (“back-end integration”), which typically requires server-side programming skills (Java, C++, etc.) and access to enterprise server-side resources. Mashups typically do the integration at the browser layer without touching the server side at all (“front-end integration”), which only requires JavaScript and HTML coding skills, and data access is readily available from eBay, Amazon, Google, etc., via the public Internet. (http://www.programmableWeb.com/ lists close to 200 public APIs as of April 2006.) AJAX (JavaScript and DHTML) is a major reason why mashups are so popular. Without the popularity and support of AJAX, it would have been difficult, if not impossible, to “integrate” data from multiple Web sites at the browser layer. As blogs have revolutionized online publishing, mashups are revolutionizing Web development by letting anyone combine existing data from sources like eBay, Amazon, Google, Windows Live, and Yahoo in innovative ways. The greater availability of simple and lightweight APIs has made mashups relatively easy to design. They require minimal technical knowledge and, therefore, custom mashups are sometimes created by unlikely innovators, combining public data in new and creative ways. Today there are many mashups available on the Web. The http://www.programmableWeb. com/ site has tracked over 600 mashups as of April 2006, though a lot of them are simply “cute” and have no real value. The interesting trend to watch is what mashups will mean to the enterprise. Will they spur a “new” way of integrating enterprise applications? Will enterprises think of a “new” approach to “service orientation,” and, for example, make data available not only through SOAP but also though REST?
Mashup Example: HousingMaps HousingMaps is a site that pulls real estate listings off the popular classified ad site Craigslist (http://www.craigslist.org), uses the addresses of the homes and apartments listed in a given neighborhood to figure out their latitudes and longitudes, and lets users view the properties on a Google map. Each listing is shown as a pushpin, and with a click on the pushpin a small window pops up with the price and sometimes a thumbnail image of the property. A list of the visible properties runs down the side of the screen, each linked to the original Craigslist posting. And because the results are filtered into price categories, users can easily steer clear of high-rent districts. HousingMaps has no affiliation with Craigslist or Google, but accesses both sites via public APIs.
Summary AJAX also enables a new kind of application, so-called mashups that open up new possibilities of how applications can be built and how Web applications can be consumed. Combing data from multiple Web sites, mashups bring the user significant additional value. In the enterprise, mashups and the traditional integration approach go together as two complementary ways of enterprise integration. 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 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 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||