<HEAD><TITLE>discuss@charon: [537] in "Coldmud discussion meeting"</TITLE>
<H1>[537] in Coldmud discussion meeting</H1></HEAD>
<A HREF="/"><IMG SRC="/i-d.gif" ALT="root"></A>
<A HREF="?537"><IMG SRC="/i-back.gif" ALT="meeting"></A>
<A HREF="/help.html"><IMG SRC="/i-help.gif" ALT="help"></A>
<A HREF="1"><IMG SRC="/i-first.gif" ALT="first"></A>
<IMG SRC="/n-fref.gif" ALT="">
<IMG SRC="/n-pref.gif" ALT="">
<A HREF="536"><IMG SRC="/i-prev.gif" ALT="previous"></A>
<A HREF="538"><IMG SRC="/i-next.gif" ALT="next"></A>
<IMG SRC="/n-nref.gif" ALT="">
<IMG SRC="/n-lref.gif" ALT="">
<A HREF="1641"><IMG SRC="/i-last.gif" ALT="last"></A>
<HR><H2>callbacks, $sys.pause</H2>
<H3>daemon@ATHENA.MIT.EDU (Sat Nov  5 21:58:52 1994
)</H3>
<PRE>
From: deforest@netcom.com (Robert de Forest)
To: coldstuff@MIT.EDU
Date: Sat, 5 Nov 1994 18:57:32 -0800 (PST)

Riche has proposed adding a request_callback() routine to 'schedule' the
 execution of the $sys.callback method at the server's convienience, and
 removing pause() on the grounds that it could be replaced with an in-db
 method to do the same thing.

pause() replenishes the current frame's ticks. It was intended for loops
 which would be known to run a long time or possibly indefinitely. It was
 supposed to provide the functionality of MOOs suspend(0).

If functions were added to allow direct manipulation of various tick counts
 then pause() could be written in-db without a callback thing. You could do
 it with the heartbeat.

So I see no use for the callback system proposed and request a system of
 direct tick manipulation.

Crag / Robert
</PRE>
