CompuServe Messages

In fact, what I'm doing is setting up an internal queue mechanism, using an EXEC list (or something similar of my own). Essentially, search (and read), add, delete and restructure (rebuild the index) operations will be queued. Add and delete operations will have the highest priority, followed by search and then restructure (which simply makes the index more efficient). The queueing will allow several searches to occur at once. When another operation is placed into the queue, however, it will wait until all active searches are complete. Then the system will execute this other request (whatever it is). So, on a given database (I may have several), there may be several searches going on, or only one of delete, add, restructure. That should take care of the contention that you spoke of. In fact, I'm beginning to rethink the entire idea of having a daemon to do some of this work. Having one task handle all of the updates may be too much of a bottleneck. Chris -)—–