On Mon, Feb 6, 2012 at 16:22, Jesse McConnell <
jesse.mcconnell@xxxxxxxxx> wrote:
> see:
http://wiki.eclipse.org/Jetty/Feature/Continuations or servlet
> 3.0 for async servlets
>
> what your running into is that once a request enters into the servlet
> api, it has a thread allocated to it for its lifetime in the
> servlet-api prior to servlet 3.0 where the concept of async was
> supported. continuations is a mechanism that allows for a similar
> mechanic on jetty in servlet 2.5
>
> and yes, jetty is multithreaded
>
> cheers,
> jesse
>
> --
> jesse mcconnell
>
jesse.mcconnell@xxxxxxxxx
>
>
>
> On Mon, Feb 6, 2012 at 08:47, Christian Wolfgang <
chw@xxxxxxxxxx> wrote:
>> Hi.
>>
>> I have a servlet that initiates some work with a post request and with
>> a get request I can get its status. But when I try to get its status,
>> the request is first processed when the post request is done.
>> But if i break up the post request in bits, with Thread.sleep(), the
>> get request can be processed.
>>
>> I thought jetty was multithreaded? Am I wrong or am I doing something wrong?
>>
>> Thanks.
>>
>> Christian
>> _______________________________________________
>> jetty-dev mailing list
>>
jetty-dev@xxxxxxxxxxx
>>
https://dev.eclipse.org/mailman/listinfo/jetty-dev
> _______________________________________________
> jetty-dev mailing list
>
jetty-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/jetty-dev
_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-dev