[
https://issues.apache.org/jira/browse/CXF-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642228#action_12642228
]
Daniel Kulp commented on CXF-1835:
----------------------------------
Ron,
Can I get your insight into how you think this should work? I've been
chatting with Sergey a bit this week about this trying to figure out what it
would mean to support the continuations and how it would work, where the
"create continuation" call would be put, how the resume occurs, etc....
On the server side, everything is assumed to be completely synchronous. We
take the request, parse to JAXB or other, find the method, call it, take the
response and write it back. This all neatly fits on a single thread. So,
the question is, how is this changed in order for continuations to fit in there
and what advantage would it give us?
> Use Jetty Continuations to implement asynchronous HTTP processing
> -----------------------------------------------------------------
>
> Key: CXF-1835
> URL: https://issues.apache.org/jira/browse/CXF-1835
> Project: CXF
> Issue Type: Improvement
> Components: Transports
> Affects Versions: 2.0.8, 2.1.2
> Reporter: Ron Gavlin
>
> Current CXF http jetty transport supports injecting a blocking and noblocking
> connector into the JettyEngine and the default connector is noblocking.
> But we don't use the Continuation to implement the async http processing.
> This is a request to use Jetty Continuations to implement this functionality.
> See
> https://issues.apache.org/activemq/browse/SM-1592?focusedCommentId=46039#action_46039
> for feedback by Willem Jiang.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
