1. 33
  1.  

  2. 6

    Anyone know if any browsers explicitly define their caching semantics for what they store, for a live-streamed object which is never “terminated”? This isn’t server-push object replacement, after all, but one object which has internal framing, and so keeps getting larger. So if the 4kB/sec claim on the page is right, then if you leave the browser open for a day then that’s a third of a GB. I know people who can forget their browser tabs for days on end.

    1. 4

      I remember on older webcams, their web interfaces could stream video via motion JPEGs, which just sends endless JPEG frames to the browser. I don’t think it was a problem back then even for those old browsers.

      1. 1

        I don’t think it was a problem back then even for those old browsers

        Even if it was a problem, this was the nineties we’re talking about. People would barely even notice if you crashed their browser or computer and they had to restart it, so long as you didn’t crash it much more than once an hour or so.

    2. 5

      I see somebody rediscovered gifsockets https://github.com/videlalvaro/gifsockets :)