Recently, given a little free time I have started work on a small light weight set of classes with some broad generic aims.

Basically I need a few tools for:

1. Tracking Debug Information
2. Tracking Performance Information
3. Reporting an Application Error
4. Tracking User Input
5. Tracking User Activities
6. Logging of all above Information
7. Logging of Unexpected Activity
8. Input Filtering

To this end I’ll create a small (as possible) library for the purpose. Many of the above are required to enable the generation of an Audit Trail of user activity, which can be analysed for unusual activity or unexpected data. In combination with the other tools, this should create a valuable framework for allowing future Admins/Developers to find cheaters, and other malfeasants fast and easily. Other parts will allow Developers to spot performance issues (like a heavy-handed SQL query, or an unusually large Memory usage of a script operation) for future streamlining.

Logging is at the heart of the system – since much of the resulting data will be worthless unless stored. There are two logging methods planned – by database, and by XML file. These classes will also see a real start towards proper use of input filtering and output escaping (sadly lacking much of the time in QS).

No name for these classes as such since I expect they will be packaged with Q-Site.

No related posts.