Question: I am mulling over a web-app in Perl that will allow users to create bug monitors. So essentially each "bug watch" will be a bug ID that will be passed to a sub routine along with the "sleep" time, and once the "sleep time" is over it must recur without blocking the parent process or the peer processes.

* I tried [Schedule::Cron](http://search.cpan.org/dist/Schedule-Cron). It supports cron-like format but here the arguments to the subs must be simple scalars hence I ruled it out.
* POE/Coro seem to be another options but I don't have much idea about it/ :(

Any insights ? TIA

-Matt.

Answer: 
What's wrong with Schedule::Cron? You can make any subroutine reference that you like, so you can make closures that refer to the extra or specific data you need. You don't have to rely on the argument list. Was there something else about the module that didn't work for you?
@(brian d foy): The reasons why i think Schedule::Cron is good for me 
1: $cron->add\_entry doesn't seem to provide me an option to pass @arrays/$vars to the subs.

$cron->add\_entry("$temp",{'subroutine' => \&test1,'arguments' => \@array}); is not allowed.

2: I am not sure if there is a way to add new cron entry after cron->run(detach=>1); has been fired without restarting the script..