Salut,
Oleksiy Stashok wrote:
> Ok.
> Grizzly, by default, doesn't have any resource associated with the
> connection - so it should be safe enough to close connection using method:
> SelectionKeyHandler.cancel(SelectionKey)
I would not touch that as the HTTP object will not be recycled and http
response/connection will be in limbo.
>
> For sure if you're inside some HTTP processor, there could be some HTTP
> specific way of closing the connection. Jean-Francois can advice better
> here.
Done :-)
-- Jeanfrancois
>
> Thanks.
>
> WBR,
> Alexey.
>
> On Jun 20, 2008, at 15:54 , Mark Hig wrote:
>
>>
>> Yes we are. We are using Grizzly 1.8 http and framework.
>> --
>> View this message in context:
>> http://www.nabble.com/Closing-connections-tp18026485p18030095.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
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>