> [1] Does this look like a complete solution? I suppose it relies on > timestamp consistency between system components... it is possible > that between setting "start = ..." and performing the rebuild, > another thread in the system will have create an earlier timestamp > for an object that did not get committed until after the rebuild > began. Is it possible to do a perfect rebuild, or would that require > building a layer of concurrency logic into AAF?
You can sync your server clocks using ntpd, and you can always update a few extra seconds to work around latency. -Kyle _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
