[DGD]Swapped-out objects

[Ludger Merkens]

On Thu, 15 Jun 2000, Felix A. Croes wrote:

> "Tavis Elliott" <tavise at nwlink.com> wrote:
> 
> > I was recently looking at the reset() functionality I have implemented, and it
> > occured to me that it is going to sweep through _all_ objects to call reset().
> >  This means any swapped-out objects will get sucked back into memory.  Is there
> > anyway I can tell if an object is swapped out before I call reset() on it, and
> > leave it peacefully where it is?
> 
> There is no way to tell.  It is best to design your mudlib so that
> objects are not accessed needlessly.  Take a look at the 2.4.5 mudlib
> simulation for an example of how to handle resets in a better way.
> 

If there is no way to tell if an object is already swapped out, is there a
way to tell that an object is about to be swapped out ? This could be
usefull to stop call_outs, drop data to save swap-space etc.

> 
> >[...]
> > If all else fails I guess I'll start a DB somewhere that tracks objects and
> > 'last-touched' type information.  Now that would be something interesting for
> > status() to return about an object.  The last time any function was called in
> > the object.
> 
> Performing a status(obj) also swaps in the object.
> 
> Regards,
> Dworkin
> 
> List config page:  http://list.imaginary.com/mailman/listinfo/dgd
> 

Ludger Merkens



List config page:  http://list.imaginary.com/mailman/listinfo/dgd