note
rcaputo
<p>If the weekly task is relatively isolated, start another [mod://POE::Session] to do it. Something like this may be sufficient if do_that_thing() doesn't take too long.</p>
<code>
POE::Session->create(
inline_states => {
_start => sub {
my $next_unix_time = calculate_when();
$_[KERNEL]->alarm(weekly_task => $next_unix_time);
},
weekly_task => {
do_that_thing();
my $next_unix_time = calculate_when();
$_[KERNEL]->alarm(weekly_task => $next_unix_time);
},
},
);
</code>
<p>If do_that_thing() takes too long, then it may need to involve system(1,"command"). See [doc://perlport] for discussion of system(1,"command") on MSWin32. For best results, use [mod://POE::Kernel]'s sig_child() to detect when the command has ended.</p>
<p>And a word about fork() in POE on Windows. If you plan to do anything more than system(1,"command") in the "subprocess", then you should check out <a href="https://github.com/rcaputo/poe">POE's Github repository</a> for pre-release iThread-safety fixes. As you may be aware, fork() on MSWin32 is implemented in terms of iThreads, so modules must be iThread-safe to fork() there.<p>
<!-- Node text goes above. Div tags should contain sig only -->
<div class="pmsig"><div class="pmsig-36709">
<p><tt>-- <br><a href="http://search.cpan.org/~rcaputo/">Rocco Caputo</a> - <a href="http://poe.perl.org/">http://poe.perl.org/</a> - <a href="irc://irc.perl.org/poe">irc://irc.perl.org/poe</a></tt></p>
</div></div>
888361
888361