Looking at perldoc POE::Kernel, it looks like everything you need is already there.

       Original alarm and delay methods:

...
         # Post an event which will be delivered after a delay, specif
+ied in
         # seconds hence. This clears previous timed events with the s
+ame
         # name.
         $kernel->delay( $event, $seconds, @event_args );

         # Post an additional delay, leaving existing ones in the queu
+e.
         $kernel->delay_add( $event, $seconds, @event_args );

       June 2001 alarm and delay methods:

...
         # Post an event which will be delivered a number of seconds h
+ence.
         # This does not clear previous events with the same name.
         $alarm_id = $kernel->delay_set( $event, $seconds_hence, @etc 
+);
...
         # Refresh an existing delay to a number of seconds in the fut
+ure.
         $kernel->delay_adjust( $delay_id, $number_of_seconds_hence );

...
[download]

It looks like you have to use the new _set and _adjust forms, but you can only do adjustments if you saved the id _set returned. Almost looks like you're back to square one :(

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.