What's a POS??

[Marcus G. Daniels]

>>>>> "MM" == Mike McDonald <mikemac@titian.engr.sgi.com> writes:

MM> How fine a granularity does your
MM> checkpointing have? How do you handle different things wanting
MM> different granularities?

One idea is to check the set of granularities using a validation
routine.  The validation routine could either throw an exception (that
the members had conflicting persistence properties) or take the most
conservative value (the decision could be based on nature of the set
itself).

MM> If not the above, then does the object builder or the object user
MM> determine if the object is persistant? Ie, does the object have to
MM> be a special kind of object (maybe a CLOS object with a particular
MM> base class) or can I tell the POS system to "save" any ole object?

I'd like to be able to save any object, just by storing it in a value
cell and adding a property to the symbol.  

MM> If it's the latter, how do you determine where the object ends and
MM> some other object begins? 

Archive a reduced `root set'.