Daniel, I had the same requirement you have a few weeks ago. First I started writing my own logger base class, but it started looking more and more like the sfLogger class as work progressed, so what I did was create my own logger base class that extends sfLogger. Yes, it extends sfLogger, however, in my class' initialize method, where I would normally call the parent initialize method I don't. This way the event dispatcher is never connected to the logger class and none of the symfony events are logged. Might not be the best solution, but I needed practically the same functionality as the sfLogger and would have simply duplicated the code almost 1:1 just leaving out the dispatcher connection code.
Cheers Henning -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richtermeister Sent: Wednesday, October 07, 2009 6:33 PM To: symfony users Subject: [symfony-users] sfLogger - why the eventdispatcher? Hi all, one thing I was wondering is why all sfLogger variants have to use the sfEventDispatcher.. it seems that this makes each logger listen to application.log events.. What if I just want a simple logger that logs results from some task I'm doing.. I don't neccessarily want application events in there as well... Thanks for any pointers. Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
