cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] Commented: (CXF-1835) Use Jetty Continuations to implement asynchronous HTTP processing
Date Fri, 24 Oct 2008 01:05:44 GMT


Daniel Kulp commented on CXF-1835:

The issue is that I don't see how this would change anything in CXF.   Basically, we would
have to create the exchange and put it on our workqueue and create the continuation.   The
Jetty thread would be released back to Jetty, but that single request would still consume
the workqueue thread.   It doesn't change anything other than moving it from the Jetty thread
to a thread on the workqueue.  

> Use Jetty Continuations to implement asynchronous HTTP processing
> -----------------------------------------------------------------
>                 Key: CXF-1835
>                 URL:
>             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
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.

View raw message