On 21.04.2011 08:48, Johannes Schmitt wrote: > Did you do any investigation what method names/log levels other > frameworks use for logging? The current ones are not only close to > syslog, or Zend, but also close to log4j, to Logbook (after which you > have designed Monolog), and I'll probably find more if I search further. > > I feel that this change is a bit rushed at this point, and IMO it should > only be made if there is a real benefit, or if the current system is > broken which I fail to see right now. Why would we want to invent our > own conventions now?
First I'm not inventing conventions I'm adjusting to the conventions of the framework. Second, Logbook only has CRITICAL, ERROR, WARNING, INFO, DEBUG, it doesn't have the full stack of syslog levels, and they don't support custom levels either (unlike ZF and log4j). ZF took the classic/academic approach (8 syslog-like levels), and I don't think it makes any sense in the web context. > To address any possible confusion what the priorities mean, this mainly > seems like a documentation issue to me. We're web developers, and I seriously couldn't find a good way to explain where you should use ALERT over CRIT or ERR etc. To me error/warning/info is more than enough, debug I just kept for a tiny bit more flexibility into low level logging. Cheers -- Jordi Boggiano @seldaek :: http://seld.be/ -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en
