Alexander Christian wrote:
On Fri, 14 Nov 2008 15:49:33 +0100, Alexander Christian <[EMAIL PROTECTED]>
wrote:
Hmm, I changed to following code
--code--
acceptor.getFilterChain().addFirst("executor", new
ExecutorFilter(filterchainWorkerPool));
--/code--
to this one:
--code--
OrderedThreadPoolExecutor c = new OrderedThreadPoolExecutor();
acceptor.getFilterChain().addFirst("executor", new ExecutorFilter(c));
--/code--
Now it works again, also with hughe messages. But what's the benefit?
the encoding will be executed using a thread from a pool, allowing many
// decoding to be done.
As
far as I understood the apidoc, the events are forwarded in the same order
they arrive. So the whole stuff seems to be "synchronized" again and the
streams did not get corrupted.
only on a single session. But as you mau have many sessions, and a
limited number of processors, adding an executorFilter will spread the
sessions decoding on many threads, potentially increasing the scalability.
So what's then the benefit of the
OrderedThreadPoolExecutor?
Mainly to keep the packates ordered within a single session.
I'm a little bit confused about this.
It's confusing, I agree. Lack of samples and spare doco does not help too...
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
