On 18 January 2013 14:33, Hiram Chirino <[email protected]> wrote:
> On Thu, Jan 17, 2013 at 4:51 PM, Robbie Gemmell <[email protected] > >wrote: > > > > The only time your really want to do the id preservation is when a > > > 'foreign' jms message is being sent. At least this is what ActiveMQ > > does. > > > If a Qpid JMS message is sent on an ActiveMQ sender, the message id > will > > > be preserved. > > > > > > > > How do you handle the situation above where the message was foreign, just > > let it duplicate the ID for the foreign message, given it it would be > ever > > so slightly slightly less usual to send the foreign message twice? > > > Correct. Then again, ActiveMQ also has dup detection logic, a subsequent > send /w the same message id would get dropped. > > Ah I see. The Qpid brokers dont currently de-dupe messages, but we could potentially add some client-side ability when dealing with messages from foreign providers that e.g allowed for a choice between throwing an exception to let them know they cant send again or allowing the same id to be used if you attempted multiple sends on the foreign message with the 'preserve id' option enabled (since they aren't strictly duplicate messages but rather different messages with non-unique ids...ick).
