Re: Asynchronous Request Processing with TCPIP

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]

From: Oleksiy Stashok <Oleksiy.Stashok_at_Sun.COM>
Date: Fri, 11 Jul 2008 17:47:13 +0200

>
>>>> @@ -209,8 +217,8 @@
>>>> copyContext.ioEvent = ioEvent;
>>>> copyContext.asyncQueueReader = asyncQueueReader;
>>>> copyContext.asyncQueueWriter = asyncQueueWriter;
>>>> - copyContext.asyncQueueReadable = asyncQueueReadable;
>>>> - copyContext.asyncQueueWritable = asyncQueueWritable;
>>>> + // copyContext.asyncQueueReadable = asyncQueueReadable;
>>>> + // copyContext.asyncQueueWritable = asyncQueueWritable;
>>> Is this a typo?
>> I have it in my trunk and forgot about it. Please see post : https://grizzly.dev.java.net/servlets/ReadMsg?listName=users&msgNo=1363
>
> You are right. Can you file an issue? Alexey, I think we need to fix
> that!
Done :)
Thanks, John!

WBR,
Alexey.

>
>
> A+
>
> -- Jeanfrancois
>
>
>>> Here I recommend we add logging with level set to FINEST. We
>>> should see, when logging turned to FINEST that a Context wasn't
>>> recycled.
>> Yes this is very important, forgot about this.
>> Many Greetings
>> John
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>