Tim Nevels writes: >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. Put failed logs into a 4D table and send them once the log writer is back online? Tom Benedict Optum This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ********************************************************************** 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] **********************************************************************
