UDP woes...

["Trustin Lee (이희승)"]

fps wrote:
> 
> Trustin Lee wrote:
>> ChannelPipelineCoverage for documentation purposes only.  In UDP, still
>> a single handler instance will handle all incoming packets to the same
>> port.  Read the Javadoc of ChannelPipelineCoverage.
>>
> 
> It doesn't tell me an awful lot... Ok UDP will have one channel handling all
> clients so the pipeline is the same for all clients.
> Unless I start prefixing all client messages with message type ids to
> indicate which handler needs to process a given type of message I don't see
> how I can handle multiple clients. Also as part of my TCP protocol the
> pipeline gets dynamically changed upon messages being processed. For example
> once the handshake has been completed for a channel, some handlers get
> removed and some get added. With UDP I can't really reuse this mechanism
> because everything comes on the same channel and I can't assume that we
> don't need such and such handlers anymore.

Good point.  It might be a good idea to provide an easy way to implement
a connection-oriented transport on top of a connectionless transport
such as UDP.  I'm not sure it can be generalized enough though.  Let me
list this in the road map and keep thinking about this..

Thanks a lot!
Trustin

-- 
what we call human nature in actuality is human habit
http://gleamynode.net/


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/netty-users/attachments/20100125/66aa885d/attachment.bin