On Fri, Jan 11, 2002 at 11:11:12AM -0500, Jason Boxman wrote:
> On Friday 11 January 2002 01:29 am, you wrote:
> > The first alarm_adjust() call is redundant. The alarm should not be
> > moved when the delta time is zero seconds. From around line 2215 in
> > Kernel.pm:
> >
> > # Nothing to do
On Friday 11 January 2002 06:09 pm, you wrote:
> As far as I can tell, you have two options.
>
> This will remove the previous delay and set a new one. The old ID is
> overwritten by a new one.
>
> $kernel->alarm_remove( $id );
> $id = $kernel->delay_set( event_name => 120 );
Well, that was
On Friday 11 January 2002 01:29 am, you wrote:
> On Thu, Jan 10, 2002 at 10:42:39PM -0500, Jason Boxman wrote:
> > I think I have it figured out, now, but for clarification.
> >
> > If I have a session that does something with a SocketFactory, and I want
> > to implement and internal timeout, I sh
On Thu, Jan 10, 2002 at 10:42:39PM -0500, Jason Boxman wrote:
> I think I have it figured out, now, but for clarification.
>
> If I have a session that does something with a SocketFactory, and I want to
> implement and internal timeout, I should do a delay_set( 'event', 120 ), then
> for each su
I think I have it figured out, now, but for clarification.
If I have a session that does something with a SocketFactory, and I want to
implement and internal timeout, I should do a delay_set( 'event', 120 ), then
for each successive success event, an alarm_adjust( id, 0 ) followed
immediately b
