I was thinking that for high volume/low latency I would get better performance with the native API instead of JMS, no? My intention is to allow applications on my LAN to subscribe, on a per symbol basis, to the OPRA options price feed.
I was also thinking I'd have to use the native java API to create queues which include the last image caching Carl committed here: https://issues.apache.org/jira/browse/QPID-1248?page=com.atlassian.jira.plug in.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640405#action_1 2640405 Thanks, Andrew -----Original Message----- From: Aidan Skinner [mailto:[email protected]] Sent: Thursday, July 02, 2009 8:50 AM To: [email protected] Subject: Re: qpid + Java without JMS...? On Thu, Jul 2, 2009 at 1:55 PM, Bryan Kearney<[email protected]> wrote: > The only thing I could see is that some of the exchange binding as done > through JMS is a bit odd. I create 3 JMS "Queues" which result in on QPID > queue being created with 2 bindings. If there was a more logical connection > between QPID queue and JMS Queue as well as binding and message selector > then perhaps it might be easier. That seems... odd. I would expect 3 JMS queues named A, B and C to result in 3 Qpid queues called A, B and C bound to amq.direct with routing key of A, B or C respectively. - Aidan -- Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org "A witty saying proves nothing" - Voltaire --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected] No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.375 / Virus Database: 270.12.90/2200 - Release Date: 07/02/09 05:54:00 --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
