You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2010/04/06 10:37:11 UTC
[jira] Assigned: (AMQ-1243) Multiple WebClient instances
[ https://issues.apache.org/activemq/browse/AMQ-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac reassigned AMQ-1243:
----------------------------------
Assignee: Dejan Bosanac
> Multiple WebClient instances
> ----------------------------
>
> Key: AMQ-1243
> URL: https://issues.apache.org/activemq/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: NEEDS_REVIEWED
>
> Attachments: patch-trunk-2007-05-04.txt, patch-trunk-2007-05-09.txt
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.