On 26 Feb 2014, at 23:08, Jason Hect wrote: > My biggest concern is adding 4D Client to the equation adds another failure > point
I think you'll find that once everything's stable, the biggest failure point is the network switch that manages the connection between the client box and the server box. If your network connection is the least bit intermittent then you'll get a -10002 on the client and will have to restart. You need Jens Blomster's lifesaver utility, Robot Watchdog (affectionately known by my customer as "the dog").... http://www.algonet.se/~blomster/tools.html It is an ultra simple utility which you can configure in 20 seconds to detect alert messages and respond with the appropriate keystrokes. It will even detect a -10002, click ok on 4D's message, restart 4D Client, do the login all the various button clicks to start the webserver - all in unattended mode. Used very rarely if you have a good network infrastructure, but it can reduce your downtime to a couple of minutes if the worst happens while you're asleep. The other thing you can do is set up more than one 4D Client web server and loadbalance them with Apache (but that doesn't protect you from the network switch blowing up). I wouldn't run the web server from 4D Server though - that's asking for a proper disaster. Regards Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
