More and more, Ajax apps are using various techniques to keep content fresh in the browser. Essentially, we’re talking about reversing the usual communication flow- the server notices something’s happened, and wants to tell the browser about it. Server “calls” browser, not browser calls server.
The popular Java Ajax framework, DWR, recently released milestone 2 towards a 2.0 release, and introduced the term “Reverse Ajax” in the process, to capture this high-level pattern. This article (via Joe Walker) abstracts the communication details behind a clean API, so you can easily switch between three different implementations of Reverse Ajax:
2. Comet, long lived Http, or the slow load technique:
3. PiggyBack Technique: | Read detailed article…
DWR, Comet, Framework