On 04/23/2012 04:17 PM, marcelloraffaele_at_gmail.com wrote:
> Ok thanks, i'll try to answer using "write" in Filter...
>
> but for me isn't clear how i can manage timeouts and ritransmission
> from Filter!
For example you can use ScheduledExecutorService. Once timeout expires -
send retransmission request.
> Isn't clear how grizzly manage Filters, how many instances of filter
> class are user for connections (each for socket?)
Filters are stateless, so only 1.
> and how grizzly
> decide the lenght of a packet/message before notify the filter chain?
Grizzly doesn't decide this, it will call FilterChain if at least 1 byte
is available for reading.
> I'm sorry but i still haven't found where to read it!
No problem :)
WBR,
Alexey.