In some email I received from Chris Calabrese, sie wrote: [...] > > Otherwise it seems like a good start. I'd add: > > > > * Performance issues with log file opening/closing (reading and > > writing the entire logfile) once per message. I don't know of *any* implementation that does the above. I think that this has been mentioned here and others have run with it. [...] > Folks, I'm not saying that the XML-style complexity I've proposed is > definitely the way to go. However, I haven't seen anything else that > addresses all the concerns of log privacy, log no-repudiation, and a flexible > structure in which to express concepts like "the source address was xxx.xxx" > in a way that's both human and machine readable. I wouldn't call XML immeadiately "human" readable. Then again, unless the `machine' is taught english and about different messages programs send, it isn't going to be able to read anything that is easily read as it is. I think it is important to group the data into two types, from the start: - supplied inside the log message by the application and - environmental, supplied by the sender (be it function call or host). Given that the `environmental' data is going to be somewhat similar for all messages, etc, maybe it's worth making a `protocol header' out of it ? Darren
