in reply to Handling asynchronous events with Perl

Hi,

As Ultra stated I also think that a good approach would be using POE

I don't know if every AUV have one file associated, if it put the data into a database or whatever, but for the normal thinks, like asynchronus DBI connection, POE has components.

If every AUV writes on a file, you can easily create a POE Session which use the POE::Wheel::FollowTail so that an Event is called everytime the file has a new line/record.

Have some practise with POE, so if you have questions don't hesitate to get in touch, but first take a look at the webpage because there you find example code and also read the 2 documents on perl.com, results of searching here.

Update: just read that it transfers files, so ::DirWatch would be a good solution; you can assign every AUV a directory where it upload its data and having POE Sessions that control each directory.

Update: I'm agree with perrin's comment about cron and absolutely with KISS. Cron do a nice job and of course, if a 1 minute lag is not too long... take the simple option, but anyway you can make your daemon supervised, so when it exits it gets relaunched again, this is also simple.

Regards,

|fire| at irc.freenode.net
  • Comment on Re: Handling asynchronous events with Perl