Hi,
>
> Hi, I am just starting to have a look at Grizzly and am interested
> in the
> asynchronous processing of messages. I have a requirement that
> means that a
> request (processTask) in Grizzly may be timed out on a separate
> thread. I
> want to be able to close the connection that is open is Grizzly from a
> separate thread without sending a response. How can I do this.
Can you pls. describe the logic of your application, where you want to
decide to close the connection?
> Also, what will happen in Grizzly if Grizzly is part way through
> writing a
> response down a connection when an attempt is made to close that
> connection?
Grizzly, by default, doesn't have any specific logic on that. So if
you write to the socket (channel) and other thread closes it - it
depends on JDK implementation how it will process that.
Thanks.
WBR,
Alexey.
>
>
> Thanks for any help you can give.
> --
> View this message in context: http://www.nabble.com/Closing-connections-tp18026485p18026485.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
>