Reverse Ajax, Part 5, Event-driven web development
From the developerWorks archives
Date archived: January 4, 2017 | First published: September 20, 2011
This series explores how to develop event-driven web applications using Reverse Ajax techniques. Part 1 introduced different ways to implement a Reverse Ajax communication. Part 2 explained how to implement Reverse Ajax using WebSockets and discussed the limitations of web servers using Comet and WebSockets. Part 3 explored the difficulties of implementing your own Comet or WebSockets communication system, and it introduced Socket.IO. Part 4 covered Atmosphere and CometD. In this final part of the series, learn about event-driven development. Build an example event-driven web application using the accompanying source code.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.