5 ms·

Unfortunately chrome recently removed support for "multipart/x-mixed-replace". It's too bad too. It was a simple way to implement a webcam. https://code.google

by dmm 13y ago

Unfortunately chrome recently removed support for "multipart/x-mixed-replace". It's too bad too. It was a simple way to implement a webcam. https://code.google.com/p/chromium/issues/detail?id=249132 https://code.google.com/p/chromium/issues/detail?id=249132 http://blog.chromium.org/2013/07/chrome-29-beta-web-audio-and-webrtc-in.html http://blog.chromium.org/2013/07/chrome-29-beta-web-audio-an...

fzzzy 13y ago
According to those links, they still support it for images, but removed support for other types of resources. It's too bad IE never supported multipart/x-mixed-replace or we might have seen more live updating websites earlier. Now that we have WebSockets and well understood long polling approaches it doesn't matter any more, since x-mixed-replace would keep the download spinner spinning forever and the newer approaches don't have that problem.
- kybernetikos 13y ago
  I used multipart replace in firefox for streaming data for years with no download spinner. I couldn't use it in chrome because chrome always seemed to have some weird bug where 'frames' (of data in my case) were delayed. I was disappointed when they were unceremoniously ripped out, but yes, websockets are better.
  - fzzzy 13y ago
    Ok, I believe you, it's been over 10 years since I tried it :-) Maybe I was thinking of the forever iframe, where a regular application/javascript document had content added to it incrementally over time.
    - IgorPartola 13y ago
      It is actually pretty bizarre. If you point Chrome at a .jpeg that does multipart/replace it will stall, giving you roughly 0.2 fps. Point it at a. .html that contains an <img> tag and it works fine. Found this out while hacking on Hawkeye: https://igorpartola.com/projects/hawkeye/ https://igorpartola.com/projects/hawkeye/
- dmm 13y ago
  Thanks. I misunderstood that post.
- makomk 13y ago
  Apparently breaking the web interface for older versions of CUPS in the process.

by dmm 13y ago

fzzzy 13y ago

According to those links, they still support it for images, but removed support for other types of resources. It's too bad IE never supported multipart/x-mixed-replace or we might have seen more live updating websites earlier. Now that we have WebSockets and well understood long polling approaches it doesn't matter any more, since x-mixed-replace would keep the download spinner spinning forever and the newer approaches don't have that problem.

kybernetikos 13y ago
I used multipart replace in firefox for streaming data for years with no download spinner. I couldn't use it in chrome because chrome always seemed to have some weird bug where 'frames' (of data in my case) were delayed. I was disappointed when they were unceremoniously ripped out, but yes, websockets are better.
- fzzzy 13y ago
  Ok, I believe you, it's been over 10 years since I tried it :-) Maybe I was thinking of the forever iframe, where a regular application/javascript document had content added to it incrementally over time.
  - IgorPartola 13y ago
    It is actually pretty bizarre. If you point Chrome at a .jpeg that does multipart/replace it will stall, giving you roughly 0.2 fps. Point it at a. .html that contains an <img> tag and it works fine. Found this out while hacking on Hawkeye: https://igorpartola.com/projects/hawkeye/ https://igorpartola.com/projects/hawkeye/
dmm 13y ago
Thanks. I misunderstood that post.
makomk 13y ago
Apparently breaking the web interface for older versions of CUPS in the process.