Hi,
> Thanks!
> 1. How about other events?
> 2. Is there any guarantee that what events will happen before what?
Accept, Connect before READ/WRITE/CLOSE
> 3. If "handleAccept" takes long time, will the subsequent events like
> "handleRead" not be fired until handleAccept is done?
Yes. ACCEPT/CONNECT events are called from Selector thread, so they
should be fast.
> 4. Is it guaranteed that handleRead for the previous packet finishes
> before
> the subsequent handleRead?
Yes.
READ/WRITE events will be called sequentially.
WBR,
Alexey.
>
>
>
>
>
> Oleksiy Stashok wrote:
>>
>> Hi,
>>
>>>
>>> I tried to use Grizzly 2.0 M1 but I found that Filter's
>>> handleAccept /
>>> handleRead don't get fired in order since it uses threadpool. For
>>> example,
>>> if I connect to Grizzly and write message to it right away, it's
>>> possible
>>> that "handleRead" is called before "handleAccept". What should be
>>> the
>>> correct to handle it?
>> You're right, ACCEPT event could come after READ or WRITE event.
>> I've just fixed it on trunk.
>>
>> Thank you.
>>
>> WBR,
>> Alexey.
>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Grizzly-2.0-M1%3A-Filter-ordering-tp23383056p23383056.html
>>> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Grizzly-2.0-M1%3A-Filter-ordering-tp23383056p23398090.html
> Sent from the Grizzly - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>