That's why I suggested using MSMQ, which can be used to guarantee that the log messages are not lost or removed until they have been successfully written.
Obviously there's still the possibility of catastrophic system failure, but in a case where that matters, there are hardware solutions (RAID etc). On 11/21/05, J. Merrill <[EMAIL PROTECTED]> wrote: > > The only real disadvantage of this is that the data is not written to the > file "in real time" -- so it's vaguely possible that some log info could be > lost if there's a very bad crash that shuts down the logging task. (But it's > probably more likely that the disk onto which the data is being written will > fail -- and there's not much you can do about that, other than to have > another place to write if the first place fails.) > > At 11:44 PM 11/20/2005, Girish Jain wrote > >Eric, > > > >The idea of using a Queue to log the entries looks better. Let me discuss > >the same internally with the team and senior, then decide its feasibility > >(certainly depending upon development cost and criticality of logging > >performance) > > > >Thanks for the suggestion > > > >Regards, > >Girish Jain > [snip] > > J. Merrill / Analytical Software Corp > > =================================== > This list is hosted by DevelopMentor(r) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > -- Eric Means [EMAIL PROTECTED] http://www.randomtree.org/eric/ =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
