The server implementations are significantly more difficult than the client implementations. And the client implementations aren't easy.
Among other problems:
* Need an SSL key, which means self-signing, $$, or a monthly update to keep your free key current
* Implementing SPDY server-push means explicit dependency lists you currently don't keep
* The protocol is young and has changed multiple times
* It's binary and hard to test -- it's not always clear where a problem lives
Add up those and "oh, my site is fast enough for what I'm doing" and you get a recipe for no good free server implementations.
Presumably some larger companies are working on it, but they have to justify that (substantial) effort for improvements only the Chrome portion of their userbase ever see.
So at least Firefox supporting SPDY will put more pressure on companies to support it.
Among other problems:
* Need an SSL key, which means self-signing, $$, or a monthly update to keep your free key current * Implementing SPDY server-push means explicit dependency lists you currently don't keep * The protocol is young and has changed multiple times * It's binary and hard to test -- it's not always clear where a problem lives
Add up those and "oh, my site is fast enough for what I'm doing" and you get a recipe for no good free server implementations.
Presumably some larger companies are working on it, but they have to justify that (substantial) effort for improvements only the Chrome portion of their userbase ever see.
So at least Firefox supporting SPDY will put more pressure on companies to support it.