camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen" ...@silverbullet.dk>
Subject RE: event:// component - example ?
Date Fri, 09 May 2008 08:34:08 GMT
Good answers that could be added to a FAQ - whats the difference between vm, seda, direct and
event components

Med venlig hilsen
 
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk

-----Original Message-----
From: James Strachan [mailto:james.strachan@gmail.com] 
Sent: 9. maj 2008 09:47
To: camel-user@activemq.apache.org
Subject: Re: event:// component - example ?

2008/5/9 cmoulliard <cmoulliard@gmail.com>:
>
>  For general purpose eventing its probably easier to use either direct:
>  seda: or vm: endpoints
>
>  >> Except that the Event-driven consumer pattern normally consumes messages
>  >> when an event is fired instead to continuously listening for incoming
>  >> messages for direct or vm.
>
>  Is there a difference from thread management between event:// and direct://
>  or vm:// ?

vm: and seda: are basically the same; they both offer asychronous in
memory SEDA queues; they differ in visibility endpoints are visible
inside the same JVM or within the same CamelContext respectively.

direct:// uses no threading; it directly invokes the consumer when sending.

event:// adds a listener to Spring's application events; so the
consumer is invoked the same thread as Spring notifies events.

-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com

Mime
View raw message