Problem of hundreds ChannelHandler for one connection

["이희승 (Trustin Lee)"]

I'm considering to provide a way to reduce the depth of call stack even 
when the pipeline has many handlers inside in Netty 4, using a 
technique similar to tail recursion.  However, in Netty 3, you'd better 
keep the number of handlers in a pipeline smaller.

On Wed 11 May 2011 01:45:25 PM KST, Marc-André Laverdière wrote:
> Hello,
> 
> I think you are trying to do something with Netty that it wasn't designed to to.
> AFAIK, the pipeline stuff is to make transformations on the
> input/output so that your handler can easily deal with things. So
> Netty helps you splitting frames and decoding it to an object form of
> your liking and all such things.
> 
> However, it comes a time when you should just let a handler... handle
> ... the request :)
> 
> On 5/9/11, magiceye <magiceye at 163.com> wrote:
>> For some application situation like network game, it will be hundreds
>> self-defined package (for example, attack, trade with other people and so
>> on). By typical sytle in netty, the logical operation is a ChannelHandler in
>> pipe. So if I have hundreds self-defined package, there will be hundreds
>> ChannelHandler in pipe, each one deal with one type of request. It seems
>> very hard to use context to control the order of ChannelHandlers dynamic
>> because they are too much.
>>
>> Should I implement myself "event-callbacking" mechanism or there are some
>> other ways to do it by netty which I don't know yet?
>>
>>
>> --
>> View this message in context:
>> http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Problem-of-hundreds-ChannelHandler-for-one-connection-tp6343673p6343673.html
>> Sent from the Netty User Group mailing list archive at Nabble.com.
>> _______________________________________________
>> netty-users mailing list
>> netty-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/netty-users
>>