cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] Commented: (CXF-1835) Use Jetty Continuations to implement asynchronous HTTP processing
Date Thu, 13 Nov 2008 15:11:44 GMT


Sergey Beryozkin commented on CXF-1835:

Hi Ron

I'd prefer going with 3 separate tasks. They might end up being solved in one merge, not sure.
Most lilkely http & jms will be tackled in one go and then https one can be handled seperately
as the work to be done for https, after the http task has been completed, will have nothing
to do with continuations per se but with replacing a SSLSocketChannel and given that https
one is the last in the priority queue I guess it can be tackled a bit later.

So may be you can crate a master task, and have this JIRA as the first task, and then create
2 more jiras, one for JMS and one for HTTPS ?

Cheers, Sergey

> 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