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: 
If u do decide to look into [Coro](http://search.cpan.org/dist/Coro/Coro.pm) then it might be worth having a look at [Continuity](http://search.cpan.org/dist/Continuity/lib/Continuity.pm) as this is a web library/framework built around Coro. 

Also take a look at [Squatting](http://search.cpan.org/dist/Squatting/lib/Squatting.pm) web microframework which "squats" on top of [Continuity by default](http://search.cpan.org/dist/Squatting/lib/Squatting/On/Continuity.pm). The Squatting distro comes with some examples of using [Coro::Event](http://search.cpan.org/dist/Coro/Event/Event.pm).
@(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..