[
https://issues.apache.org/jira/browse/CXF-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647307#action_12647307
]
Ron Gavlin commented on CXF-1835:
---------------------------------
Hi Sergey,
I am interested in asynchronous server-side processing in general, including
the following transports in priority order: jms, http, https. Originally, I
referenced the http transport in the title of this JIRA because I assumed the
async jms transport was already available. After discovering that was not the
case, I wasn't exactly sure how I should proceed. Should this JIRA be re-titled
to encompass a generic solution for all transports? Or should I create separate
tickets for the jms transport work and the https transport work? What do you
think?
/Ron
> 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.
