Hi gnodet
Its very important for the Apache Camel project that a feature - is implemented fully - is active being supported - is documented - is throughly well tested - etc. In terms of camel-jhc it fails on all accounts. It has been moved to the sandbox area https://svn.apache.org/repos/asf/camel/sandbox/components/camel-jhc/ It was created by you in sep 2007. r574819 | gnodet | 2007-09-12 09:29:20 +0200 (Wed, 12 Sep 2007) | 1 line CAMEL-146: Asynchronous HTTP component And it hasn't been active maintained since. This is the last commit log which has a meaningful change in the component r599946 | gnodet | 2007-11-30 21:20:26 +0100 (Fri, 30 Nov 2007) | 1 line CAMEL-245: JHC componet should be able to create more than one consumer on the same port You are much welcome to pickup this work again. However I would suggest to look at JBoss Netty as it seems like its the new king of the hill as async framework. Maybe its better as the async foundation than Apache HTTP core will be. It seems as Netty got more attraction going on than HTTP core has. On Wed, May 12, 2010 at 1:09 AM, Guillaume Nodet <gno...@gmail.com> wrote: > Sorry, the message has been sent before being finished. > > On Tue, May 11, 2010 at 17:58, Guillaume Nodet <gno...@gmail.com> wrote: > It's been a long time I ad not looked at the asynchronous support in > Camel.I had to do so today and I must say I'm a bit disapointed. > What's the way to have a scalable route using http such as even the > one in the documentation: > from("jetty:http://localhost:8080/service";).to("jhc:http://localhost/service-impl";); > > Given the jetty consumer doesn't use continuations anymore, I don't > understand. > I know the asynchronous API has been refactored and (mea culpa), i > haven't paid much attention to it. > > But I think there has been a big misunderstanding about the purpose of > this api.The goal was not to process things in another thread. The > goal was to be scalable. The AsyncProcessor was only a tool to > achieve that. Maybe not the best one, but still it was working. > > > Now, the only implementation of AsyncProcessor is the > JettyHttpProducer [continued] > Looking at what needs to be done, you would have to do something like: > to("jetty:http://xxx?jetty.async=true";)or something like that which does > not > I don't understand the purpose of the new api. Can somebody shed some light ? > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
