I am using AAF trunk, and I want a way to rebuild an index on a
production site with little or no interruption to service. The Drb
Server documentation* states that when an index is rebuilt, it is
done in a separate location and then swapped into place when
finished, and so to do a complete rebuild on a live site, one must
take into consideration objects which have been created or modified
in the meantime. To achieve this, I have come up with the following
 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?
 Is the behavior described in the Drb Server documentation
different from AAF when not using the Drb Server?