W3C home > Mailing lists > Public > public-webapi@w3.org > February 2008

Re: multipart, server-sent events, and

From: Mark Baker <distobj@acm.org>
Date: Tue, 19 Feb 2008 00:20:15 -0500
Message-ID: <e9dffd640802182120vc702f07j82abc870ff8b191@mail.gmail.com>
To: "Maciej Stachowiak" <mjs@apple.com>
Cc: "Kris Zyp" <kzyp@sitepen.com>, public-webapi@w3.org

Hi Maciej,

On 2/18/08, Maciej Stachowiak <mjs@apple.com> wrote:
> Last time I looked into this, there were some proxies and some origin
> server configurations (in particular certain Apache modules, perhaps
> now obsolete) that broke with pipelining.

Can you define "broke"?

I've done a search on Apache and Squid pipelining bugs, and didn't
find any open ones.

> Since it is not possible to
> find out from the server if pipelining is correctly supported, and
> since it is not generally possible to tell from the response that it
> has failed, enabling it by default in the browser http stack was not a
> safe thing to do.
>
> Since the breakage is caused in at least some cases by proxies, it is
> not in general safe to let XHR users opt in since they may control the
> origin server but generally would not control whatever proxies are
> between the server and the user.
>
> Pipelining is a great potential performance improvement and it's sad
> that it can't safely be used on the public Internet right now, so I
> hope we someday find a way out of the impasse.

Well, I'd like to see some hard evidence of this before we write it off.

Mark.
-- 
Mark Baker.  Ottawa, Ontario, CANADA.         http://www.markbaker.ca
Coactus; Web-inspired integration strategies  http://www.coactus.com
Received on Tuesday, 19 February 2008 05:20:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 February 2008 05:20:26 GMT