I guess the part of the broker which replays all pending messages to a
new consumer on a queue needs to be changed to say - 'ah if the
consumer is only for a specific mesage ID then just replay that one
message'.
Maybe we just need a new operation on a broker to allow a specific
message ID to be consumed?
Either would be awesome. I'm happy to try and figure it out and
contribute a patch if you'd like. If so, any hints would be great :)
cheers,
j.
On 8/4/06, James Strachan <[EMAIL PROTECTED]> wrote:
On 8/4/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> On 8/4/06, Jamie McCrindle <[EMAIL PROTECTED]> wrote:
> > Thanks Hiram,
> >
> > I'll definitely look into that. How difficult do you think it would be
> > just to optimise the selector "JMSMessageID = '" + id + "'"?
> > presumably there are some hooks for that already (e.g. indexes in
> > db's)?
> >
>
> Yep.. you just need to add something the analyzes the selector and
> avoids the queue scan. Geez this starting to should like DB.
I guess the part of the broker which replays all pending messages to a
new consumer on a queue needs to be changed to say - 'ah if the
consumer is only for a specific mesage ID then just replay that one
message'.
Maybe we just need a new operation on a broker to allow a specific
message ID to be consumed?
--
James
-------
http://radio.weblogs.com/0112098/
