[ https://issues.apache.org/jira/browse/AMQ-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-1243. ----------------------------- Resolution: Unresolved > Multiple WebClient instances > ---------------------------- > > Key: AMQ-1243 > URL: https://issues.apache.org/jira/browse/AMQ-1243 > Project: ActiveMQ > Issue Type: Improvement > Environment: Using activemq-web-demo as a test for changes in > activemq-web while using the 'chat demo'. Patch created from eclipse on mactel > Reporter: James Alan Shepherd > Assignee: Dejan Bosanac > Priority: Minor > Fix For: AGING_TO_DIE > > Attachments: ASF.LICENSE.NOT.GRANTED--patch-trunk-2007-05-04.txt, > patch-trunk-2007-05-09.txt > > Original Estimate: 2h > Remaining Estimate: 2h > > Just learning about ActiveMQ and noticed, like many before I imagine, that > the chat demo doesn't let you use it in different tabs/windows of a browser > at once. Well, it runs, but you share the consumers in the WebClient stored > in the HttpSession. > So, why not have multiple WebClients in the Session, one for each 'rendering' > of the window, meaning for each instance of amq(.js)? > So you need a UID in HttpSession for each amq instance. > You also need to set the amq._pollDelay to something sensible, as polling is > done by GET and connections to the server are throttled by the browser. > Hopefully the attached patch will seem resonable. > Changes in _amq.js are set to test the new functionality; > minimal changes to MessageListenerServlet; > few changes to WebClient; > added WebClientDirector to direct getting of correct WebClient instance and > creating new ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)