Hi,
Geoff Hutchison wrote:
> I expected this would be a subject that would bring out input from a lot of
> people. Right now this list numbers 65 people, and only a few messages have
> flashed back and forth.
Sorry ;) was busy.
Here's something that could be done in the database... but if that's the
smartest place to put it is another question.
In Intranet situations one has often situations that certain parts of
the intranet are inaccessible for a person. When using a searchengine
the search should not give any hits on pages a person may not access.
Some more support for this apart from the multiple db's would be a good
thing.
Some access rights could be stored within the db. But I guess this is
not practical. It would probably be more practical to make htsearch a
two layer application. A search part that supplies all hits and a filter
that filters out unwanted results depending on the authentificated user.
. err.. just brainstorming ahead. The filter could also be implemented
as a filter/collector. It could issue the search to different search
engines (working probably on different db's but having a compatible
scoreing system) collect and filter the results and then present them to
the user.
Just a few thoughts,
Ric
------------------------------------
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.
