-
Support Options
Recent Comments
- Lars Vogel on The new Jetty 9 HTTP client
- Tomas Theunissen on The new Jetty 9 HTTP client
- Thomas Becker on Why detecting concurrent issues can be difficult
- Min Idzelis on Why detecting concurrent issues can be difficult
- Jetty 9 – Updated WebSocket API | Webtide Blogs on Jetty 9 – Features
Archives
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- May 2011
- April 2011
- March 2011
- February 2011
- November 2010
- October 2010
- August 2010
- June 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- October 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- May 2006
- April 2006
- March 2006
- November 2005
- September 2005
- February 2005
- December 2004
- October 2004
- September 2004
- July 2004
- June 2004
- May 2004
- February 2004
- December 2003
- November 2003
- January 1970
Categories
- Ajax Comet
- cometd
- General
- GWT
- HTTP
- i-jetty
- Intalio
- Java
- Jetty
- Maven
- Servlets
- SPDY
- Status
- Uncategorized
- WebSockets
- Webtide
Meta
- Log in
- Entries RSS
- Comments RSS
- WordPress.org
SPDY support in Jetty
SPDY is Google’s protocol that is intended to improve user experience on the web, by reducing the latency of web pages, sometimes up to a factor of 3. Yes, three times faster.
How does SPDY accomplish that ?
SPDY reduces roundtrips with the server, reduces the HTTP verboseness by compressing HTTP headers, improves the utilization of the TCP connection, multiplexes requests into a single TCP connection (instead of using a limited number of connections, each serving only one request), and allows for server to push secondary resources (like CSS, images, scripts, etc.) associated with a primary resource (typically a web page) without incurring in additional round-trips.
Now, the really cool thing is that Jetty has an implementation of SPDY (see the documentation) in the newly released 7.6.2 and 8.1.2 releases.
Your web applications can immediately and transparently benefit of many of the SPDY improvements without changes, because Jetty does the heavy lifting for you under the covers.
With Chromium/Chrome already supporting SPDY, and Firefox 11 supporting it also (although it needs to be enabled, see how here), more than 50% of the web browsers will be supporting it, so servers needs to catch up, and where Jetty shines.
The Jetty project continues to foster innovation by supporting emerging web protocols: first WebSocket and now SPDY.
A corollary project that came out from the SPDY implementation is a pure Java implementation of the Next Protocol Negotiation (NPN) TLS Extension, also available in Jetty 7.6.2 and 8.1.2.
To prove that this is no fluke, we have updated Webtide’s website with Jetty’s SPDY implementation, and now the website can be served via SPDY, if the browser supports it.
We encourage early adopters to test out Jetty’s SPDY and feedback us on jetty-dev@eclipse.org.
Enjoy !
12 comments on “SPDY support in Jetty”
-
Pingback: Fast, Easy Web Design! » Blog Archive » InfoQ Ratpack Classy and Compact Groovy Web Apps
-
-
simon on said:
In the 7.6.2 and 8.1.2 releases, we forgot to make SPDY available in the distribution; we will fix this in 7.6.3 and 8.1.3.
Meanwhile, you can download the SPDY jars from repo2.maven.org/maven2/org/eclipse/jetty/spdy/.
Sorry about that, SPDY was there but slipped out of the distribution packaging.
Reply ↓
-
-
Stefan Arentz on said:
I actually am interested in the source code, so I followed the Sources link to the page that explains how to grab the code from the Eclipse git server. Unfortunately the checkout fails with:
$ git clone git.eclipse.org/c/jetty/org.eclipse.jetty.project.git
Cloning into org.eclipse.jetty.project…
error: The requested URL returned error: 403 (curl_result = 22, http_code = 403, sha1 = 1b72c3a0a79654ac272aea6eb2f3f9aa1d20c7e6)
error: Unable to get pack index git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/objects/pack/pack-4f01a64aa08c03b8317ede41ac67aa3fff82e6cf.idxReply ↓-
simon on said:
$ git clone git.eclipse.org/gitroot/jetty/org.eclipse.jetty.project.git
should work.
Can you please file a bug at https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Jetty so we can update the docs ?
Thanks !
Reply ↓-
Indu on said:
Is there any chance to have some futeares of SPDY to be backported into a new version of HTTP (say, HTTP 1.2) in order to get most of speedy SPDY futeares (but without TLS) into HTTP, that is, in order not to have to do a more radical move ? Is SPDY making mandatory the use of spdy:// addresses ?Thanks.
Reply ↓
-
-
-
Pingback: Jetty-SPDY is joining the revolution! | Webtide Blogs
-
Mario on said:
I was wondering is the java requirement for OpenJDK 1.7 only or it will work with Oracle’s JDK 7 also?
Reply ↓-
Prince on said:
Ian,if you can’t get a consensus that it is a seicruty bug, then the IETF will pick something that you might IYNSHO think is a seicruty bug.Conversely, I’ve argued that sentinel framing is a seicruty vulnerability in websockets because it is susceptible to injection attacks (as is HTTP but no reason to repeat mistakes), yet the WHATWG process goes with your opinion and ships anyway. Can you give me the emails of the WHATWG members so I can appeal your decision?
Reply ↓
-
-
Pingback: 500,000 Requests/Sec? Piffle! 1,000,000 Is Better « The Low Latency Web
-
Pingback: Jetty-SPDY blogged | Webtide Blogs
-
Misaki on said:
IANA had good reasons to useggst the usage of port 80/443, and I’ve actually got few objections to that happening. The upgrade mechanism is there in HTTP for a reason.But the initial upgrade request should be a real HTTP request (not something that just looks like a HTTP request), and the entire internet community need to be involved in the process of developing the upgraded protocol not just the browser vendors.
Reply ↓
Leave a Reply Cancel reply
Your email address will not be published. Required fields are marked *
*
*
*
You may use these HTML tags and attributes: <a class="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
I downloaded both 8.1.2 and 7.6.2 but there is no sign of the spdy code. Is there an additional package that I need to download?