2015-02-11 10:15 GMT+01:00 Mark Thomas <ma...@apache.org>: > On 11/02/2015 07:58, Romain Manni-Bucau wrote: > > Well in two words if you take the most common example of JAXRS 2 > > continuation (@Suspended) it will do it (doing the link with > > servlets): > > > > -> request 1 -> suspend async context > > -> request 2 -> async context dispatch (resume) > > > > issue is that resume is called from request 2. In other words > > ContainerThreadMarker should check current thread id and not just a > > boolean cause request 2 is in a container thread but this is not > > request 1 thread so you can do request 1 async operations in it. > > > > wdyt? hope it is clearer > > Nope. I still don't see what the problem is or why forcing a dispatch to > a different container thread is any different to continuing to execute > on the current container thread. > > > +1, that looks good enough to me as well so far.
Rémy
