camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Strachan <james.strac...@gmail.com>
Subject Re: [DISCUSS - Camel 2.0 - Internal API reworkings] - Channel and AsyncProcessor
Date Fri, 24 Apr 2009 12:36:19 GMT
2009/4/24 Claus Ibsen <claus.ibsen@gmail.com>:
> On Fri, Apr 24, 2009 at 11:23 AM, Guillaume Nodet <gnodet@gmail.com> wrote:
>> The goal of the AsyncProcessor is to not block the calling thread when
>> using an InOut exchange mostly.
>> For example, if you invoke a web service which takes a long time to
>> answer, you don't really want the thread to be blocked for a few
>> seconds simply waiting for the answer: it just does not scale welll.
>> Not sure if the UnitOfWork stuff is sufficient to cover the InOut stuff.
> I do think we need a redesigned API for this that leverages the JDK
> concurrency stuff much more, e.g. the Future.
>
> And the current implementation is broken. And when you get the done
> callback, how do you get the result?

Exchange.getOut() ?

The Exchange object kinda is the 'future' object.
-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://fusesource.com/

Mime
View raw message