Re: [Zope-dev] Logging for ZScheduler?
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 relevant modules. Hmm... I think I'll add a section to the Interfaces Wiki...
Hm... this could work well with Observer->Observable, too. Imagine firing ObservableEvents, and subscribing a "Log" object to them...
"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 just needs someone to write the relevant modules. Hmm... I think I'll add a section to the Interfaces Wiki...
Hm... this could work well with Observer->Observable, too. Imagine firing ObservableEvents, and subscribing a "Log" object to them...
Agreed; I see this as by far the best approach. It's a tried and true pattern. Shane
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 place, you can make a monitoring object that notices when new things are added, and subscribes the logger to them...
-----Original Message----- From: zope-dev-admin@zope.org [mailto:zope-dev-admin@zope.org]On Behalf Of Phillip J. Eby Sent: Wednesday, June 14, 2000 21:21 To: zen@cs.rmit.edu.au; Loren Stafford
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 relevant modules. Hmm... I think I'll add a section to the Interfaces Wiki...
Hm... this could work well with Observer->Observable, too. Imagine firing ObservableEvents, and subscribing a "Log" object to them...
Cool! Then the logging operation would become a part of the scheduled event thread and transaction instead of part of the Dispatcher's thread (a possibly transaction). I'll have to think about the implications of that. Where is Observer->Observable in the development plan? ZPatterns 0.4? -- Loren
At 01:40 PM 6/15/00 -0700, Loren Stafford wrote:
Where is Observer->Observable in the development plan? ZPatterns 0.4?
-- Loren
No. 0.4 is targeted for 2.1.6 compatibility, and Observable will require Zope 2.2's new Traverse features. Also, 0.4 is due out tomorrow and I'm way behind on finishing up some bits. (Like icons...)
----- Original Message ----- From: "Loren Stafford" <lstafford@icompression.com> To: "Phillip J. Eby" <pje@telecommunity.com>; <zen@cs.rmit.edu.au>; "Loren Stafford" <lstaffor@dynalogic.com> Cc: "zope-dev" <zope-dev@zope.org> Sent: Thursday, June 15, 2000 4:40 PM Subject: RE: [Zope-dev] Logging for ZScheduler?
Cool! Then the logging operation would become a part of the scheduled event thread and transaction instead of part of the Dispatcher's thread (a possibly transaction). I'll have to think about the implications of that.
Where is Observer->Observable in the development plan? ZPatterns 0.4?
Actually, it's in Zope 2.2... It was checked into CVS a few days back. Kevin
participants (4)
-
Kevin Dangoor -
Loren Stafford -
Phillip J. Eby -
Shane Hathaway