2013-01-23 15:41 AEST by Arthur Barrett - The audit sessionlog records the closing status of the client app, but does not record errors that do not 
alter the client status, e.g.: 
- attempts to commit a file with a conflict
- attempts to commit an 'open' file
- merge conflict 
- etc

These are most likely 'client only' errors, so the client would need to communicate these to the server 
somehow so that the server can audit them.  

Maybe all 'error messages' should be 'stored' in memory, then when the 'client status' is sent to the server 
(is it sent?) the whole 'error message log' can also be sent.