[DGD] Failed Inheritance and Object Daemon

[Noah Gibbs]

  Sounds good, though it's still not clear what you do if it screws up partway.

  You could try and figure out if there's some way you could do a series of
smaller updates, but that would only work in some cases (for instance, not if
one of your updated libs is the AUTO object!).  It'd also be kind of a pain to
figure out, though I guess you could just update libraries one at a time, each
atomically.  That'd be slow, though.

  But yeah, having a "force update" command that can break your ObjectD's
tracking could definitely suck :-(

  Also, it could be hard to figure out what X should be - remember it'll depend
on things like available memory, at least if you do it well.

--- Steve Wooster <swdgd at intergate.com> wrote:

> Thank you Felix and Noah for suggesting atomic functions! :)
> 
> Here's what I'm thinking now... the object daemon will check if the number of
> objects 
> it would need to update is less than X... If so, it tries to update it
> atomically. If there's 
> too many objects or the atomic update fails, there would be some extra
> override flag 
> that can be used to force it to do an update no matter what.
> 
> -Steve Wooster
> 
> __________________________________________
> http://mail.dworkin.nl/mailman/listinfo/dgd
> 





		
____________________________________________________
Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs