Who said it's undesirable?

Oh right, this is KeepYourRemoteFingersAwayDot, sorry.

Say what now? Precaution against what?
And browsers cache assets transferred over HTTPS just fine.

Well, you are wrong. At least as a general statement. :)

It prevents caching by proxies, but it works fine with regular client/server HTTP caching.

I actually wouldn't mind typing that in or dictating it.

msblows://microsoft.com

Mmmm, braiiiiiiins...

Sorry, you were saying?

Well, they could have gone with "Hypertext Transfer Protocol 2.0 Speed and Mobility Express Professional Server 2013 Edition for Workgroups" instead, or httpsmepew:// for short. I think "S&M" is already a pretty good try for them.

I really like that SPDY insists on SSL secured connections. This is what we should be moving towards and having it forced upon us in the next HTTP revision is a great step. But of course Microsoft tries to be backwards compatible, as they always are.

I say SPDY for modern devices, HTTP 1.1 for the foreseeable future for low powered devices. It still works fine, you know? And by the time HTTP 1.1 is retired, there will be no more devices so underpowered they can't establish a SPDY connection. For the love of god, drop legacy when you get the chance!

Oui, c'est suoirálih.

Well, soon you'll be able to try your luck on Arctic call-in shows. I'd say the chances should be pretty decent there.

I currently get a 431ms Japan <> UK ping on a pretty mediocre Japanese ADSL line in the country side.
So, yes, that's realistic.

A lot of members must've brought their kids to work that day.

But that's going to be the other way around soon, what with the Euro going down and the US$1 per bought-European-vote rate increasing.

The car driver coming down the street at 200mph. Without him, there'd be no need to help the old lady across the street in the first place, she could do it alone.

QED.

Ah, grasshopper... the article _is_ the first post. What we need after that is a frist post.

You blew it.

Yup, coming to a theater near you April 19.