server push in ext 2.0.?

[rahulmca1@gmail.com]

Hi,

Ext is a great framework to go ahead with.
Are you going to introduce the concept of server push in ext 2.0.? ;)

thanks =;

[brian.moeskau]

No plans.

[mystix]

Hi,

Ext is a great framework to go ahead with.
Are you going to introduce the concept of server push in ext 2.0.? ;)

thanks =;

:-/ correct me if i'm wrong, but isn't server-push a server-side technology, and not a client-side technology?

[devnull]

The main problem is that there is no real support for push technology in browsers, so anything thats created would be a hack thats specific to each browser. And as mentioned, highly specific to the server platform as well. It's just not within the scope of a client-side library to do this right now.
Furthermore, I've seen reports that show server push does not scale well at all, leading to a huge load on the server side. For now, Ext contains great tools for polling to get updates (updateManager and related components).

[vaddi.sudhakar]

Hi,

I am also looking for Server-side push technique with Ajax. If you have found a solution, please post the sample for the same.

Thanks in advance !

Cheers
Sudhakar

[RWaters]

http://extjs.com/roadmap

3.0 (Fall/Winter 2008)
* Comet/Bayeux support

[wm003]

http://extjs.com/roadmap

3.0 (Fall/Winter 2008)
* Comet/Bayeux support

In the meantime tof's solution (http://extjs.com/forum/showthread.php?p=58156#post58156) works perfect

[devnull]

his solution does work (I am using a modified version of it for an app), but it isnt perfect.

[Eric24]

Another problem with push: firewalls. Anything that needs to run over the Internet can't effectively do "true" push. Someone mentioned Ajax "push", but this is really just a simulated push, where the client/browser uses Ajax to request data, using polling or response delays (or some combination thereof). Firewall-friendly push to a browser requires something in the browser to open a TCP session, which passed through the firewall from the client to the server, but then allows the server to send async data to the client via the established and persistent TCP session. That would require something like ActiveX, Java (not JavaScript), or maybe Flash (?).
--Eric

[wm003]

his solution does work (I am using a modified version of it for an app), but it isnt perfect.
the only thing i discovered is, that other ajax.requests wait until the 30sec timeout from the comet-ajax have been reached. I also use Mindpatterns concurrent ajax-calls but this would allow 2 ajax.reuests at a time(i still need to test, if this issue occurs when i turn off mindpatterns ajax-routine), so i came up with the solution to stop the comet-ajax everytime i will start another planned ajax-request...

ok, it's not "perfect" for everyone, but i was quite happy with the result :) and works until Ext 3.0 will come up with (the best?) solution.

[devnull]

I have had problems with multiple "updates" getting processed at the same time, no matter what i set the poll interval too. I suspect this is due to caching somewhere that cant be controlled. It doesnt cause any negative effects for me as i am just using it to monitor a long and intensive server process, rather it just skips that update (updating a progress bar).
the term I have seen used for this type of "push" method is "infinate ajax".