As you know, none of the javascript rewrite has made it into HEAD. Perhaps
James or a committer on the project can weigh in on the patch I submitted.
If it is in HEAD then it can be improved upon and have these new features
added. Not to say, we can't evolve the code outside of that process, but
then we end of with source control and versioning problems.
-- jim
Dan The Man wrote:
>
> Hi Jim,
>
> I am most concerned with the first type of failure, where the client
> has a problem with the network connection, but the server is still
> running properly. What I did was take your modified amq.js (from link
> in my previous message) and then added the following to line 111 in
> pollErrorHandler() :
>
> setTimeout(function() { sendPoll(); }, pollErrorDelay);
>
> That seems to work well enough, but then I am very new to the whole
> AJAX thing, and there is probably a better way. I was hoping that some
> sort of retry logic would make it into the head so that I can use the
> standard javascript files (makes maintenance a lot easier).
>
> --Dan
>
> On 10/13/07, chago <[EMAIL PROTECTED]> wrote:
>> One is when the webserver closes the connection due to restart or network
>> problem. In this case, the assumption is that the ActiveMQ server is
>> still
>> running properly and the connection between the browser and the servlet
>> needs to be reestablished. Since the client discovers the disconnect when
>
>
--
View this message in context:
http://www.nabble.com/AJAX-Client-Reconnect-tf4608571s2354.html#a13217585
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
