That does sound like a good idea, please log it as a feature request in the issue tracker:
http://code.google.com/p/google-wave-resources/issues/list Thanks, -joe On Thu, May 6, 2010 at 7:24 AM, Daniel F. <[email protected]> wrote: > I'd like the debug logs to not only show me the incoming blips, but > also which regex filtering rule it was which allowed Wave to pass the > message to the robot. > > My issue is that I've got a complex regex rule set up, which is > generated automatically, and my incoming bandwith is exploding with > DOCUMENT_CHANGED events which, after being evaluated by the handler > don't result in any changes being sent to the server. > > The ratio of DOCUMENT_CHANGED which I'm really getting and which I > actually should be getting is about 500:1, so I could save *a lot* of > bandwidth and cpu. > > It would be quite laborious to check by hand which of the ~50 patterns > in the filtering regex is causing probably any blip to get through, so > adding the match to the debug text would be really great. > > Kind regards, > Daniel > > -- > You received this message because you are subscribed to the Google Groups > "Google Wave API" 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/google-wave-api?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Wave API" 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/google-wave-api?hl=en.
