At 7:04 AM -0400 9/20/99, Tillman, James wrote:
>We had checked out the perl-wrappers, and had the same thoughts. Looking
>over the source of htsearch.c, we're thinking it would be easy to work up a
>C++ class version of it that we could use from our XS code. Then all we'd
>have to do when the main htdig project brings out a new release is merge the
>new htsearch.c changes into our htsearch class. We want to avoid
>duplicating the logic in htsearch.c in our own code (esp. since it's likely
>to change as time goes by). Comments?
I'm not quite sure what you mean by a C++ class version. Do you mean
moving more of the logic of htsearch.cc into a new C++ class?
>One other concept we had in mind was a database indexing system. Since
>ht://Dig requires a web server's http 1.0 responses to index a site (this
>_is_ still true, right?), we thought the ideal solution would be to set up a
>database-reader daemon that spoke http 1.0 and returned the database results
This would work. It's obviously not particularly efficient, since
it's wrapping every response in HTTP. But for now, it will work. Part
of the 3.2 rewrite is to generalize the HTTP protocol code to allow
different methods, including an "External Transport" protocol,
similar to the external_parsers hook. In this case, you could simply
write a Perl DBI module that would output the data as an External
Transport module.
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
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.
