You are not logged in.
Pages: 1
In order to improve system security and project reliability, a user audit function is added to record user behavior logs. One method is to use TSynLog, another method is to intercept method events from the interface, and finally the framework's time machine.
I hope everyone can help improve the plan and provide key suggestions.
Offline
Those 3 methods are fine.
You have also the interface-level SOA execution statistics into a TOrmServiceLog ORM table, with TServiceContainerServer.SetServiceLog.
It write one DB row per SOA call, so you can easily search using SQL within the stats DB.
Or perhaps I would add this feature outside of the mORMot logic.
I mean, if you define a SOA server, I would implement an Audit Trail not at mORMot level, but in your interfaces/classes logic.
- or was it your 2nd method?
Offline
Thank you! Of course, if there are events, use events, if there are interfaces, use interfaces, and callback functions are also acceptable.
Offline
Pages: 1