|Summary:||Add support for multipart/x-mixed-replace to XMLHttpRequest|
|Product:||WebKit||Reporter:||Rob Butler <crodster2k>|
|Severity:||Enhancement||CC:||alex, annevk, ap, chase, dadariop, eric, goberman, gregory.houston, ian, matt, rainhead|
|Version:||523.x (Safari 3)|
Description Rob Butler 2007-06-25 11:55:46 PDT
Add support for multipart/x-mixed-replace to XMLHttpRequest as was done in Firefox. Please use same method calls so API is compatible between WebKit, Safari & FireFox. https://bugzilla.mozilla.org/show_bug.cgi?id=237319
Comment 1 Alexey Proskuryakov 2007-06-25 13:10:50 PDT
Confirmed. Please note that support for multipart/x-mixed-replace is not even considered for inclusion in future versions of XMLHttpRequest spec yet, as seen in the current draft of the spec, <http://www.w3.org/TR/XMLHttpRequest/#notcovered>. We may want to discuss its possible standardization first.
Comment 2 Anne van Kesteren 2007-06-26 06:18:01 PDT
HTML5 seems to have <event-source> for server push.
Comment 3 Rob Butler 2007-06-26 08:09:18 PDT
Comment 4 Rob Butler 2007-06-26 08:17:45 PDT
(In reply to comment #1) > Confirmed. > > Please note that support for multipart/x-mixed-replace is not even considered > for inclusion in future versions of XMLHttpRequest spec yet, as seen in the > current draft of the spec, <http://www.w3.org/TR/XMLHttpRequest/#notcovered>. > We may want to discuss its possible standardization first. > Standardization happens via 2 routes. Route 1, everyone gets in a room and creates a spec with little or no real world experience. These specs sound great on paper, but usually have a great deal of problems when people try to implement them. Route 2, someone comes up with an innovative idea and everyone says "Wow, that's cool". They then copy that idea as closely as possible. Everyone now supports that "defacto" standard and eventually it is documented as "the standard" by some committee. Route 2 usually results in better software and more rapid innovation. This is particularly relevant to XmlHttpRequest. It was originally an IE only extension and the rest of the browser world said "Wow, that's cool". Soon it showed up in all the other browsers (without the need for ActiveX on which IE's XmlHttpRequest is based). It might be worthwhile to implement support for multipart/x-mixed-replace in WebKit in a manner compatible with Firefox's and then push for that to become the standard with the appropriate group.
Comment 5 Eric Seidel (no email) 2007-10-09 22:56:51 PDT
Personally I think supporting this is really important. I might even try and hack a patch together.
Comment 7 Alexey Proskuryakov 2009-11-02 11:11:27 PST
EventSource is now available in WebKit (and proposals to standardize support for any of the multipart/* flavors were few, and never got enough attention to be added to XMLHttpRequest).
Comment 8 goberman 2010-12-28 07:34:39 PST
I have to agree with Rob. EventSource implementation is a disaster. Besides poor design, it has memory leaks and cannot be used from Java: http://code.google.com/p/chromium/issues/detail?id=66666 It is obvious that it was not tested very well. I cannot imagine anyone would prefer EventSource to the multipart/x-mixed-replace.
Comment 9 Dario Palumbo 2013-01-25 09:49:33 PST
Hi guys is there any news about this issue? FF has this option since a long time... https://bugzilla.mozilla.org/attachment.cgi?id=144021&action=diff Thanks a lot
Comment 10 Matthieu Heimer 2014-11-19 21:25:43 PST
I think this can be closed as WONTFIX. This feature has removed from FireFox, https://bugzilla.mozilla.org/show_bug.cgi?id=843508.