activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chir...@apache.org
Subject svn commit: r426036 - /incubator/activemq/site/virtual-destinations.html
Date Thu, 27 Jul 2006 12:05:03 GMT
Author: chirino
Date: Thu Jul 27 05:05:02 2006
New Revision: 426036

URL: http://svn.apache.org/viewvc?rev=426036&view=rev
Log:
Latest export from confluence

Modified:
    incubator/activemq/site/virtual-destinations.html

Modified: incubator/activemq/site/virtual-destinations.html
URL: http://svn.apache.org/viewvc/incubator/activemq/site/virtual-destinations.html?rev=426036&r1=426035&r2=426036&view=diff
==============================================================================
--- incubator/activemq/site/virtual-destinations.html (original)
+++ incubator/activemq/site/virtual-destinations.html Thu Jul 27 05:05:02 2006
@@ -298,9 +298,9 @@
 
 <P>The idea behind virtual topics is that producers send to a topic in the usual JMS
way. Consumers can continue to use the Topic semantics in the JMS specification. However if
the topic is virtual, consumer can consume from a physical queue for a logical topic subscription;
allowing many consumers to be running on many machines &amp; threads to load balance the
load.</P>
 
-<P>e.g. lets say we have a topic called <B>ActiveMQ.Virtual.Orders</B>.
(Where the prefix ActiveMQ.Virtual. indicates its a virtual topic). And we logically want
to send orders to systems A and B. Now with regular durable topics we&apos;d create a
JMS consumer for clientID_A and &quot;A&quot; along with clientID_B and &quot;B&quot;.</P>
+<P>e.g. lets say we have a topic called <B>VirtualTopic.Orders</B>. (Where
the prefix VirtualTopic. indicates its a virtual topic). And we logically want to send orders
to systems A and B. Now with regular durable topics we&apos;d create a JMS consumer for
clientID_A and &quot;A&quot; along with clientID_B and &quot;B&quot;.</P>
 
-<P>With virtual topics we can just go right ahead and consume to queue <B>ActiveMQ.Virtual.A.Orders</B>
to be a consumer for system A or consume to <B>ActiveMQ.Virtual.B.Orders</B> to
be a consumer for system B.</P>
+<P>With virtual topics we can just go right ahead and consume to queue <B>Consumer.A.VirtualTopic.Orders</B>
to be a consumer for system A or consume to <B>Consumer.B.VirtualTopic.Orders</B>
to be a consumer for system B.</P>
 
 <P>We can now have a pool of consumers for each system which then compete for messages
for systems A or B such that all the messages for system A are processed exactly once and
similarly for system B.</P>
 
@@ -314,8 +314,8 @@
     </DIV>
     <DIV id="site-footer">
           Added by     <A href="http://goopen.org/confluence/users/viewuserprofile.action?username=jstrachan">James
Strachan</A>,
-    last edited by     <A href="http://goopen.org/confluence/users/viewuserprofile.action?username=jstrachan">James
Strachan</A> on Jul 14, 2006
-                  &nbsp;(<A href="http://goopen.org/confluence/pages/diffpages.action?pageId=9061&originalId=9063">view
change</A>)
+    last edited by     <A href="http://goopen.org/confluence/users/viewuserprofile.action?username=jstrachan">James
Strachan</A> on Jul 27, 2006
+                  &nbsp;(<A href="http://goopen.org/confluence/pages/diffpages.action?pageId=9061&originalId=9284">view
change</A>)
               
       (<A href="http://goopen.org/confluence/pages/editpage.action?pageId=9061">edit
page</A>)
     </DIV>



Mime
View raw message