users@grizzly.java.net

Re: WG: Re: WG: Re: WG: Re: Asynchronous Request Processing with TCPIP

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Tue, 08 Jul 2008 11:58:37 -0400

Salut,

John ROM wrote:
> Hi Jeanfrancois,
>
> So I really now think that I just should and do a :
> (in com.sun.grizzly.filter.MessageDispatcher)
>
> final Context copyContext=workerCtx.getController().pollContext(workerCtx.getSelectionKey());
> workerCtx.copyTo(copyContext);
>
> // and then when I am finished
> //
> copyContext.getController().returnContext(copyContext);

What about this proposal:

When calling suspend/resume, we never recycled the object. If an
implementation wants to recycle those, we can either add a new API like
recycleAndReturn(), which will internally call the
controller.returnContext().

What peoples thinks?

A+

-- Jeanfrancois



>
> Many Greetings John
>
>
>