Reverse Ajax revealed
Can you explain reverse Ajax and do you consider it technology that can be used in something beyond trial or fringe applications?

    Requires Free Membership to View

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Reverse Ajax is basically a way for servers to send Ajax-based information to browsers. Because browsers don't expect information from servers without having made a request, you can either do this with polling, by holding open an HTTP connection, or by sending more information with a response than the browser requested. In other words, reverse Ajax equals regular Ajax plus one or another stupid HTTP trick we used to use back in the Web 1.0 days.

This was first published in June 2008