- From: Alex Russell <alex@dojotoolkit.org>
- Date: Fri, 15 Feb 2008 13:07:26 -0800
- To: Kris Zyp <kzyp@sitepen.com>
- Cc: "Mark Baker" <distobj@acm.org>, <public-webapi@w3.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Feb 14, 2008, at 1:27 PM, Kris Zyp wrote: > >> I always wondered why plain old multipart/mixed was never used, with >> Content-Location headers per part. It would even be more general, >> permitting multiple streams to be muxed over a single connection. > > I agree, multipart/x-mixed-replace is a strange content type for > streams of messages. From a functional standpoint it does not > matter, Alex and I simply want something that can provide a stream > of messages from the server. Yes. I was suggesting multipart/x-mixed-replace because it's nearest to a de-facto standard currently. It works (modulo connection close notification issues) on Firefox for text content and is only a bug or 2 away from working correctly in Safari. Obviously, I'm not opposed to something better, and since this would be a JS API no matter what, some level of divergence is tolerable while "better" gets deployed. Regards - -- 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (Darwin) iD8DBQFHtf8Rz3jiQlnDlyMRAoMjAJoD+e0QWhXIcZiMSRmUjiX7wqZnKgCfReNO e48y0OFMSUZ06DpwP9dx+sk= =3XJ5 -----END PGP SIGNATURE-----
Received on Friday, 15 February 2008 21:07:47 UTC