I think I'd rather look at any such work as orthogonal perf metrics data gathering since it is really is, functionally, an independent question of the log level. For example, we might want to see the effect of logging itself on the speed of hosted mode refresh. I think some sort of separate global collector mechanism would be a better design.
On Wed, Sep 2, 2009 at 9:48 AM, John Tamplin <j...@google.com> wrote: > On Wed, Sep 2, 2009 at 8:58 AM, Freeland Abbott <fabb...@google.com>wrote: > >> Is the TIMING log level a good idea, though, and sorted correctly? I >> waffled a bit on whether to make it be a new log level or an orthogonal >> flag.... > > > I'm not sure it makes sense as a log level -- I think perhaps a separate > flag to trigger timing information is useful, though it isn't clear how that > will wind up different than the existing PerfLogger usage. > > > -- > John A. Tamplin > Software Engineer (GWT), Google > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
