single channelpipeline vs multiple channelpipelines
anthony_w
awwold69 at hotmail.com
Mon May 24 15:59:32 EDT 2010
I think what I missed in the samples and api was a clear understanding of the
use of an ExecutionHandler. After digging through many forum posts I now
see that I should use an EH to separate my I/O from my business logic. And
that the EH will have its own executor. So I'm going to have a single
pipeline and manage the "hosting" of my multiple devices in a
java.util.concurrent.ConcurrentHashMap. Once my business logic handler
received the incoming request, it can look up the device in the map by some
key.
--
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/single-channelpipeline-vs-multiple-channelpipelines-tp5010378p5095524.html
Sent from the Netty User Group mailing list archive at Nabble.com.
More information about the netty-users
mailing list