I just saw the post of XML output of ht://dig
results patches.
I was wondering about this.. Going through
the code on 3.2.0b4 (or atleast the cvs pull that I had like about 2 months
ago), I was wondering why the work for the search is done in such a very tightly
coupled fashion with the display logic.
Only an idea or a suggestion...encapsulate the
search functionality into a subsystem whereby you can retrieve structured
information back from the search system. This way we could, as developers
of other projects, be able to embed the ht://Dig search engine into other
projects and or products.
Just an idea. I don't know how much it would
impact performance though.
|