[ 
https://issues.apache.org/activemq/browse/AMQ-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43480#action_43480
 ] 

Saira Gul commented on AMQ-1377:
--------------------------------

hi dan!!

hi dan!! 
Could u please explain me vat does following means? 
var sendPoll = function() {
// Workaround IE6 bug where it caches the response
// Generate a unique query string with date and random
var now = new Date();
var data = 'timeout=' + timeout * 1000
+ '&d=' + now.getTime()
+ '&r=' + Math.random();

var options = { method: 'get', data: data, success: pollHandler, error: 
pollErrorHandler};
adapter.ajax(uri, options);
};
u'hv already set 25 sec that the long-polling socket will stay connected. does 
it mean u r going to set 25000 secs for timeout parameter which seems quite 
unrealistic.. iam confused..

by using ur file the following scenerio occurs:
1. ActiveMQ and tomcat running on my machine and if i disabled network 
connection from my machine the pooling doesnt break, js continously send 
request for message to MessageListenerServlet 

2. but other machines running same application through my IP stop sending 
sending requests to servlet means polling breaks here, and on the establishment 
of network again js become able to send request to servlet and response also 
come back to activeMQ but pooling doesnt occur so that js fail to get response 
from servlet..

hope i explain the possible scenario.?

This is the same scenario when Tomcat, activeMQ, and Asterisk running on same 
machine and if i terminate the tomcat then polling stops and pollErrorHandler 
only calls once. on the activation of tomcat again, js file again able to send 
request (queue)to servlet and listener are failed in this case   

> amq.js should not have a dependency on prototype.js
> ---------------------------------------------------
>
>                 Key: AMQ-1377
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1377
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.0.0
>            Reporter: Jim Cook
>         Attachments: amq.js, amq.js, amq.js, amq_js.zip
>
>
> amq.js uses a script loading technique to include behavior.js, prototype.js 
> and _amq.js. The Behavior library is included only for the purposes of the 
> chat client and is only GUI in nature, so that should go. Also, Prototype is 
> included for its AJAX functionality, however everyone has their favorite 
> javascript library and although I cut my teeth on prototype, I use jQuery 
> now. I certainly don't want amq.js to include prototype when I have a 
> perfectly good AJAX library already included in jQuery.
> IMHO, amq.js should include only the functionality of client-side 
> javascript-enabled JMS. The page author should include her AJAX library of 
> choice (prototype, dojo, jquery, mootools, etc.) and an adapter class that 
> allows amq.js to use the particular ajax library.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to