Page 2 of 2

Re: Include redundancy

Posted: Wed Sep 29, 2010 10:31 am
by AdamBlackwell
More great ideas, thanks guys!

I see fault recovery as a seporate area/issue to coding for failure, although the two are obviously connected very closely I would like to save this topic for another post :).

The biggest problem for me is that the site will provide a work interface, so if the server goes down while a work page is open and being worked on all that work is subsequently lost because the page now has nowhere to comunicate using a html form POST during site failure and any data is lost from the POST action.

The above 3 posts have got me thinking about using the page itself as a kind of third party mointor. What I am contemplating is using ajax xmlhttp.open to communicate with a PHP file that saves the data into the database, with any problems reported back. In the event of problems things can be controlled and the work page is never actually closed until the user navigates away.

Any thoughts (and don't worry I have got a thick skin)

Thanks in advance
Adam

Re: Include redundancy

Posted: Fri Oct 01, 2010 3:38 am
by josh
Yep basically automatically save drafts of their work, and notify when the connection drops.