Your understanding of $_KERNEL->alarm() is slightly off. It will clear any undispatched alarms with the same event name (for the same session) before setting the new one. Compare it to alarm_add(), which adds another alarm without clearing the previous one.

In your broken case, "wakeup" is always dispatched before "wokeup" because it's a fraction of a second earlier (due to Time::HiRes::time()). Every time "wakeup" is dispatched, it pushes "wokeup" 2sec into the future... so "wokeup" never has a chance to be dispatched.

Actually, it behaves the same way even if "wakeup" and "wokeup" are set for the same time. POE breaks ties by dispatching timers in the order they were set.


In reply to Re: POE::Session - why does alarm order matter? by rcaputo
in thread POE::Session - why does alarm order matter? by jfroebe

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.