2008/5/9 cmoulliard <[EMAIL PROTECTED]>: > > 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
