Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twitter adds SPDY support to Netty

netty.io

Post reply on HN
Print view View original

11–20 of 21 posts

Re: Twitter adds SPDY support to Netty

#11

Post by tlrobinson »

[deleted] wrote: post #4

[deleted]

SPDY "gracefully degrades" to HTTP, so there's not really a chicken and egg problem. If your web server makes it easy to enable SPDY, there's not a big reason not to (that I'm aware of).

Technically SPDY is an application layer protocol, but you shouldn't need to change your existing HTTP application to enable it.

Re: Twitter adds SPDY support to Netty

#13

Post by adpowers »

ComputerGuru wrote: post #5
[deleted] wrote: post #4

[deleted]

I believe Firefox + Chrome easily qualifies as "wide browser support." IE is really the only one left now.

Uhh, Safari? Safari is the number one browser on one of my (non-technical) websites, primarily because of mobile traffic (iPhone and iPad).

Re: Twitter adds SPDY support to Netty

#14

Post by bensummers »

I presume that it doesn't support SNI (for SSL vhosts) as the underlying JVM doesn't support it for servers? (I couldn't see anything in the docs, and it says it uses the JVM's SSL support underneath.)

One of the Google chaps said that SPDY required SNI when it was originally announced, so I was hopeful for a while.

Re: Twitter adds SPDY support to Netty

#15

Post by ivanr »

bensummers wrote: post #14

I presume that it doesn't support SNI (for SSL vhosts) as the underlying JVM doesn't support it for servers? (I couldn't see anything in the docs, and it says it uses the JVM's SSL support underneath.) One of the Google chaps said that SPDY required SNI when it was originally announced, so I was hopeful for a while.

Server Name Indication was added in Java 7, so I would expect that Netty supports it too, assuming you're running the latest version of the Java runtime.

Re: Twitter adds SPDY support to Netty

#16

Post by ComputerGuru »

adpowers wrote: post #13
ComputerGuru wrote: post #5

Earlier quoted context omitted.

I believe Firefox + Chrome easily qualifies as "wide browser support." IE is really the only one left now.

Uhh, Safari? Safari is the number one browser on one of my (non-technical) websites, primarily because of mobile traffic (iPhone and iPad).

Mobile browsers are already slow and playing catchup with the desktop web. They're hardly the place cutting edge innovation is taking place.

Re: Twitter adds SPDY support to Netty

#18

Post by wbier »

ivanr wrote: post #15
bensummers wrote: post #14

I presume that it doesn't support SNI (for SSL vhosts) as the underlying JVM doesn't support it for servers? (I couldn't see anything in the docs, and it says it uses the JVM's SSL support underneath.) One of the Google chaps said that SPDY required SNI when it was originally announced, so I was hopeful for a while.

Server Name Indication was added in Java 7, so I would expect that Netty supports it too, assuming you're running the latest version of the Java runtime.

the missing piece is next protocol negotiation. we're working on releasing this code soon. expanded support in finagle (github.com/twitter/finagle) is also forthcoming.

Re: Twitter adds SPDY support to Netty

#19

Post by afimrishi »

chc wrote: post #6
[deleted] wrote: post #4

[deleted]

Surely you just need your webserver to support the protocol. I don't think most apps will directly speak SPDY.

That's true for the most part. But if you want to leverage certain SPDY features like SPDY server push, then your app must be SPDY aware. Likewise, if you want to undo normal HTTP optimizations like hostname sharding which are damaging for SPDY, your app should be SPDY aware. Check out http://dev.chromium.org/spdy/spdy-best-practices for other recommendations.
Post reply on HN