4 ms·
Now it's time for the other browsers to support it Nope, that time would be when there is an RFC
by Angostura 16y ago
Now it's time for the other browsers to support it
Nope, that time would be when there is an RFC
- edu 16y agoWell, you've plenty of documentation at http://www.chromium.org/spdy http://www.chromium.org/spdy just need to push to the IETF.
- protomyth 16y agoand get it through the standard process: http://www.ietf.org/about/standards-process.html http://www.ietf.org/about/standards-process.html
- drivingmenuts 16y agoNo, now is the time to make it an option, not ram it down our throats. As developers, we need to be able to see things exactly as the people we're developing for who do not always have the luxury of using the latest and greatest browsers.
- djroketboy 16y agoThis is the piss poor attitude that kept us stuck on IE6 for 10 years...
- Seldaek 16y agoThis is the piss poor attitude that makes HN a better place. Not that the other comment was the most clever thing I ever read, but please.
- djroketboy 16y agoYour comment makes little sense; if my piss poor attitude makes HN a better place than why the downvote and snide remark? What is so clever about yours?
- pyre 16y agoYou're suggesting that IE6 gave the user options?
- stcredzero 16y agoStaying there, wallowing in the mud, is an option, though most of us here wouldn't call it a good one.
- jrockway 16y agoFuck them. Why should I suffer because some people don't know how to use their computers?
- drivingmenuts 16y agoHey, Jonathan, learn to read. I said "optional" and I meant it. A dev needs to be able to turn certain "features" on and off to model how various types of users are going to experience a site. How difficult would it have been to implement that, instead of just forcing down our throats?
- cube13 16y agoPretty much. Looking at it, there's a lot of things that need to be fleshed out before it's actually ready. EDIT: The main concern I have over this is that it basically forces a state into an already stateless protocol. Streams need to be established, which means that they need a state(up/down/in-between), and both the server and client(browser, in this case) needs to maintain it. For example: 1. Should the protocol allow browsers to combine streams? I.e. if a user is accessing 3 different youtube videos in HTML5 mode, can the browser do 1 stream for the various static elements on the page, and 3 or more streams for the video and other content? This can make the browser feel faster even when loading non-cached pages, so it's definitely desirable. However, it's a lot more work on both the browser and the server to maintain it. 2. What rules are there for streams? The draft states that 1 HTTP request and response should be used per stream, but would it make sense to allow the browser and server to assign streams? How are browser-instantiated streams different from server instantiated ones? Do those need any additional rules? 3. Should SPDY be content agnostic(where a stream is a stream), or would it make sense to have several QoS levels assigned to them(i.e. high for video or other streaming data, medium for control, low for static elements)? 4.(related to 3) Does HTML, CGI, etc. need to be extended to handle this, or should it be left up to the server/browsers to implement it?
- newman314 16y agoWaiting for nginx to support it too.