Reverse AJAX is actually an implementation (seems more of a marketing buzz word to me) rather than a technology. In case of AJAX it is the browser that initiates the request, but what if the server needs to inform the browser of something ?
Suppose there are 6 clients (browsers) connected to a server viewing the same financial record, if one of the clients updates the record then how do the other connected clients get informed that the record has been updated ? this is a typical problem that a reverse AJAX solution can be used to target.
There are generally 3 methods that can be used for implementation of Reverse AJAX, the details can be read on the original link that I posted earlier
1) COMET or SLOW LOAD
- COMET was coined by Alex Russell , its a technique to keep keep alive HTTP connections
- Bryce Nesbitt's example on slow loading, it uses an frames to keep the connection open
- the browser polls the server after some specified intervals to check if something new has happened
- piggy backing means that whenever a browser requests an operation, you send back the notification with the result of that request, hence piggy backing on the response
I'll try it out if I can get the time, I'm currently preparing for an MCTS exam due in July... so lets see
No comments:
Post a Comment