Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Only example I could find on Netty and SPDY is a test code for <a href="https://github.com/netty/netty/blob/master/codec-http/src/test/java/io/netty/handler/codec/spdy/SpdySessionHandlerTest.java" rel="nofollow">SessionHandler</a> and <a href="https://github.com/netty/netty/blob/master/codec-http/src/test/java/io/netty/handler/codec/spdy/AbstractSocketSpdyEchoTest.java" rel="nofollow">socket echo test</a>. I'm yet to make this thing running, but Your client should make pipeline consisting of <code>SpdyFrameCodec</code>, <code>SpdySessionHandler</code> and your handler.</p> <p>Your handler should be modeled after <code>EchoHandler</code> in session test, because that way <code>SpdySessionHandler</code> does job of decoding raw frames into more meaningful ones and does some things as required by SPDY protocol.</p> <p>As for fall-backing, there are <code>SpdyHttpCodec</code> in snapshot version of the Netty that translates from SPDY to HTTP. That way you can build your client handler in terms of HTTP and receive messages that came either through SPDY or HTTP transparently. To do this it is required to implement something similar to <a href="http://netty.io/docs/stable/xref/org/jboss/netty/example/portunification/package-summary.html" rel="nofollow">port unification</a> example.</p> <p>All that said. There is room for few utility classes/handlers to make all of this an "out of the box" experience. I wanted to make a working example, but am lacking time right now for it, and there would be too much code to simply paste it here as answer.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload