> > -----Original Message----- > > From: Wiggins d Anconia [mailto:[EMAIL PROTECTED] > > Sent: Monday, May 10, 2004 4:36 PM > > To: PerlDiscuss - Perl Newsgroups and mailing lists; > > [EMAIL PROTECTED] > > Subject: Re: File Monitoring > > [snip] > > > There is a directory watching component in POE > > Where to find doc on that (link) ? >
http://search.cpan.org/~cholet/POE-Component-DirWatch-0.01/DirWatch.pm > >or you could grow your own, sorry > >I can't provide the one I have (licensing issues). > > Why did you re-invented the wheel ;) > Or Am I missing some basic infos ? > Good question. Several reasons, mostly dealing with our application overall. 1. The component mentioned is a very good example of using POE's inline sessions to do a polling type of activity but isn't terribly robust (I don't believe it was designed nor needs to be as a core component). 2. The callback interface didn't quite suit our needs as we were going for more of an overall OOP structure and wanted continuity across the app components. 3. I found it difficult to manage the directory watchers, for a couple it would be sufficient but we were talking about upwards of 40 to start, with more coming in the future. One of the key goals of our app was to have the ability to pause/resume as well as start/stop a particular watcher at any given time, the session based watcher made this more difficult (in my mind) than an object based one. 4. As a production app in a financial organization we needed a lot of logging, and scalability, but could sacrifice development time and maintenance. We also wanted the logging to be seemless across the app, so we built the logging directly into the watcher we made. In the end because of the simplicity of the base module I don't know that we reinvented the wheel, more like just put a nice steel belted tire around it :-). The underlying session that forms the core of the component is still intact, the same events are used, but the data structure itself is more accessible and the HEAP usage was dropped in favor of a standard OOP hash. These things made it simpler to control the session since it is just a basic Perl object and will allow us to change the implementation in the future if need be since it is completely encapsulated (aka no fussing with POE events outside the object's internal implementation). I am still attempting to get the organization to allow me to release it, that or I may build "my own" from scratch and incorporate it into another app that I can release :-). But there is no timeline for all of that... http://danconia.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
