Comment 1 for bug 436640

Our error reporting utility will have a new method on it called something like "handling" (to parallel the current "raising"). It would be responsible for simply marking the error record as informational. With only this flag, we should be able to see what is
going on for this case, because the zope publisher will raise the exception normally (using "raising") if the retry fails for whatever reason.

We would also presumably use this "handling" method for the ++oops++ handler, wherever that is.

To mark the records as informational, the change needs to be something that your OOPS tool can read. Ideally it would be something that an older version of the OOPS tool will ignore (not fall over) and a newer version would know to identify the OOPS as informational in the DB for filtering, as I said.

If this method works out well for us, we can propose it for the zope package that defines the error reporting utility generally.

Thanks

Gary