Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.213.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1390924116.91621.YahooMailNeo@web125404.mail.ne1.yahoo.com>
References: <1390858556.23972.YahooMailNeo@web125406.mail.ne1.yahoo.com>
 <1390922195387-5746552.post@n5.nabble.com>
 <1390924116.91621.YahooMailNeo@web125404.mail.ne1.yahoo.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 28 Jan 2014 16:50:47 +0100
Message-ID: 
 <CAGB5yN=VJbjsgRfYandWWw62Go7YfErFr_mnHdJP=fi+AzDiQQ@mail.gmail.com>
Subject: Re: Pros and cons of using choice as opposed to having separate
 endpoints
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Hi

Just one thing about 1 route vs N routes.
If you have N routes then you can individually control these routes to
suspend/resume them.


On Tue, Jan 28, 2014 at 4:48 PM, Shing Hing Man <matmsh@yahoo.com> wrote:
>
>
> Hi John,
>
>
> Thanks for mentioning the point below.
>
>> the incoming message if it doesn't match. I.e. if a non-matching .from() is
>> first to pull the http request, will the http request still be available for
>> the correct endpoint to process? Asked another way, what does a .from(http)
>> endpoint do with non-matching http requests?
>
> The multiple route option is in production already and from what I have observed in our production system,
> Camel is clever enough to match an incoming message with  the correct route. We have not seen any missing
> incoming messages.
>
> Shing
>
>
>
>
>
>
> On Tuesday, January 28, 2014 3:17 PM, John Kramer <jakramer@ascenditsolutions.com> wrote:
>
> Hello Shing,
>
> I'm in somewhat of a similar situation except I'll be pulling messages from
> multiple email accounts for the from endpoint. I should add that I'm
> relatively new to camel so please factor that into my responses to follow.
>
> My first question regarding the use of the multiple route option is that
> given the different .from()'s are monitoring the same port is the status of
> the incoming message if it doesn't match. I.e. if a non-matching .from() is
> first to pull the http request, will the http request still be available for
> the correct endpoint to process? Asked another way, what does a .from(http)
> endpoint do with non-matching http requests?
>
> For my situation, there is a great deal of commonality in the needed routing
> and processing of the incoming messages so I am planning on using a single
> route. I believe this will result in a camel application that is easier to
> maintain in the long run.
>
> Best,
> John
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Pros-and-cons-of-using-choice-as-opposed-to-having-separate-endpoints-tp5746510p5746552.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Make your Camel applications look hawt, try: http://hawt.io