W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2006

[whatwg] XMLHttpRequest connection limit

From: Ted Goddard <ted.goddard@icesoft.com>
Date: Wed, 1 Nov 2006 17:06:36 -0700
Message-ID: <7B7EDD0A-99FB-4357-97E3-27D786EDDEB7@icesoft.com>

On 1-Nov-06, at 4:42 PM, Charles Iliya Krempeaux wrote:

> Hello,
>
> I think we're starting to see some of the limits of HTTP being hit.

We're actually quite far from using the full capabilities
of HTTP.  We're definitely bumping into limits exposed by
HTTP implementations, though (in the case of Ajax we could
use control over the number of HTTP connections and HTTP
pipelining).

> Personally, I'd like to a protocol which allows communication in  
> both ways.
>
> HTTP 1.2?  XMPP/Jabber?  Something else?

Exposing XMPP well in a JavaScript API would certainly be
interesting.  BEEP is another possibility.  However, all of
these would require protocol implementation and API
standardization.  If we can do a lot more just by changing
a single parameter, perhaps we should start with that and
then begin work on adding more suitable protocols.

Regards,
Ted.

> See ya
>
> On 11/1/06, Ted Goddard <ted.goddard at icesoft.com> wrote:
> Ajax applications often make use of multiple concurrent
> HTTP requests; in particular Ajax Push (Comet/Reverse Ajax)
> makes use of two HTTP connections: one to block waiting for
> messages from the server, the other to send messages to
> the server.
>
> The problem is that the connection limit for many browsers
> is two connections per browser per server. Sophisticated
> Ajax applications, on the other hand, need two connections
> per window (or tab) per server. This allows each window or
> tab to support two-way messaging with the server.  Without
> it (and without the ability for the two client windows
> to communicate and thereby share a single connection) the
> two available HTTP connections become consumed by the
> blocking message requests.
>
> I would like to propose that the HTTP connection limit
> be standardized at two per user-initiated window. (For
> instance, Safari is not limited to two connections per
> browser.)  This should be a relatively straightforward
> change in browser policy (browsers other than Safari,
> that is), but it is a significant enhancement for
> Ajax applications.
>
> Ted.
>
>
>
> Ted Goddard, Ph.D. - Senior Software Architect
> ICEsoft Technologies Inc
> Suite 300, 1717 10th St. NW
> Calgary, AB - Canada - T2M 4S2
> T 403 663-3322
> F 403 663-3320
> ted.goddard at icesoft.com
> http://www.icesoft.com
>
>
>
> -- 
>     Charles Iliya Krempeaux, B.Sc.
>
>     charles @ reptile.ca
>     supercanadian @ gmail.com
>
>     developer weblog: http://ChangeLog.ca/
>
Received on Wednesday, 1 November 2006 16:06:36 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:49 UTC