[EMAIL PROTECTED] wrote:
> 
>  >      parser which recognise <server: http://www.......>
>  >                              wait_time:      10
>  >                              max_hop_count:  999999
>  >                              ........... :   .....
>  >                              </server>
>  > and insert it into config
> 
>  Just an idea, for the future. I don't know if everyone agree with
> the fact that at some point htdig will use an SQL database for things
> like documents database. If this is the case, I think that the
> configuration file could be loaded in a SQL table.
>  The main argument in favour of a database version of the configuration
> file is scalability. I currently have a search engine (not htdig)
> that contains 150 000 starting points for exploration (servers). It
> is hard if not impossible to manage such a list in a flat file (people
> submit new URLs to the search engine, two personns review from 600 to 1000
> submissions each day).

I don't like the idea of having the whole configuration set in a sql
database.  It makes it hard to deal with when no sql is available.  (We still
want to allow ht://Dig to be used *without* external database tools)  It also
makes it almost manditory to create tools to maintain the configuration.  A
simple text based configuration file like what exists now should be used at
all times.

However, I think it is a great idea to allow values to be located in a sql
database.  As you know, the current configuration file allows for the
expansion of a whole file as an attribute value.  We can easily extend that
sort of mechanism to include other data sources.
I personally like the idea of allowing URLs to be specified as data sources. 
The file inclusion will need to be changed to use the "file:" protocol.  sql
data inclusion could be changed to something like
"odbc:server:instance:username:password:select+value+from+table" or
"sql:select+value+from+table" if there is only one sql connection type
available at the time.

By also adding support for the "http:" protocol, the configuration can be
made a lot more distributed as well.

>  Cheers,

Proost,
-- 
Andrew Scherpbier <[EMAIL PROTECTED]>
Contigo Software <http://www.contigo.com/>

------------------------------------
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.

Reply via email to