Re: checkpoint timing & movement

• Date: Thu, 4 Jan 1996 09:12:14 PST
• From:
  Pavel Curtis <pavel@parc.xerox.com>
• In-Reply-to: "\"Seth I. Rich\"'s message of \"Wed, 03 Jan 1996 08:28:15 PST\" <199601031628.LAA01231@po.cwru.edu>dhcmQgcm"

Seth Rich writes:
> I'd love for a mechanism by which the server will forget all about periodic
> checkpoints, and leave it up to the wizards to checkpoint as often and at
> whatever intervals they wish.  Maybe make this optional, with the default
> behavior to respect current behavior.

.program #0:server_started
$dump_interval = $maxint - time() - 10; /* -10 to allow for slop */
.

> The move() builtin, as well as its related stuff (:accept, :enterfunc,
> :exitfunc, .location, .contents) gets in my way sometimes (especially with
> E_RECMOVE, which I still don't get).  Can we move movement and location out
> of the server entirely?  I'd like to control it in-DB.  (This would be
> consistent with uses of the LambdaMOO server for which "location" is
> meaningless.)

The server uses the built-in properties .location and .contents in the command
parser/matcher.  Why not simply set $server_options.protect_move = 1, move()
everything to #-1 (and leave things there when created), and then pretend that
.location, .contents, and move() simply don't exist?

	Pavel

• checkpoint timing & movement
• From: "Seth I. Rich" <sir@po.cwru.edu>

• Prev: checkpoint timing & movement
• Next: CinderVR (LambdaCore) in need of Programmers
• Index: MOO-cows
• Thread: MOO-cows