Some of the highly requested features for 3.2 are simple database requests. Like 1) delete a document 2) add a document (or index only a certain set of URLs and not pull a full update) 3) get stats on the databases (I'm assuming pulling up the stats from -s is fine) 4) dump the databases to a file for transporting or upgrading 5) load the database from a file Adding 2) to htdig is pretty easy, and it's already done, with the -m (minimal file) flag. 4) already exists through the htdig -t flag, so it would only require some minor coding to get this to work. But with the possible exception of 2), I'm not sure what the best interface to these features would be. Should they exist as small one-purpose utilties or as some sort of option to the current programs. If the former, what should they be called and where should they live (httools/ directory?). If the latter, how do you make them easy enough to use without making the current programs unweildy? -Geoff ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] containing the single word "unsubscribe" in the SUBJECT of the message.
