BTW. you can try web sockets, which will be included in the next release http://www.nighttale.net/activemq/activemq-54-stomp-over-web-sockets.html
Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Apr 6, 2010 at 10:34 AM, Dejan Bosanac <de...@nighttale.net> wrote: > Hi, > > this sounds similar to this > https://issues.apache.org/activemq/browse/AMQ-1243 > > will take a look at it. > > Cheers > -- > Dejan Bosanac - http://twitter.com/dejanb > > Open Source Integration - http://fusesource.com/ > ActiveMQ in Action - http://www.manning.com/snyder/ > Blog - http://www.nighttale.net > > > On Mon, Apr 5, 2010 at 2:23 AM, niccotnt77 <n.ventur...@labbit.it> wrote: > >> >> Hello, >> I'm using Active-MQ with AJAX for displaying messages coming from a topic. >> A >> producer is correctly sending message topic://test and a consumer is >> reading >> from it and displays messages on a web page. >> >> When I open two or more consumers on a single web page, or on multiple >> pages >> within the same session I get a strange behavior. I expected a broadcast >> of >> the messages to all the listening consumers, but what I see is some sort >> of >> distribution of messages between them. >> >> I went deeply inside the code and I noticed that the destination is tied >> to >> one and only one consumer inside the session. Some questions: >> >> 1. how can I get more instances of a consumer for a specific topic, during >> the same session? >> 2. if it's not possible, how can I assign a different session every time i >> POST a 'listen' command? >> >> I think the concept of 1-consumer per session is correct applied to an >> application environment where i can create as many sessions as I like... >> but >> applied to the web, it gets confusing. I think web session are very >> different from JMS sessions, they have only the name in common. I think we >> should tie the consumer to another kind of "session", maybe the listener >> id, >> or a tag inside the request. >> >> >> -- >> View this message in context: >> http://old.nabble.com/Topics%2C-Consumers-and-Web-Session-tp28133871p28133871.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> >
