This discussion seems pointless, given that you can set an Ajax timer to make an async request every number of milliseconds to the server. What are you going to do, run a job on the iSeries and then 'push' the data out to however number of browsers that 'might' be listening (how long would that job take)?
Examine the needs of the application you have in mind and I'm sure it can be met without 'Push' (perhaps that’s why push has never really caught on just yet)
IMHO
- Maurice O'Prey
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Thorbjørn Ravn Andersen
Sent: 25 September 2008 19:42
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] push data from server to client web browser
john e skrev:
http://en.wikipedia.org/wiki/Comet_(programming)
It's a big hack, and therefore complex to implement and i don't know how scalable it is.
But it seems to work (never tried it myself though).
Any sufficiently advanced hack is indistinguishable from magic :)
It is very important to use a web server which is built to serve Comet
applications, as you otherwise end up using one thread (or even worse -
process) per outstanding idle request.
From
http://www.webtide.com/downloads/whitePaperAjaxJetty.html which
discuss the Jetty web server (which is a good alternative to Tomcat)
"The following table shows that a Web 1.0 server can handle 10000 users
with 500 threads and 36MB of thread stacks, which is easily achievable
with current JVMs and servers. For a Web 2.0 application these
requirements explode an order of magnitude to 10600 threads and 694MB of
stack memory, which is pushing the limits of current servers without
even considering the resource requirements of the application:"
I know that the i scales well, but having to use over half a gigabyte of
memory just to serve is a bit much :)
midrange.com
