Here are some examples of message flows you'll be able to express in the configuration:
"when a persistent message arrives on this server and is addressed to any address beginning with "jmsqueues.*", please route it round-robin style to any of the following nodes: .., ..,"
"when a non-persistent message arrives on this server and is addressed to any address beginning with "jmstopics.*", please route it to ALL of the following nodes: .., ..,"
"when a non-persistent message arrives on this server and is addressed to any address beginning with "jmstopics.*", please route it to ALL of the following nodes discovered using UDP discovery on port xyz"
"when a message arrives on this server, and has a property "office-name" = "London", route it over the internet using HTTP to the server at address abc, if the connection is down, store it locally and forward it on when the connection comes back up".
Here are some examples of message flows you'll be able to express in the configuration:
"when a persistent message arrives on this server and is addressed to any address beginning with "jmsqueues.*", please route it round-robin style to any of the following nodes: .., ..,"
"when a non-persistent message arrives on this server and is addressed to any address beginning with "jmstopics.*", please route it to ALL of the following nodes: .., ..,"
"when a non-persistent message arrives on this server and is addressed to any address beginning with "jmstopics.*", please route it to ALL of the following nodes discovered using UDP discovery on port xyz"
"when a message arrives on this server, and has a property "office-name" = "London", route it over the internet using HTTP to the server at address abc, if the connection is down, store it locally and forward it on when the connection comes back up".
For those of you who have been following my various ramblings on AMQP, specifically on the whole Exchange-Routing semantics (which overflowed into Ben Hood's blog), on Ben and Alexis' request I've started a thread over on rabbitmq-discuss to try to hash things out in a more direct format rather than duelling bloggers. If you think you have something to add, or just want to watch things unfold, I recommend you take a gander over there.
presentation to the technical management and architects at a Very Large Web Property on messaging systems, AKA Message-Oriented Middleware, AKA Enterprise Services Bus, etc