users@grizzly.java.net

Re: is grizzly.Context is thread safe ?

From: Oleksiy Stashok <Oleksiy.Stashok_at_Sun.COM>
Date: Fri, 11 Jul 2008 14:11:45 +0200

Hi,

basically, you're right the new API proposed by John in not available
yet.
But if you need Context just to get AsyncWriteQueue - you can use
following:
selectorHandler.getAsyncQueueWriter().write(...)
this will be safe.

Thanks.

WBR,
Alexey.

On Jul 11, 2008, at 13:57 , Survivant 00 wrote:

> the thread :Asynchronous Request Processing with TCPIP look my
> current problem it's really interessting.
>
> I look into the Thread you give me, but look like it's not totally
> ready right ?
>
> I have no problem to use the new API, but where to start from ?
>
>
>
> 2008/7/10 Jeanfrancois Arcand <Jeanfrancois.Arcand_at_sun.com>:
> Salut,
>
>
> Survivant 00 wrote:
>
> Suppose that in a ProtocolFilter in the execute method a create a
> Thread and pass the context to that Thread for further processing.
>
> the context will still be valid when the program will exit the
> execute method ? (or do I have to wait until the processing is
> done ? )
>
> No you cannot do that because the Context get recycled when the
> ProtocolChain complete its execution.....unless your use the new API
> we added this week, or John's proposal. See:
>
> https://grizzly.dev.java.net/issues/show_bug.cgi?id=186
> http://www.nabble.com/Re%3A-Asynchronous-Request-Processing-with-TCPIP-td18391541.html
> http://www.nabble.com/Re%3A-WG%3A--Re%3A-WG%3A--Re%3A-Fwd%3A-WG%3A--Re%3A-WG%3A--Re%3A-WG%3A--Re%3A-WG%3A--Re%3A-Asynchronous-Request-Processing-with-TCPIP-td18360066.html
>
> A+
>
> -- jeanfrancois
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>