directory indexing

Mark I. Lubin writes:
 > That's the story with the indexing of directories. First, I got
 > indexing Ok following the documentation. Then I found that all
 > resources in the directory do not disappear after I physically
 > removed them from the disk ( I mean just simple files here). Thanks to
 > the mailing list I found that it is because of alpha status of
 > Jigsaw and for now I have to delete file .jigsaw manually to get
 > rid of old stuff.  OK, I did it.  But then I could not get 
 > any .jigsaw back even I hit 10 times button OK in corresponding
 > form.  After a lot of trial and error I found that is because of
 > Netscape's cache,  so if you use as a browser netscape you have to
 > frequently flash cache. Well,  after that I thought that I 
 > learned something but then I found  that  some resources are not
 > indexing right anyway even I flash Netscape's cache and push 
 > button OK in corresponding form or even restart Jigsaw.

I am using Nestacpe in my everyday life, and haven't yet encountered
the problem you mention (I don't flush my nestacpe cache and
everything still works fine). 

Again, Jigsaw write the .jigidx files only when it thinks it is a good
time to do so, and in your case it is when Jigsaw exists. So if you
actually want to *see* the changes, you will have to kill Jigsaw
(using /Admin/Exit), and then use the nice trick.

There is still something I don't understand: how you generated these
buggy .jigidx file. I think I remember some situations where the
SimplResourceStore main method won't be able to restore some resources
(because it is not run in the full server environment). This may be
the casue of the exception you see. Do you see the same exceptions
when running Jigsaw and accessing the same resources ?

Anselm.

Received on Friday, 5 July 1996 18:45:35 UTC