Budd, S. writes:
> > Agreed... please not such a complexity.
> >
> > Just dynamically produces a configuration script from your data base!
That's an idea. As stated in the previous mail, I think htdig should
support both, though. Ascii configuration files and SQL table configuration.
The main motive for this is scalability. Parsing a 30Mb configuration file
each time a process is run is not possible. I'm 100% with you when you
say that it would be too complex to impose this to all htdig users, though.
Less than 0.1% of them will have huge configuration files.
What do you think of the following:
. htdig internals uses an SQL table
. If no config file is found, use the content of the table
. If a config file is found, wipe out the content of the SQL table,
parse and store the config file in the table.
This way we achieve the two goals : simplicity and scalability.
FYI, I'm a MySQL user for other purposes since two years and find it
very fast, compact and reliable.
--
Loic Dachary
ECILA
100 av. du Gal Leclerc
93500 Pantin - France
Tel: 33 1 56 96 09 80, Fax: 33 1 56 96 09 61
e-mail: [EMAIL PROTECTED] URL: http://www.senga.org/
------------------------------------
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.
