You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "James Alan Shepherd (JIRA)" <ji...@apache.org> on 2007/05/04 13:09:34 UTC
[jira] Created: (AMQ-1243) Multiple WebClient instances
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
Priority: Minor
Attachments: patch-trunk-2007-05-04.txt
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.
[jira] Commented: (AMQ-1243) Multiple WebClient instances
Posted by "James Alan Shepherd (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39113 ]
James Alan Shepherd commented on AMQ-1243:
------------------------------------------
I need to also either create multiple instances of MessageListenerServlet$Listener, or make the instance in the Session wake up all Continuations. I think the former. Will do ASAP.
> 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
> Priority: Minor
> Attachments: patch-trunk-2007-05-04.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.
[jira] Updated: (AMQ-1243) Multiple WebClient instances
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated AMQ-1243:
----------------------------
Fix Version/s: 5.3.0
(was: 5.2.0)
> 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
> Priority: Minor
> Fix For: 5.3.0
>
> 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.
[jira] Assigned: (AMQ-1243) Multiple WebClient instances
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (AMQ-1243) Multiple WebClient instances
Posted by "James Alan Shepherd (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Alan Shepherd updated AMQ-1243:
-------------------------------------
Attachment: patch-trunk-2007-05-09.txt
Second Patch
> 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
> Priority: Minor
> 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.
[jira] Commented: (AMQ-1243) Multiple WebClient instances
Posted by "James Alan Shepherd (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39115 ]
James Alan Shepherd commented on AMQ-1243:
------------------------------------------
Second patch includes changes to MessageListenerServlet$Listener.
> 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
> Priority: Minor
> Attachments: patch-trunk-2007-05-04.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.