James Tillman writes...
> Again, I'll recommend reading the excellent article at this URL:
>
> http://beta.devshed.com/Server_Side/search/
>
> It describes using htdig's templating feature to get it to output parsable
> data that you can turn into just about any format you want. You run
> htsearch from your shell script (the article uses PHP, but shell scripts
> would work the same way), and then parse the output to create your own web
> page. I think you'll find it much more flexible, and you won't have to hack
> the source to do it.
>
> I guess this makes my 4 cents worth now, unless saying the same thing twice
> doesn't count!
> Best of luck no matter how you decide to do it...
>
> Jamie
That URL is broken. But from your description it doesn't sound like
that is solving the same problem I am. If you have a good URL,
send it and I'll take a look.
The problem I am solving is to have multiple independant htdig
databases co-exist on the same machine (or on CD-ROM). The basic
issue I've run up against is to convince htsearch to use separate
configuration files (with no restrictions on their location) in order
to locate the proper databases.
Originally, I did not want to have to modify the httpd or htdig
installation in any way. The less stuff that isn't stock, the easier
it is to move the databases between machines. In fact, I was hoping
that I would not have to make any local additions. I even consider it
a shame that "htdig" isn't part of, say, the RedHat distribution.
That how little setup I want to have for the end users of the various
databases I want to make. One of those end users is likely to be *me*
in, say, a year when I go to setup up a new computer and want to
install my old databases. Or me in a year when I want to build a new
database and don't want to invest the time to learn htdig all over
again.
I finally ran into the brick wall of needing to pass the -c option to
htsearch on a GET request. And I came to the conclusion that I was
going to need a shell script installed into cgi-bin to do it. It is
unfortunate that htsearch isn't more flexible out of the box. I
really didn't want to have to tell users that they have to install
special versions of htsearch or even a 5 line shell script. But given
those two alternatives, I'll take the latter.
Gilles posted an excellent idea on what that shell script should
contain, and I think I am going to wrap htsearch that way.
-Rick
--
Rick Richardson [EMAIL PROTECTED] http://RickRichardson.freeservers.com/
My current CI is 28. I'm 41. I need 14 more cylinders by my next
birthday. Two PWC's and an SUV ought to do it. Thats my new goal.
------------------------------------
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.
