Re: Handling asynchronous events with Perl

What exactly is wrong with the approach you have now? Using a cron job is a pretty robust approach, since you don't have to worry about creating your own daemon that is reliable enough to run for months. I don't think any of the approaches discussed here will prevent you from needing to check if the directory has been updated, so it's really just a question of how often you check. If a 1 minute lag is acceptable, use cron and keep it simple.

Comment on Re: Handling asynchronous events with Perl

Replies are listed 'Best First'.
Re^2: Handling asynchronous events with Perl by njcodewarrior (Pilgrim) on Jul 11, 2005 at 10:59 UTC
When the AUV surfaces and connects to the onshore server, it displays some basic information (ie: GPS position and some ocean measurements such as temperature, currents, etc.). The only real problem with using a cron is that I'd like to immediately begin parsing this information and (possibly) retask to the AUV to a new location or modify it's behavior some other way. While 1 minute might be acceptable, I'd really like to know as soon as the vehicle surfaces. I will definitely consider this, however....thanks for the suggestion.	[reply]

Replies are listed 'Best First'.

Re^2: Handling asynchronous events with Perl
by njcodewarrior (Pilgrim) on Jul 11, 2005 at 10:59 UTC

When the AUV surfaces and connects to the onshore server, it displays some basic information (ie: GPS position and some ocean measurements such as temperature, currents, etc.). The only real problem with using a cron is that I'd like to immediately begin parsing this information and (possibly) retask to the AUV to a new location or modify it's behavior some other way. While 1 minute might be acceptable, I'd really like to know as soon as the vehicle surfaces. I will definitely consider this, however....thanks for the suggestion.

[reply]