MixinPipeline, or more generally ideas for structuring pipelines.

["Trustin Lee (이희승)"]

Hello Ron,

If a pipeline is parallelized, how do we determine which event from
multiple sub-pipelines should be forwarded to the next joined pipeline?

What about implementing it as a separate ChannelPipeline implementation
instead of modifying Bootstrap?

Thanks for a cool idea!
Trustin

rzo wrote:
> Hello,
> 
> with this post I would like to initiate a discussion on enhancements for 
> pipeline.
> 
> Within my asynch hessian patch I have implemented a "MixinPipeline".
> That is an implementation of a Pipeline, which allows to insert a 
> pipeline or remove a pipeline
> to/from an existing pipeline.
> 
> Another idea I had for the "WAF" example which I posted was to implement 
> "parallel" pipelines.
> eg the ability to send an incoming buffer along multiple parallel 
> pipelines, synchronize their processing, etc.
> 
> I think that implementing generic methods/classes for this kind of 
> operations would be great and will enable
> to use building blocks within netty. It will also enable to use existing 
> pipeline factories from other applications by
> just combining them. Something in the line of:
> 
> bootstrap.addLastPipelineFactory("httpTunnelServerPipeline", ...)
> bootstrap.addParallelPipelineFactory("httpTunnelServerPipeline", 
> "wafPipeline", ...)
> bootstrap.addLastPipelineFactory("asycHessianServerPipeline", ...)
> 
> What do you think ?
> 
> -- Ron
> 
> 
> 
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users

-- 
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/8fe13d08/attachment.bin