Re: Clarification on the indexer

Anselm I think your are right insaying we would want to
modify the indexer itself... our site is made up of a collection
of materials that are....
HTML Documents
CGI (Lots of CGI)
Documents from an imaging system (FAXes mainly)
Dynamic Information coming from our engineering group

and all of this information is either...
Completely accessable
filtered
or not available
according to the users security privledge and
the objects access privledge

if the information is not available
I dont want the user to know its there
..our goal here was to have a site that would not say no,
it would onlt make available the items that are accessable
to the user.

All of these objects are registered within a 
Sybase RDBMS along with the users and all of the security
info needed to do this. our current project is PERL based
but afer reading your initial papers on Jigsaw and working
with the alpha we could see that we could intigrate many of our back-end 
cgi applications into the httpd.  

This is where the indexer came in as an issue. I think if we could index
on the fly from our RDBMS instead of the default method according to the 
users access, we could bypass the need for cgi (or resource) controlled 
indexes and document serving.

I hope this clears up my initial question.

Bruce Nelson

On Sun, 1 Sep 1996, Anselm Baird-Smith wrote:

> Bruce Nelson writes:
>  > Anselm...
>  > 
>  > I was curious after reading your latest description
>  > of the new release of what was the final decision on 
>  > how the indexer would work -- our needs are as follows
>  > our site currently is using a Sybase RDBMS back-end
>  > to handle security, dynamic indexing and filtering we have 
>  > a pretty good port of Syb-Java (Sybase Java) and have
>  > done some preliminary testing with Jigsaw's resources.
>  > The places that were we have been focusing on the most
>  > are the Auth filters, Directory resource, CGI resource and
>  > the indexer. Our hope is that the indexer will allow
>  > for modifications/ehancements such as ours and still be
>  > the indexer, but builds its indexes from foriegn sources.
>  > -- I am reffering earlier email you had sent (last month?)
> 
> Am I right in saying that you want to customize the indexer itself ?
> That's interesting, I haven't though ot it before. My main concern was
> to be able to implement resource stores on top of a database, but
> that's another issue.
> 
> For tha uth filter, you probaly need to rewrite some parts of the
> existing GenericAUthFilter to make it access the DB (not a big deal, I
> think).
> 
> For remaining resources, my understanding is that you want to index
> them, according to some infos you have available in your RDBMS. If
> this is the case, then you will have to redefine the ResourceIndexer
> class...
> 
> Anselm.
> 
>  > P.S. Shouldn't you be helping with that new baby ?? 
>  >      instead of answering e-mail :-)
> 
> Yes, I should ! But my typing rocks him - "le berce" in french - ;-)
> 
>

Received on Monday, 2 September 1996 04:25:18 UTC