users@grizzly.java.net

Re: CurrentOpType is not set in the context when executed in a worker thread

From: Oleksiy Stashok <Oleksiy.Stashok_at_Sun.COM>
Date: Tue, 01 Apr 2008 17:11:11 +0200

we can use SelectionKey.readyOps().
But, IMHO, we need to fix Context.currentOpType to have correct value?

Thanks.
WBR,
Alexey.

On Apr 1, 2008, at 13:27 , Ramesh Parthasarathy wrote:

> Hi,
> In the controller if delegateToWorkerThread is true, then the
> curentOpType is not set on the context. The optype is set (in the
> onWriteInterest or onReadInterest of selectorhandler) only when
> async mode is enabled or there is a callback handler.
> I feel that Context.OpType should also have another type called
> "OP_READ_WRITE" which would indicate that both operations were
> selected. Would be useful especially when the
> handleReadWriteConcurrently is true.
>
> Please let me know if i should write an Issue for this.
>
> Thanks
> -Ramesh
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>