Re:Introducing the ‘mozjpeg’ Project
by kybernetikos on Wednesday March 05, 2014 @02:51PM
(#7349382)
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.
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.
Re:Introducing the ‘mozjpeg’ Project
by IgorPartola on Thursday March 06, 2014 @01:54AM
(#7352299)
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/
Thanks. I misunderstood that post.
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.