Jetty 7 Continuations: How to *not* redispatch the request?

Posted by Don Werve on Stack Overflow See other posts from Stack Overflow or by Don Werve
Published on 2010-03-20T04:31:23Z Indexed on 2010/03/20 4:41 UTC
Read the original article Hit count: 334

Filed under:
|
|

I'm using Jetty 7 continuations to implement some asynchronous processing. What I'm trying to do is start off the continuation (via .suspend()), and then hand the continuation off to some other object that will compose the response, which works fine. But Jetty keeps redispatching the response (with isInitial = false) to the servlet, and I don't want or need that, because the response is being dealt with by some other object.

So, I'd like to find a way to explicitly not redispatch the request on timeout or expire, because I'm using an event-driven series of callbacks to actually produce the response.

© Stack Overflow or respective owner

Related posts about java

Related posts about jetty