Hey Tim, > Consider the situation where you have a mission critical system that is up 24/7 and you need logging to always work every second of the day.
> How do you handle the situation where the stand-alone log writer app crashes, is not running due to a machine restart, or for whatever reason > goes deaf and stops responding to the HTTP calls? You certainly don’t want any possibility of losing some logging information. Again, talking about a workaround. I want to log to disk out of 4D via SEND PACKET. As to your point, it's true. However, I'm seeing is a *far* more likely that 4D Server crashes than a 4D stand-alone. But your point is good. Perhaps it's better to find a small, stable service (Windows) that can run in the background to handle the HTTP-push-to-disk task and leave 4D out of it entirely. ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
