2 ms·
I suspect that his point is- Using long-lifed connections, and sliding more data through as time goes on, avoids some of the overhead of additional HTTP header
by e1ven 18y ago
I suspect that his point is-
Using long-lifed connections, and sliding more data through as time goes on, avoids some of the overhead of additional HTTP headers that you see in opening new requests and replies.
- axod 18y agoThat is good for receiving data. Yes, having a single JSONP etc would save some headers there. (Although creates other issues). But for sending data from the browser, you can't do any other sort of streaming, so you have to send a new request each time.
- e1ven 18y agoSure, I suspect he was referring to the server modifications section, not the Javascript. The JS really is a clever idea, I didn't realize that was configurable through JS! Edit- Just checked the posting history of the OP. He looks like a troll. I withdraw my comment, he was just being a jerk. Cool demo, though. Very clever- I wouldn't have necessarily thought about the header size in the sends.