- From: Anselm Baird_Smith <abaird@www43.inria.fr>
- Date: Fri, 15 Nov 1996 10:42:41 +0100 (MET)
- To: Alexandre Rafalovitch <alex@access.com.au>
- Cc: Craig Brozefsky <cosmo@dobie.ebs.net>, www-jigsaw@w3.org
Alexandre Rafalovitch writes: > Reindexing a directory deletes all its entries and then tries to recreate > the items in it. It means all the items without filesystem presence will > dissapear and the rest of the files will apear only if their extensions are > registered in extension database. Correct that's a real problem, which is not easy to solve unfortunatelly. My best take on it is the following: Add a non-editable attribute to HTTPResource, say "manually-edited", and have the following delete modes: - one that will delete everything recursively (the current delete) - one that will delete only non manually edited resources, non recursively (BTW re-index basically delete things, leaving it to Jigsaw to incrementally reindex) The problem is what happens when a manually edited resource is the child of a non-manually edited resource ? I am not sure the two modes above cope with that problem in the correct way... > IMHO it should not do it that way, but with no discussion about the best > way to do it, Anselm is probably finding more important areas to look into. > (I am sure MUX is a very serious problem) It was, I am nearly done with it ;-) Anselm.
Received on Friday, 15 November 1996 04:43:18 UTC