[
https://issues.apache.org/jira/browse/CXF-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642409#action_12642409
]
Sergey Beryozkin commented on CXF-1835:
---------------------------------------
Ron, just would like to clarify :
Are you thinking of doing explicit continuations in the application code and
expect CXF support handling continuation.suspend() done from the application
code ( like Dan described above ) ?
Or you're only after ensuring that when CXF is used as a SMX BC, it releases
Jetty threads asap for them to do some other SMX work ? We reckon that it might
work (with explicit configuration involved) but as Dan said, it would simply
lead to replacing a Jetty thread with an internal CXF thread and thus, as far
as the resource consumption is concerned, it's not obvious what will be gained
in the end ?
> 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.
