Yes I know about repeated headers but as I explained I've actually found a use for them. I do pipelining everyday. I don't think "Gee, these repeated headers are really eating up my bandwidth." It's just not that big a deal. The headers are like 10 lines or less. The headers for HN are like what, two lines? Headers are nothing compared to all the useless cruft in HTML nowadays.* That is a situation where I am definitely thinking "This is unbelievable. 90% cruft and 10% content." Wanna "fix" something? Talk some sense into web developers.
* Unless you start jamming them with larger and larger cookies.
Multiplexing is also my preference. I think you would be able to keep your left arm. But I'd rather do it over UDP. HTTP is OK, we all have to use it, but it's not the bee's knees. Uploading stuff via non-idempotent HTTP requests needs to die. The web browser centricity school of thought is not my thing. SPDY is probably excellent for Google's purposes, it just isn't for mine. I guess I am one of the few.
I think Firefox has actually had pipelining support for many years. They just never turned it on by default. As I say no one seemed to use pipelining. Neither servers nor clients. But they sure took notice of SPDY.
I'll bet the SPDY fan tested things with downloading stuff from multiple domains, simulating the typical hodgepodge webpage. But that's not how I do my "browsing". I block everything but the stuff I want, it all comes from one source, one domain. I retrive only the content and leave the cruft behind. Efficiency.
I've never been thrilled with SSL (and guess what, I'm not a Javascript fan either... Netscape was the world's slowest and most unstable browser but they did what they had to do to make ecommerce possible; now we have js, ssl and cookies, what lovely things) but what choice do I have? And what am I supposed to do if my bank has an unpatched SSL? Email them and tell them they are idiots? I just assume there's always something wrong with SSL; if I just wait a while somehow I'm always right. Time to upgrade. Again. I've become an NaCl fan, so maybe there is hope. There life after SSL.
Comments
I agree with your comments.
Yes I know about repeated headers but as I explained I've actually found a use for them. I do pipelining everyday. I don't think "Gee, these repeated headers are really eating up my bandwidth." It's just not that big a deal. The headers are like 10 lines or less. The headers for HN are like what, two lines? Headers are nothing compared to all the useless cruft in HTML nowadays.* That is a situation where I am definitely thinking "This is unbelievable. 90% cruft and 10% content." Wanna "fix" something? Talk some sense into web developers.
* Unless you start jamming them with larger and larger cookies.
Multiplexing is also my preference. I think you would be able to keep your left arm. But I'd rather do it over UDP. HTTP is OK, we all have to use it, but it's not the bee's knees. Uploading stuff via non-idempotent HTTP requests needs to die. The web browser centricity school of thought is not my thing. SPDY is probably excellent for Google's purposes, it just isn't for mine. I guess I am one of the few.
I think Firefox has actually had pipelining support for many years. They just never turned it on by default. As I say no one seemed to use pipelining. Neither servers nor clients. But they sure took notice of SPDY.
I'll bet the SPDY fan tested things with downloading stuff from multiple domains, simulating the typical hodgepodge webpage. But that's not how I do my "browsing". I block everything but the stuff I want, it all comes from one source, one domain. I retrive only the content and leave the cruft behind. Efficiency.
I've never been thrilled with SSL (and guess what, I'm not a Javascript fan either... Netscape was the world's slowest and most unstable browser but they did what they had to do to make ecommerce possible; now we have js, ssl and cookies, what lovely things) but what choice do I have? And what am I supposed to do if my bank has an unpatched SSL? Email them and tell them they are idiots? I just assume there's always something wrong with SSL; if I just wait a while somehow I'm always right. Time to upgrade. Again. I've become an NaCl fan, so maybe there is hope. There life after SSL.