here. Let me know how your
mileage varies.
-- Loren
- Original Message -
From: "Stuart 'Zen' Bishop" [EMAIL PROTECTED]
To: "Loren Stafford" [EMAIL PROTECTED]
Cc: "Loren Stafford" [EMAIL PROTECTED]; "zope-dev"
[EMAIL PROTECTED]
Sent: June 15, 2000
"Phillip J. Eby" wrote:
At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote:
Its not a problem with ZScheduler, it a problem that no one has written
a plug-in logging system that is good enough for what you are trying to
do. The existing zLOG API is fine (well - it could be better), but
At 12:42 PM 6/15/00 -0400, Shane Hathaway wrote:
Agreed; I see this as by far the best approach. It's a tried and true
pattern.
Not only that, but it gives you extremely fine-grained control over what
you do and don't log. And, if the other events like adds and deletes on
folders are in
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Stuart 'Zen' Bishop
Sent: Wednesday, June 14, 2000 20:58
To: Loren Stafford
On Wed, 14 Jun 2000, Loren Stafford wrote:
I need some advise for designing a flexible system for logging the
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Phillip J. Eby
Sent: Wednesday, June 14, 2000 21:21
To: [EMAIL PROTECTED]; Loren Stafford
At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote:
Its not a problem with ZScheduler, it a problem that
On Thu, 15 Jun 2000, Loren Stafford wrote:
It would be a good idea if there was a field in the ZEvent that defined
the subsystem used in the zLOG call.
I didn't follow your point here. By "subsytem" do you mean which logger in
the loggers tuple? Then do you mean that different ZEvents
- Original Message -
From: "Loren Stafford" [EMAIL PROTECTED]
To: "Phillip J. Eby" [EMAIL PROTECTED]; [EMAIL PROTECTED]; "Loren
Stafford" [EMAIL PROTECTED]
Cc: "zope-dev" [EMAIL PROTECTED]
Sent: Thursday, June 15, 2000 4:40 PM
Subject: RE: [Z
At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote:
Its not a problem with ZScheduler, it a problem that no one has written
a plug-in logging system that is good enough for what you are trying to
do. The existing zLOG API is fine (well - it could be better), but just
needs someone to write the
