Hello Harsha,
think currently in Grizzly there is no functionality you're asking.
The way I see it could be implemented - extending ReadFilter with
overriding postExecute method.
May be others have better ideas?
Thanks.
WBR,
Alexey.
Harsha Godugu wrote:
> Hi Jeanfrancois,
>
> How does Grizzly v1.6.0 handle the following scenario:
> The underlying channel gets closed (unexpectedly, due to say some
> network problem.. or loose contact etc.. and then backs up to live )
> while reading data using ReadFilter. Consider this can happen on both
> client and server side.
>
> I see that, the ReadFilter class sets an attribute in Context, in
> case of an exception. But that same attribute is removed in the
> postExecute(..) method of ReadFilter. How does user of Grizzly know,
> if there is an IO exception (ChannelClosedException..) while reading
> data using the filter? Do we have state listeners of connection to
> monitor connection state? (Similar to Controller state!)
>
> Thanks,
> Harsha
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>