Hi Jim, On Sun, Oct 03, 2004 at 06:31:20PM -0600, Jim wrote: > > There is nothing built into ht://Dig to map users to potential search > results. If you need to adjust results on a user by user basis, you would > probably need to write some sort of wrapper script that calls htsearch and > then does the appropriate filtering before returning the results.
O.K. Then I will write a wrapper. > If instead the access control is focused more on groups of users than > individual users, you might consider building separate databases for each > group. That of course assumes a manageable number of groups and some disk > space to burn. You could then focus on restricting access at the level of > the databases (i.e. the configuration files). Without some additional > work, this approach wouldn't be terribly secure; you would need a way to > ensure that no one could provide arbitrary config file names in calls to > htsearch. Due to my aplication should be as simple as possible, I think of building only one htdig-database and restricting the returned results by parsing them and restricting them with my own db. Thank you all. Regards, Yann ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
