An introduction to Reverse Ajax Despite all the hype, Ajax cannot get real time information directly from the server. If some information arrives after the user has loaded a page they will never see it, unless they refresh the page. We could easily solve this problem in the traditional way, by having a having a little bit of Javascript in the webpage that automatically refreshes the page every few seconds. But refreshing an entire page every few seconds is overkill. If the millions of users of a large site were to refresh every few seconds it would increase the bandwidth dramatically. The effect on the servers would be similar to a DOS attack! We really just need the small piece of real time data to be updated on the browser as soon as it arrives in the server. The simplest way would be to have the server tell all the browsers that the data has been updated. But as we discussed in the introduction to Ajax, servers cannot initiate contact with browsers. Hence we need a solution which gets around this problem. Reverse Ajax allows servers to push content out to browsers immediately it becomes available
Subscribe to:
Post Comments (Atom)
4 comments:
Good Post men...Keep it up
Please Send More links On this Topic
It Is Interesting Topic
thanks.
Do you have any more links/info on this subject? I am looking for a sample implementation in C#, kinda hard to come by.
The major drawback of Reverse Ajax is that it needs long running HTTP Connections (since server needs to know which client are currently active).This is a major issue since server would be overloaded keeping long running sockets opened!
and moreover AJAX one will use to not post whole page but just a part of it so you can very easily do traditional AJAX.
Instead of burdening the server with the task of maintaining the active clients why not distribute that load on to clients....?
Post a Comment
Comments posted on ASP.Net C# Programming Blog are moderated and will be approved only if they are on-topic and not abusive. Please email me or my team for tech-support or blogging related questions. Avoid including website URLs in your comments - Thanks Nirav Bhatt