Re: [jetty-user] SPDY failures

> From: Howard Lewis Ship <[email protected]>
>
> I'm attempting to set up a Tapestry 5 application on Jetty
> 8.1.4.v20120524, Mac OS X Lion, JDK 1.7, Chrome.
>
> Most features work fine: HTTPs converts into SPDY (I'm using the SPDY
> Indicator plugin for Chrome, and it turns green).
>
> My page's HTML markup comes down fine, as does most of the related
> images and stylesheets.
>
> I'm having one problem though ... some of my larger JavaScript files
> are coming through truncated.  In production mode, Tapestry aggregates
> many small JavaScript files into a single virtual file.  This appears
> to be failing, and I'm seeing exceptions on my server side, and
> truncated JavaScript on the client side.

There were problems regarding the handling of SPDY flow control, and
handling large files, indeed.

Both are fixed in the current Jetty 7 HEAD. Can you give that a spin ?

> Thanks in advance for any help or insight.  This is awfully bleeding edge stuff!

Thanks for trying it out.
Yes, it's bleeding edge, we're eating our own food at
http://www.webtide.com (runs on SPDY), but there still are few rough
edges.

Latest HEAD should be much better though.

Let us know.

Simon
-- 
www.webtide.com
Developer advice, services and support
from the Jetty & CometD experts.
----
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email