users@grizzly.java.net

Re: Developing with Grizzly 1.0.x and 1.9.x simultaneously?

From: Igor Minar <iiminar_at_gmail.com>
Date: Tue, 17 Feb 2009 13:00:48 -0800

On Feb 17, 2009, at 12:46 PM, Jeanfrancois Arcand wrote:

> Salut,
>
> Igor Minar wrote:
>> On Feb 16, 2009, at 6:02 PM, Jeanfrancois Arcand wrote:
>>> Salut,
>>>
>>> Igor Minar wrote:
>>>> Hi there,
>>>> so I'm looking at what would be the most efficient way to develop
>>>> grizzly-sendfile for grizzly 1.0.x and 1.9.x in a most efficient
>>>> manner.
>>>> I saw that there is a grizzly-compat module in 1.9.x which looks
>>>> to work just fine for comet apps but it is just not going to cut
>>>> it for my needs.
>>>
>>> Can you come with a list of API you are using from Grizzly 1.0.x?
>>> I can look at it and see if I can emulate them. I'm not 100% I can
>>> fix all of them but I would like to see :-)
>> Brief grep through the source code revealed dependencies on these
>> classes:
>> import com.sun.enterprise.web.connector.grizzly.AsyncExecutor;
>> import com.sun.enterprise.web.connector.grizzly.AsyncFilter;
>
> All renamed to com.sun.grizzly.arp
>
>> import com.sun.enterprise.web.connector.grizzly.Constants;
>> import com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask;
>> import com.sun.enterprise.web.connector.grizzly.LinkedListPipeline;
>> import com.sun.enterprise.web.connector.grizzly.Pipeline;
>> import com.sun.enterprise.web.connector.grizzly.Task;
>> import com.sun.enterprise.web.connector.grizzly.TaskBase;
>
> All under com.sun.grizzly.http, with the exception of Pipeline/
> LinkedListPipeline which has been replaced with ExecutorServices. Is
> it a big problem?

I'll look tonight. Maybe I could create an adapter or something.

thanks

/i

>
>
>> import com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask
>> ;
>> import com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncHandler
>> ;
>
> All renamed to com.sun.grizzly.arp
>
>> import org.apache.coyote.Request;
>> import org.apache.coyote.Response;
>
> under com.sun.grizzly.tcp
>
>> import org.apache.tomcat.util.http.FastHttpDateFormat;
>
> under com.sun.grizzly.util.http
>
> A+
>
> -- Jeanfrancois
>
>
>> /i
>>>
>>>
>>>> Given all the differences between 1.0.x and 1.9.x I'm thinking
>>>> that creating two separate projects might be the best way to go,
>>>> but I wanted to check with you in case someone had to go through
>>>> this already.
>>>
>>> Will be painful IMO as the package were renamed, the Pipeline
>>> dropped, etc.
>>>
>>> A+
>>>
>>> -- Jeanfrancois
>>>
>>>
>>>> cheers,
>>>> Igor
>>>> ---------------------------------------------------------------------
>>>> 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
>>>
>> ---------------------------------------------------------------------
>> 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
>