What I am trying to do is create a notification mechanism for interested servers. For example, there is a system flag (which defines a system behavior) which would be published. Any consumer interested in that system flag would get latest system state by consuming a published message.
New subscribers would not need to access any previous messages, only the most recent. I'm going to look into the Subscription Recovery stuff a bit. Looks like the Retroactive Consumer might do the trick. Thanks. Kit James.Strachan wrote: > > Could you describe your requirements a little more just to check I > understand. You basically want a topic which always sends 1 message to > every > consumer when they start subscribing and this message changes over time > right? When the message changes is it sent to all consumers active, or is > it > just sent to new subscribers? > > You could go with durable subscribers; but then that means all messages > sent > to a topic are persisted until your consumer restarts. It seems like you > just want 'the last one' available to new consumers? > > So maybe using a Subscription Recovery Policy might be cleaner... > http://activemq.org/Subscription+Recovery+Policy > > so that you can decide what message is sent to new consumers using a > cached > 'last image' that is sent when new consumers start; then you just send a > message to everyone when this 'last image' changes? > > > On 5/4/06, kitplummer <[EMAIL PROTECTED]> wrote: >> >> >> I suppose all I need to do is setup the consumers as durable subscribers. >> The producer side doesn't matter does it? >> -- >> View this message in context: >> http://www.nabble.com/Special-Topic-Queue...-t1558344.html#a4233834 >> Sent from the ActiveMQ - User forum at Nabble.com. >> >> > > > -- > > James > ------- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Special-Topic-Queue...-t1558344.html#a4234792 Sent from the ActiveMQ - User forum at Nabble.com.
