'll work on it next week.
Thanks very much. (I'll work on my A4D testimonial :)
Wait, are you saying the web server actually returns a connection error to the user? Wow, that really sucks.
The simulation software reports 2 types of errors - TCP socket errors and HTTP errors. My remark concerned the former. I don't actually know if the error is returned by 4D Webserver, but there are 2 failure scenarios you get with an overloaded 4D Web Server:
[1] - browser request times out (browser reports a timeout after the timeout period)
[2] - a network error (this is instantaneous - no delay after clicking the link). Browser reports a similar 'white screen' message saying "A connection could not be made with host ... etc"
I've only seen the second type with 4D Web server, however, I was under the impression that the connection was rejected at the OS level because it had reached it's socket backlog maximum (i.e. the request doesn't even get to 4D).
Peter _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
