[AMQ-1243] Multiple WebClient instances

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Abandoned
• Fix Version/s: AGING_TO_DIE

Environment

Using activemq-web-demo as a test for changes in activemq-web while using the 'chat demo'. Patch created from eclipse on mactel

• Patch Info: Patch Available
• Assignee: Dejan Bosanac
• Reporter: James Alan Shepherd
• Created: 04/May/07 11:09
• Updated: 20/Jan/16 22:59
• Resolved: 20/Jan/16 22:59

Description

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.