On 06/11/06, Vinod Panicker <[EMAIL PROTECTED]> wrote:
Did you try having multiple SocketIoProcessors for the acceptor?
IIRC that should provide more concurrency to your application, and
should alleviate the starvation problem.
I don't think it would. The problem is that for a given socket, reads
and writes are handled by a single SocketIoProcessor. Reads and writes
cannot happen concurrently *for a given socket*.
Also the current SocketIoProcessor is biased for writes, which can
cause problems if a server app has to buffer up responses to be sent
back to a client that is doing a sustained period of writes.
RG
