Thomas, Off the top of my head, you could log everything with NDC then take logs from the main log based on user id and the level. This removes the complexity to your text parser, which could run as a separate application watching the log files, but won't appeal to your client if they want to micro-manage the solution. Why does your client need to restrict the logs- do you have some restriction on the available storage?
William Chamberlain Programmer MiTech Group Plc Gilford House, The Valley Centre, Gordon Road, High Wycombe, Bucks, HP13 6EQ. -----Original Message----- From: Auinger, Thomas [mailto:[EMAIL PROTECTED]] Sent: 2002 07 23 09:37 To: '[EMAIL PROTECTED]' Subject: Multiple logger hierarchies / subclassing category? Hello, I currently work for a project which involves server side logging of client requests. Clients are uniquely identified by a client id. Our customer demands different logging 'coverage' depending on the client id: client "c1": com --- mycompany --- util [ERROR] [ALL] client "c2": com --- mycompany --- util [INFO] Meaning for client c1 all calls from the "com.mycompany.util" package should be logged and all calls with level ERROR from beneath "com." For client c2 only all INFO level calls from beneath "com.mycompany.util" I have the client id available in some thread-based dictionary, so obtaining it from any point in the code is no problem. My first id is to subclass Logger as in the MyLogger example from the distribution and override the getEffectiveLevel() method with some client-id sensitive code. Additionaly I will have to create new Level classes which allow for storing log level information depenending on a client id. Any ideas more than welcome! Thanks in advance, Thomas --------------------------------------------------- Thomas Auinger . Software Engineer Wincor-Nixdorf GmbH . Paderborn . -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
