cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <...@envoisolutions.com>
Subject Re: Proposal for porting cxf-rt-transport-http from Jetty5 to Jetty6
Date Wed, 20 Dec 2006 16:53:26 GMT
Sounds good to me. Looking forward to having the async http support working!

It'd be good if we could do some testing to make sure that we are able to
handle the large number of connections concurrently too (i.e. 10000). The
one challenge in that is having a working async http client though. Greg
Wilkins (who wrote Jetty) was working on a Jetty HTTP client at my request,
I'll check to see what the status of that is. Otherwise I did write some
testing utilities in asyncweb as well which we might want to consider using.

Regards,
- Dan

On 12/20/06, Willem Jiang <ning.jiang@iona.com> wrote:
>
> Hi,
>
> I am working on porting cxf-rt-transport-http from Jetty5 to Jetty6.
> It is hard to just work directly on the cxf-rt-transport-http module.
> Because  it will take some time to finish this task and some other
> modules such as cxf-rt-bindings-http , cxf-systest  are related to this
> transport-http module.
> My plan is to add cxf-rt-transport-http2 module for this porting, then
> someone can help me to review it.
> My porting schedule will be
> 1. Copy cxf-rt-transport-http to cxf-rt-transport-http2 module
> 2. Modify cxf-rt-transport-http2 to use Jetty6's API for this porting
> 3. Working on my workspace to make sure cxf-rt-bindings-http,
> cxf-systest 's test passed.
> 4. Run the performance test with the cxf-rt-transport-http2
> 5. If performance test good, then rm cxf-rt-transport-http,  mv
> cxf-rt-transport-http2 to cxf-rt-transport-http
>
> Any thought ?
>
> I almost finished 1, 2 on my trunck , now I am working on 3 fixing some
> systest error which caused by my porting.
> If there is no other objection, I will begin to commit 1, 2 tomorrow.
>
> Thanks,
>
> Willem.
>
>
>
>


-- 
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message