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

Re: Multipart Support Proposal

From: Alex Russell <alex@dojotoolkit.org>
Date: Thu, 21 Feb 2008 06:51:48 -0800
Cc: "Kris Zyp" <kzyp@sitepen.com>, "Web API WG (public)" <public-webapi@w3.org>
Message-Id: <E23F5599-9BDB-4723-A3AC-D9B80B1BBD45@dojotoolkit.org>
To: Anne van Kesteren <annevk@opera.com>

Hash: SHA1

Hey Anne:

On Feb 19, 2008, at 8:12 AM, Anne van Kesteren wrote:

> On Tue, 19 Feb 2008 16:55:18 +0100, Kris Zyp <kzyp@sitepen.com> wrote:
>> Multipart Support
> Do we really want to overload XMLHttpRequest with "comet-style"  
> functionality?

I don't have a strong opinion one way or another, but I was simply  
suggesting that we codify what's closest to being most widely  
implemented. Safari is already very close and modulo the big  
connection-level issues, Mozilla is already there.

> XMLHttpRequest is already quite complex. I'd personally (and I think  
> the company I represent would agree) much rather go with the server- 
> sent events proposal in HTML 5. Remove some functionality from it as  
> proposed by the WebKit guys so that it becomes easier to implement  
> and author and ship it.

Perhaps, but server-sent events are *still* silent on the most  
important points:

	* how do you detect connection close?
	* what is/will-be done to ease the 2-connection limit?

I really don't have an opinion about what API surfaces solutions to  
those problems, only that one of them does. As-written, neither  
multipart or server-sent events currently are workable in the wild.


- --
Alex Russell
alex@sitepen.com  A99F 8785 F491 D5FD 04D7 ACD9 4158 FFDF 2894 6876
alex@dojotoolkit.org BE03 E88D EABB 2116 CC49 8259 CF78 E242 59C3 9723

Version: GnuPG v1.4.2 (Darwin)

Received on Thursday, 21 February 2008 14:52:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:09:59 UTC