[CXF-1835] Use Jetty Continuations to implement asynchronous HTTP processing

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.8, 2.1.2
• Fix Version/s: 2.0.10, 2.1.4
• Component/s: Transports
• Assignee: Sergey Beryozkin
• Reporter: Ron Gavlin
• Created: 30/Sep/08 15:37
• Updated: 02/May/13 02:29
• Resolved: 24/Nov/08 09:38

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.

Issue Links

• is depended upon by: CXF-1911 Implement asynchronous support in CXF Server
• is depended upon by: CXF-1913 Implement asynchronous support for HTTPS transport in CXF Server