RE: Reverse Ajax reconnecting

Thanks.

 

What would be the best way, in your opinion, to catch the disconnect error so that we can at least notify the user and maybe reload the page? 

 

The only obvious way I could think of is hooking the warningHandler (it seems to go there for reverse ajax disconnects) and parsing the error text to see if it's a disconnect.

 

Have any better suggestions?

 

---

From: joseph.walker-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx [mailto:joseph.walker-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx] On Behalf Of Joe Walker
Sent: Friday, February 16, 2007 13:54
To: users-EyPigyGktj4FDOXUYO6UHQ@xxxxxxxxxxxxxxxx
Subject: Re: [dwr-user] Reverse Ajax reconnecting

There isn't currently. Maybe post 2.0
Joe.

On 2/12/07, matan-FP6co0geiwbQT0dZR+AlfA@xxxxxxxxxxxxxxxx < matan-FP6co0geiwbQT0dZR+AlfA@xxxxxxxxxxxxxxxx> wrote:

I was wondering how the reverse ajax mechanism deals with disconnects (for example if i turn off the web server, then turn it back on)?  Is there a mechanism to retry the connection and reestablish it when it becomes viable again? 

 

Obviously, this would be a new "session", but i'd like to know if anything is in place for this?

 

Thanks