[
https://issues.apache.org/jira/browse/CXF-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Gavlin updated CXF-1835:
----------------------------
Description:
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.
was:CXF client should support asynchronous HTTP transport. See
https://issues.apache.org/activemq/browse/SM-1592?focusedCommentId=46039#action_46039
for feedback by Willem Jiang.
Summary: Use Jetty Continuations to implement asynchronous HTTP
processing (was: Support asynchronous client using HTTP transport)
> 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.
