Nitro- If you set your messages to be "persistent", you won't lose them across a reboot. A queue is intended to be short term storage, not a permanent data store to be queried often. Queues generally provide one message to one client.
Messaging systems, like ActiveMQ, provide queues and topics to meet different eventing patterns that developers might need. A simple example would be like an Instant Messaging system, where users send each other chat messages-- or like Twitter, where a user sends on message and it can go to multiple subscribers using Topics. Matt Pavlovich On Apr 8, 2011, at 10:55 AM, nitro wrote: > I think my question was to be: What's the difference between a queue and a > database. Can I have auto-incrementing fields in a queue? Will data get lost > in a queue once I reboot my box(System)? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Can-I-use-Active-MQ-in-this-Regard-tp3433946p3436741.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
