That doesn't sound like long polling. Long polling sends a request and then receives one or more responses over its lifetime. It wouldn't be a 5 second latency if implemented properly. The max latency should be the interval between the termination of one poll cycle and the setup of the next.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Kevin Turner
Sent: Wednesday, July 11, 2012 6:03 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Websockets on the IBMi
With my web socket alternative, there is virtually no latency - ever. As soon as the call arrives, the server send the customer screen to the browser instantly. It doesn't have to wait for (up to) 5 seconds for it to be polled by the server. In order to achieve the same instant response using XHR long polling, I have to reduce the polling interval to something like 100ms. So while waiting for a call, my browser is flooding the server with 600 HTTP requests per second. Multiple that by 1500 call centre agents, and the server is getting 900,000 HTTP requests per minute. The server and the CGI application just dies. With web sockets, I get an instant response and virtually no traffic in comparison.
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.
midrange.com
