You can also get around the "hiding" problem, by setting the restrict_url via a htsearch2.cgi, which appends the restrict and calls the original htsearch.cgi. -----Urspr�ngliche Nachricht----- Von: Geoff Hutchison [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 25. Juli 2000 18:53 An: alan Cc: [EMAIL PROTECTED] Betreff: Re: [htdig] using htdig in two separate sections of a website On Tue, 25 Jul 2000, alan wrote: > to index the entire site and use restrict in the form and only run > rundig for the entire site?? This will be more space efficient. There's a small amount of overhead in the database structures, so I usually prefer this route. The catch is that the form is open for everyone to see and it's not to hard to imagine that you could change the restrict value to get other information. If it's simply an issue of public sections, then there isn't a problem. But if you want to "hide" some of the data, then you probably want a separate database. -- -Geoff Hutchison Williams Students Online http://wso.williams.edu/ ------------------------------------ To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this. ------------------------------------ To unsubscribe from the htdig mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
