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

Subject: Re: push data from server to client web browser
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Thu, 25 Sep 2008 12:36:44 -0700 (PDT)
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>

From: Thorbjørn Ravn Andersen
Well, you can also put it that the client tells the server "I am ready,
just give me what you want when you want" and then awaits server
data.

Sorry, we're still not in sync. There's an HTTP server in the middle. And in the case of J2EE, there's also an application server in the 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 indefinately too, but they won't. The connections will drop, on one end or the other.

Nathan.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: push data from server to client web browser , Thorbjørn Ravn Andersen

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.