Torsten Neuer (email@example.com)
Wed, 28 Apr 1999 17:55:37 +0200
According to Andrew Scherpbier:
>Even though I am not actively working on ht://Dig anymore, I do read all
>the messages on the lists and still think about all this stuff on a
>regular basis... I want to plant a seed:
>It seems to me that there are quite a few people that use php3 (or perl
>or whatever) to parse output from htsearch. The reasons are quite
>My suggestion is to maybe look into making php3 a plugin into htsearch
>so that the output template processing can be done directly by php3
>instead of the simple variable substitution of htsearch itself.
>Not knowing a whole lot about the workings of php3, I am saying this
>simply to plant a suggestion.
From my point of view it depends on what PHP will be used for in ht://Dig.
If you use it to make the template processing even more configurable, I
think it would be a slight overkill. On the other hand, a plugged-in PHP
interpreter (or a Zend engine) cannot do the stuff PHP will do when used
to postprocess the results from a htsearch. Wrappers tend to be quite
site-specific.. using includes and such. There might even be code that
is absolutely dynamic with regards to the referring URL or the request URI
which is what might blow a PHP plug-in.
Ht://Dig is a tool for searching a web-site - and it should stay that way.
If some folks need to mess around with the search results other than just
by rewriting the HTML stuff that encloses the results, they should do it
the way they like to... PHP, ASP, CGI, Java... whatsoever.
>It seems to me that the guts of php3 can either be put into a shared
>library that is loaded by htsearch at runtime (hey, I am a Java guy
>now... runtime loading of code is my life!) or it could possibly be
>linked into htsearch directly.
>Maybe something even more strange would be to compile/load the
>functionality of htsearch into php3 itself. (I've seen all kinds of
>different database bindings for php3, so why not htsearch?)
The latter would be the best approach since it leaves ht://Dig basically
as it is now and eases the task of post-procesing htsearch results.
It also should be easier to do, since it would just resemble the execution
of htsearch and scanning the returned array. Combined with the new Zend
backend for PHP, this could significantly increase the performance of a
>Anyway... Back to the real world. :-)
Have fun ;-)
-- InWise - Wirtschaftlich-Wissenschaftlicher Internet Service GmbH Waldhofstraße 14 Tel: +49-4101-403605 D-25474 Ellerbek Fax: +49-4101-403606 E-Mail: firstname.lastname@example.org Internet: http://www.inwise.de ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to email@example.com containing the single word "unsubscribe" in the SUBJECT of the message.
This archive was generated by hypermail 2.0b3 on Wed Apr 28 1999 - 09:20:50 PDT