Re: Clarification on the indexer

This is the kind of thing that we need also. Is the ResouceIndexer
interface intedned to address this sort of thing?

-Mark

Dave Makower wrote:
> >...
> >public interface ResourceIndexer {
> >     public Resource createDirectoryResource(File directory
> >                                             , String name
> >                                             , Hashtable defs);
> >
> >     public Resource createFileResource(File file
> >                                        , String name
> >                                        , Hashtable defs);
>
> YES!!! This would fit very nicely into a project we're working on, where we
> would like to use the indexer to create "virtual directories" of
> information that might not exist on the server at all.  Instead, there are
> repository files (like .jigidx files) containing metadata, which is used to
> obtain/synthesize/present the information on the fly when it is accessed.
> By using a different indexer implementation, we could better integrate the
> creation of these metadata repositories into the Jigsaw architecture.
> 
> What if, instead of CreateFileResource(), there were something more
> general, like CreateHTTPResource() or CreateContainerResource(), or
> something of that ilk?
> 
> Our "virtual directories" are not instances of DirectoryResource, nor are
> our leaf resources instances of FileResource.  Instead, we are using more
> abstract definitions specific to our architecture.  Our
> VirtualContainerResource and LeafResource classes are, in fact, descended
> from FilteredResource.  The reason for this is that DirectoryResource is
> currently written in such a way that it must contain files/directories, and
> our "virtual containers" contain more abstract entities.

Received on Thursday, 5 September 1996 13:03:40 UTC