Re: [jetty-dev] Planning for Jetty-9

[Greg Wilkins <gregw@xxxxxxxxxxx>]

Chad,

I actually do mean that the SPDY connector will become the primary connector (at least for SSL).
The reason for this is that the connector  will determine (using the NPN extension for TLS) if the new connection is going to run HTTP or SPDY.     If it is HTTP, then it will start a HttpConnection like we have now.

So we keep the current Connection code, but have an improved Connector that can create HttpConnections or SpdyConnections

cheers

On 30 January 2012 23:28, Chad La Joie <lajoie@xxxxxxxxx> wrote:

Hey Greg,

On Sun, Jan 29, 2012 at 23:25, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:
> SPDY Connector
> The SPDY protocol from google is already deployed in Chrome and available on
> google servers.  It is intended as a highly efficient carrier of HTTP
> semantics and provides significantly better scalability and latency for
> normal web traffic.  Jetty already has a prototype SPDY connector which
> could become the primary connector for Jetty-9.

The wording on this is a bit worrisome.  I take it you mean that the
SPDY connector would become one of the out-of-the-box,
continually-developed connectors.  The way its written now, it almost
sounds like you mean that SPDY will become the connector you expect
everyone to use and that the HTTP connector would become a secondary,
deprecated, thing.

--
Chad La Joie
www.itumi.biz
trusted identities, delivered
_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev