Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 67367 invoked from network); 24 Feb 2010 12:51:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Feb 2010 12:51:57 -0000 Received: (qmail 66764 invoked by uid 500); 24 Feb 2010 12:51:57 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 66712 invoked by uid 500); 24 Feb 2010 12:51:56 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 66702 invoked by uid 99); 24 Feb 2010 12:51:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Feb 2010 12:51:56 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Feb 2010 12:51:48 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NkGi7-0005Om-OB for users@camel.apache.org; Wed, 24 Feb 2010 04:51:27 -0800 Message-ID: <27714187.post@talk.nabble.com> Date: Wed, 24 Feb 2010 04:51:27 -0800 (PST) From: Ashwin Karpe To: users@camel.apache.org Subject: Re: Design and ability questions (multiple questions) In-Reply-To: <27711311.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: askarpe@progress.com References: <27711311.post@talk.nabble.com> Hi, First and foremost, I would ask you to read up on JMS and understand messaging concepts. I am sure that will clarify several questions. http://java.sun.com/products/jms/ http://java.sun.com/products/jms/ Then you can check out ActiveMQ and there are several books and guides available both at Apache and several other sites.For example (http://fusesource.com/products/enterprise-activemq/... Check out the documentation tab on the page). These should get you started... Basically Queues are FIFO and Topics are publish/subscribe based communication channels. As for ActiveMQ and switching to Camel, that is not necessary as Camel is part of the ActiveMQ distribution. Cheers, Ashwin... Eibwen wrote: > > I'm completely new to message queues, i've been looking at the ActiveMQ > and Camel website all day but the concepts are not fully clicking for my > specific situation. > I've read most of the FAQs but i think i'm still not seeing how everything > will fit together. I'd love a link to something to help me understand the > protocol some more. > > Specifications: > Messages will be fairly low rate, I'd estimate at peak times 1 a minute > Messages will be fairly large, i'll say average 500kB, up to around 2mB > Messages are a combination of an xml document with a byte stream probably > encoded into that > Right now a single Producer, and 10-20 Locations, in the future 100+ > Locations, and a limited number of Producers > > > The Producer is being built by someone else > The Locations are C# and behind a firewall where they can connect out, but > i cannot connect in > > > Many terms are confusing me still > I don't really understand the virtual destinations and such > When a queue is "foo.bar" is that a subset of "foo" ? > > > Questions (see image below): > 1. Is there any difference in the connection between Topic and Queue? > a. Is it a persistent connection or will I code my client to connect into > the broker every 5 minutes to check if the queue has anything? > b. Or does the broker connect into the client when a message is put into a > queue? (if this is the case my custom filtering/queue piece would have > webservices the clients will connect to) > > 2. To filter/distribute the messages, would either of these be worse?: > a. asking the producer to put each location's messages in a different > queue > b. Or have selectors on each Location pointing to the same queue? > c. Or have the producer put it into a single queue, and have forwardTo > filteredDestination split it into different queues? > d. Is filtering using an XPath on the xml message body horribly > inefficient? > > 3. If i want to do these things, would ActiveMQ be able to accomplish > these/would Camel? > a. Put a copy of each message into a database for indefinite storage > b. Add in new Producers sending messages from other common languages > (giving this portal out to new customers that will send information down > to our Locations) > > 4. If I were to start with ActiveMQ, would i be able to switch to Camel > fairly easily in the future? Or at least without having to ask the > developers of the Producer to change their code? > > > Thank you for reading your message and any help you can give me. > > > http://old.nabble.com/file/p27711311/MessagingLayouts.png > ----- --- Ashwin Karpe, Principal Consultant, PS - Opensource Center of Competence Progress Software Corporation 14 Oak Park Drive Bedford, MA 01730 --- +1-972-304-9084 (Office) +1-972-971-1700 (Mobile) ---- Blog: http://opensourceknowledge.blogspot.com/ -- View this message in context: http://old.nabble.com/Design-and-ability-questions-%28multiple-questions%29-tp27711311p27714187.html Sent from the Camel - Users mailing list archive at Nabble.com.