You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by nitingupta183 <ni...@gmail.com> on 2008/10/01 06:24:28 UTC

Re: Camel + Seda

Hi James,

Bu process I meant, the application process i.e. inside the same JVM.

Thanks for the clarification.

Regards,
Nitin


James.Strachan wrote:
> 
> 2008/9/27 nitingupta183 <ni...@gmail.com>:
>> Hi Claus,
>>
>> I intend to use SEDA endpoint to asynchronously call a process from
>> another
>> process as I think that the called process can be time intensive. So
>> unless
>> it is not made to act in the async mode, then app users' wait time is
>> gonna
>> go rise.
> 
> Sounds good.
> 
> BTW when you say 'process' do you mean operating system process or are
> we talking about in the same JVM here. If its separate processes then
> the seda endpoint won't work (it only works for producers and
> consumers within the same JVM) - instead try looking at JMS or file
> endpoints...
> http://activemq.apache.org/camel/jms.html
> 
> 
>> Is it a valid use case for using SEDA? As you can see, my purpose is just
>> to
>> make the called process work in its own thread so that the calling thread
>> can return in quick time.
> 
> Definitely!
> 
> -- 
> James
> -------
> http://macstrac.blogspot.com/
> 
> Open Source Integration
> http://open.iona.com
> 
> 

-- 
View this message in context: http://www.nabble.com/Camel-%2B-Seda-tp19688151s22882p19754303.html
Sent from the Camel - Users mailing list archive at Nabble.com.