On Feb 18, 2009, at 10:59 AM, Igor Minar wrote:
>
> On Feb 17, 2009, at 1:00 PM, Igor Minar wrote:
>
>>
>> On Feb 17, 2009, at 12:46 PM, Jeanfrancois Arcand wrote:
>>>
>>>> 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.
>
> So I had a look at this last night, and I should be able to get it
> to work even without Pipeline.
>
> I started working on an inverse grizzly-compat module, which would
> allow me to develop against 1.9.x api, but make it run with the
> compatibility layer on top of 1.0.x as well.
This turned out to be just way too much work for relatively small
benefit (being compatible with glassfish v2).
I decided that grizzly-sendfile 0.3+ will be 1.9.x compatible, which
means that it will run only on grizzly 1.9.x standalone and gf3.
I'm excited about the changes in the api that grizzly made from 1.0 to
1.9. I think that this is the best direction for the grizzly-sendfile
project.
/i