Hi Bertrand, I wouldn't be opposed to using a better-structured RequestProgressTracker log. (I did originally look at the existing one, but wasn't too excited about parsing it to get the info out.)
But I don't think it saves adding a new mechanism. The new mechanism's primary job is to weave the debug info into the rendered html so that it can be displayed client-side in the context of the portions of the page it rendered. That's the "highly-integrated" part. Cheers, Jeff. On 08/01/2014 10:47, "Bertrand Delacretaz" <bdelacre...@apache.org> wrote: >On Wed, Jan 8, 2014 at 11:42 AM, Jeff Young <j...@adobe.com> wrote: >> ...FWIW, the idea came up during the investigation of a similar (but >>more >> highly-integrated) debug/developer-mode facility.... > >IMO that kind of info should come from the RequestProgressTracker >instead of adding new mechanisms. This is a basic log-like structure >for now, but improving it with more structure shouldn't be too hard, >and making sure it has all the info that a developer would want has >other benefits in terms of troubleshooting. > >-Bertrand
