mORMot Open Source

Thanks for your detailed answer! Here is the use cases:

x users working with y applications on z terminal servers, every app needs to write a log file.

Possible solutions:

* every user session writes its own log file (see the disadvantage?)
* one log per application (exe1 -> exe1.log, exe2 -> exe2.log) does not work with basic file open modes like fmShareDenyWrite
* all apps write into one big log file (good for browsing)

Other options:

* write to a central application server with a UDP based service, write to central files from there (this is what I am implementing at the moment).

But I think that writing to the same file from different processes would not be slow. Even if the logging speed is slower with file locking, it is still better than no logging, in production mode apps log only events every couple of seconds.