Hi Peter

On Wed, Jul 15, 2009 at 5:59 PM, Peter Jones<[email protected]> wrote:
> Just to be clear, the "com.sun.jini.jeri.tcp.useNIO=true" mode of the
> JERI TCP endpoint implementation still uses multiple threads to
> dispatch remote invocations-- RMI behavior would be drastically
> impacted if it only used a single thread for that (for reasons like
> you describe below).  It just uses a single thread for performing I/O
> operations, at least those that "would block".

Do you happen to know if there is documentation from the time when the
NIO support was added, for example, regarding benchmarks, problems,
etc.?


Thanks
Patrick

Reply via email to