Jon- First question—
A. Is the goal to get the same message to all users? ie.. 100 messages each go to 10 users. B. Is it to get the correct subset of messages to each user? ie.. 100 messages, 10 different message to 10 users. For A, you want Topics, or Virtual Topics For B, you want some sort of message filtering/content based routing. Matt On Jul 24, 2014, at 8:56 AM, Jon Mithe <[email protected]> wrote: > Hi, > > Sorry this may be a silly question, I'm new to ActiveMQ and reading ActiveMQ > in action but I don't understand with a desktop application with multiple > different users connecting to a broker how you can provide the same > messaging functionality but unique to each user. > > For example, a system where a user can use their application send an order > and receive updates on it. The send queue could be generic to everyone one > but if you use a queue like jms:order-updates then how can each individual > user get their specific updates? > > I imagine here you could maybe use some form of publish subscribe or for > reply - request to which your messages would specify a dynamically allocated > queue, e.g. something like jms:updates_<user_id> > > Just feels ott / not scalable / I'm not getting something. > > Can anyone point me in the right direction? > > Thanks, > Jon > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/How-to-handle-users-tp4683585.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
