cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Gavlin (JIRA)" <>
Subject [jira] Commented: (CXF-1835) Use Jetty Continuations to implement asynchronous HTTP processing
Date Thu, 23 Oct 2008 23:55:46 GMT


Ron Gavlin commented on CXF-1835:

Would it be appropriate to offer a boolean synchronous flag that is true by default? When
set to false, this alternate async behavior would be enabled. 

I agree that CXF should be optimized for the typical use case where low latency is of utmost
importance. When CXF is used as a binding component in SMX, the servicemix implementation
tends to be an integration process which is longer running. So, allocating one thread per
request is not scalable. So, I would think the typical SMX use case would want the synchronous
flag set to false. Offering this alternate behavior would seem useful when CXF is used as
an SMX JBI Consumer. Does that make sense?


> 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