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
