Re: push data from server to client web browser -- WEB400

Subject: Re: push data from server to client web browser
From: Thorbjørn Ravn Andersen <ravn@xxxxxxxxxx>
Date: Thu, 25 Sep 2008 23:33:02 +0200
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

Nathan Andelin skrev:

middle. And neither of those servers is going to wait indefinately for an application to respond to a request from a browser. If you configure your middleware servers to wait indefinitely, then scalability goes down the tube. And it presuposes that browsers will wait

Hence my reference to the Jetty+Comet white paper.
We are discussing server push, to me that is _web_ server push (or j2ee web container). How it decides when to push what where, is determined internally and not necessarily in a ProgramCall.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.