Rossen, David, I recently changed the behaviour of isAsyncStarted() under protest because it was pointed out to me that we were not following the spec. I feared that it would lead to exactly the kind of problem that you are having here.
Currently I'm thinking that I will revert the default behaviour so that isAsyncStarted will return true until the original dispatch is completed, but add a configuration option to switch on strict adherence to the spec (but I cannot think why anybody would want that). cheers On 13 August 2013 01:03, Rossen Stoyanchev <[email protected]>wrote: > Hi Simone, > > Sure, no worries. Actually David already opened a ticket for this issue: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=413901 > > Maybe the title can be updated now that we have more information. Will > that work? > > Rossen > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > -- Greg Wilkins <[email protected]> http://www.webtide.com Developer advice and support from the Jetty & CometD experts. Intalio, the modern way to build business applications.
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
