I am assuming you're talking about collections support to search multiple
databases?
According to [EMAIL PROTECTED]:
> Appears that this has been supported since 3.20b2.
>
> I'm interested in it because of some problems executing htmerge on 3.20b2
> (performance/memory requirements).
>
> A. Is all result-related information obtained from the
> first-accessed config file?
No. This depends what you mean by result-related. Arguably, the
database_dir and database_base attributes are result-related, as the
results are derived from these, but obviously htsearch will search the
database defined in each of the specified config files. All the result
formatting attributes are taken from the last config file, not the first,
because the formatting is done after all databases are searched.
The safe thing to do is just to define the database_dir or database_base
in each config file, and then include a common config file that contains
all the other attributes. That way, you know the attributes are all set
consistently for all config files in the collection, regardless of when
htsearch uses them.
> B. If I specify config_dir in the first-accessed config
> file, will this result in all other files being obtained
> from [config_dir]?
No. config_dir is essentially intended to be a read-only variable, so you
can refer to the hard-coded CONFIG_DIR value in other attribute settings.
Although you can change the value of config_dir, this will have no effect
on where htsearch will look for config files. htsearch only looks at
the CONFIG_DIR environment variable, if set, or the CONFIG_DIR makefile
variable set at compile-time.
> =============================================================
> C. Is it still supported in 3.20b3 (doc is not clear)?
Still supported, but unfortunately still mostly undocumented. The author
had submitted sample forms and config files with his patches, but they
never made it into the source tree.
> D. Does it appear to work properly under 3.20b2 and 3.20b3?
I don't think it's changed much from b2 to b3, other than the fact b2
would add an extra config= parameter to the URLs for the PAGELIST buttons.
We've had sketchy reports of some problems still existing with this code,
but not much that we could really nail down as a bug.
> E. Does there appear to be a major performance penalty (especially in a
> Linux installation)?
Depends what you consider major, and how many databases you're searching.
Searching multiple databases will be slower than searching one combined
DB, but we don't have any performance figures to give you.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
