On Wed, Mar 11, 2009 at 10:55 AM, Neil Rutherford wrote:
> With this approach:
>
> from(tcp).process(controlMessage).to("direct:submsg");
> from("direct:submsg").split().parallelProcessing().to(client socket).end();
>
> How does the threading work?
>
> Will a new thread be spawned for each new req
With this approach:
from(tcp).process(controlMessage).to("direct:submsg");
from("direct:submsg").split().parallelProcessing().to(client socket).end();
How does the threading work?
Will a new thread be spawned for each new request into the tcp
endpoint and will that thread then spawn a new thread
e it load service messages from DB and process them.
>
> socket -> rendezvous -> content based router -> submessage processor ->
> rendezvous -> ...
>
> I'm probably not being very clear, so feel free to ask specific questions.
>
> thanks,
>
> Neil
>
ay also be the wrong word, its just what we call it here.
--
View this message in context:
http://www.nabble.com/trying-to-implement-rendezvous-tp22449660p22449660.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
