Note that there are some explanatory texts on larger screens.

plurals
  1. POCustom Netty ServerChannel implementation
    primarykey
    data
    text
    <p>I have two systems I'd like to integrate, one which uses a completely in-house networking stack, and one (specifically Flazr) which uses Netty. I want to proxy the Flazr Netty-based RTMP stream over our in-house HTTP stack, to yield a system that speaks RTMPT. </p> <p>To accomplish this, I need a Netty object that acts like a socket, but lets me do all of the "low-level" stuff myself - basically just wrapping the data in HTTP and passing it down our custom networking stack. In other words, I don't want Netty to manage any sockets for me - I want to insert my own stuff between the socket and Netty.</p> <p>I suspect that the right way to go about this is to extend AbstractServerChannel and create a *Factory class, but I'm uncertain as to how the rest of Netty expects data to be flowing through the ServerChannel.</p> <p>My custom ServerChannel need to be able to:</p> <ul> <li><p>Notify Netty when a new client connects via our existing HTTP system</p></li> <li><p>Push data up to Netty, when it arrives</p></li> <li><p>Poll for new messages from Netty, at the request of a client</p></li> <li><p>Clean up Netty state when the HTTP session times out (or the RTMP stream is closed cleanly)</p></li> </ul> <p>Any pointers on how ServerChannel, ServerChannelFactory are to be implemented? I found the javadocs rather lacking in this area.</p> <p>Some specific questions:</p> <ul> <li><p>How should my implementation respond to "InterestOps"-type stuff?</p></li> <li><p>Is ServerChannel.write what is called for messages that come all the way down the stack? What's up with the two different overloads?</p></li> <li><p>How do I need to implement ServerChannel.(dis)connect?</p></li> <li><p>Should I still do all of this stuff through ServerBootstrap, or is that too high-level for this stuff?</p></li> </ul> <p>Thanks!</p> <p>Before anyone asks: YES, I would love to replace our custom networking stack with a Netty-based one, but that's a large engineering task that I'd have a hard time justifying. Baby steps.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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