Sidnei da Silva wrote:
On Wed, Dec 07, 2005 at 10:13:36PM +0100, Dieter Maurer wrote:
| And, as we speak about replacing Zope2's ZPublisher
| by Zope3's Publisher, the old Zope2 ZPublisher will
| probably not grow such hooks any more -- but hopefully,
| the Zope3 Publisher will signal
On Thu, Dec 08, 2005 at 09:23:47AM +, Chris Withers wrote:
| Sidnei da Silva wrote:
| On Wed, Dec 07, 2005 at 10:13:36PM +0100, Dieter Maurer wrote:
| | And, as we speak about replacing Zope2's ZPublisher
| | by Zope3's Publisher, the old Zope2 ZPublisher will
| | probably not grow such hooks
Hi Dieter,
You err: I do want to see them in the logfile and
I stole Florents idea to use threadframe (in his DeadlockDebugger)
to include a traceback for long running requests in the logfile.
This way, it is
easy not only to identify long running requests but also to
get hints where they are
Chris Withers wrote at 2005-12-7 10:01 +:
You err: I do want to see them in the logfile and
I stole Florents idea to use threadframe (in his DeadlockDebugger)
to include a traceback for long running requests in the logfile.
This way, it is
easy not only to identify long running requests
On Wed, Dec 07, 2005 at 10:13:36PM +0100, Dieter Maurer wrote:
| And, as we speak about replacing Zope2's ZPublisher
| by Zope3's Publisher, the old Zope2 ZPublisher will
| probably not grow such hooks any more -- but hopefully,
| the Zope3 Publisher will signal corresponding events.
It already
