Comments on: DWR 2.0: Reverse Ajax

By: CometDude

CometDude — Thu, 20 Aug 2009 23:42:07 +0000

@newbie: Try StreamHub Reverse Ajax Server - it uses true push.

By: newbie

newbie — Thu, 23 Nov 2006 04:23:43 +0000

so..can the dwr provide me with the true push just like lightstreamer?i don’t want my client keep requesting my server for new updates

By: Techhawking » Blog Archive » The RAJAX framework (Reverse AJAX)

Techhawking » Blog Archive » The RAJAX framework (Reverse AJAX) — Sun, 19 Nov 2006 07:37:51 +0000

[...] http://ajaxian.com/archives/dwr-20-reverse-ajax [...]

By: Irving Lv

Irving Lv — Mon, 04 Sep 2006 03:52:54 +0000

It says DWR2.0 uses Comet as default, but when I test the Chat demo I find that it also polls the server although at a relative long interval. I am not very clear about how DWR implement the Comet mechanism, is Comet means a long interval polling or a tradeoff between polling and long-lived http connection?

By: Aaron Johnson

Aaron Johnson — Thu, 18 May 2006 08:54:24 +0000

Links: 5-17-2006

Ajaxian Â» DWR 2.0: Reverse Ajax Prediction: reverse ajax (I prefer rajax) will be big… and hard on servers. (categories: ajax rajax )…

By: Deepak

Deepak — Thu, 27 Apr 2006 20:58:29 +0000

Has anybody got this working? If yes, do you use “polling” or “comet”
setting? I don’t see any documentation on usage of these except for Chat example which uses “polling” setting. As per my experience, it sometimes work, sometimes doesn’t – pretty unreliable.

So far, I have not been able to get it working with “_pollComet”. Any body had better luck than me? Pls let me know if so.

By: ãƒ©ã‚¯ãƒ©ã‚¯æ—¥è¨˜

ãƒ©ã‚¯ãƒ©ã‚¯æ—¥è¨˜ — Wed, 26 Apr 2006 08:37:44 +0000

A new concept – REVERSE AJAX

æ–°ã—ã„ã‚³ãƒ³ã‚»ãƒ—ãƒˆã‚’å‹‰å¼·ã—ãŸã€‚

Reverse Ajax
Comet Queryies

Reverse Ajaxã®æ„å‘³ã¯Ajaxianã‹ã‚‰ã®èª¬æ˜Žã‚’è¦‹ã‚Œã°åˆ†ã‹ã‚‹ã¨æ€ã†ã€‚
The big new feature is Reverse Ajax: DWR 1.x allowed you to asynchronously call Java code from Java…

By: Gonzalo

Gonzalo — Sun, 16 Apr 2006 20:09:00 +0000

So… “the process of using either polling or a long lived connection (Comet)”… why the need to rename it as “Reverse AJAX” other than the cool sound of it? ;)

By: HU YIQUN

HU YIQUN — Thu, 13 Apr 2006 15:45:34 +0000

To pplante - As mentioned in this post, both polling and Comet are sopported. If you use the polling mode, it means you keep requesting server at some interval. That's the way you said like everything in the web2.0 done. But if you use Comet mode, then it's like server-push technique. Please refer to Comet

By: Jon

Jon — Thu, 13 Apr 2006 14:04:57 +0000

Iâ€™m using sockets for my realtime systems. Currently Iâ€™m using Flash8 (AFLAX). What Iâ€™m running into is that a lot of MSIE users canâ€™t get Flash 8 to install. About 1 out of 5 right now. I tried some Java applets to do sockets, but I couldnâ€™t get that to work across platforms too well (again MSIE).

Developing and deploying eLearning encounters the same types of hurdles. You *want* to use the latest and greatest technology but some of your audience just doesn’t have it…nor are they able to install it. The ‘live’ connection between the eLearning course and the server is typically through a java applet that has an open socket connection to the server and a javascript API that makes calls to the applet for storing/retrieving information. The trouble is the JRE. If the user has a version that’s too old, they have to download and install a new one, etc etc.

I feel your pain….

By: Neil Mix » Blog Archive » Asynch updates == execute JavaScript from your server

Wed, 12 Apr 2006 23:52:45 +0000

[...] I see that a new version of DWR has been released. And it sounds very familiar for some reason. [...]

By: Phill Kenoyer

Phill Kenoyer — Wed, 12 Apr 2006 23:19:54 +0000

I’m using sockets for my realtime systems. Currently I’m using Flash8 (AFLAX). What I’m running into is that a lot of MSIE users can’t get Flash 8 to install. About 1 out of 5 right now. I tried some Java applets to do sockets, but I couldn’t get that to work across platforms too well (again MSIE).

By: Steven Roussey

Steven Roussey — Wed, 12 Apr 2006 22:15:30 +0000

pplante — you aren’t quite getting it right. Their system keeps a socket open indefinately. Think of each client as slowly loading content from the server and displaying it progressively. Except that the data can trickel in over hours. Then you have a server process-to-process communication so that all the other processes that you might want to notify start downloading a more information. This won’t work with PHP, etc., since they don’t have process-to-process communication, and it won’t work with HttpXmlObject (as far as I know, since most don’t implement multi-part-mime needed to make this work), but it will work with Java and Iframes.

By: Phill Kenoyer

Phill Kenoyer — Wed, 12 Apr 2006 18:42:19 +0000

I would think that the only way to do “Reverse AJAX” is to use a socket connection back to the server. No?

By: pplante

pplante — Wed, 12 Apr 2006 18:01:56 +0000

Maybe I am just not understanding this concept right. But I do not see how this can be called “Reverse AJAX” when all it seems to do is have the client javascript keep calling the server, so that when the server has a new update the client can receieve it.

If thats all this does then I don’t really think its “Reverse AJAX.” Its just a client-server events system, but like everything else in the web 2.0 world we have to give this an improper name so that way it seems revolutionary or cool.