I have a situation where a request comes in to Jetty, and goes through
two other routes and queues before a response is generated that allows
the HTTP response to be sent to the caller. I'd like to be able to
force Jetty into using continuations so it doesn't park a thread while
those other routes are going.
The async page on the wiki suggests a usage pattern that would allow
Jetty to operate asynchronously, but it's short on specifics, and it's
not clear I can coerce my logic into that pattern anyway.
It was suggested on IRC that I file a Jira, but I just thought I'd
collect any other thoughts on this before doing so.
I guess I'm thinking it wold be nice to have like a
"continuations=true" type parameter on a Jetty endpoint that would
explicitly tell it to go into asynchronous mode.
Thanks,
Aaron
