[EMAIL PROTECTED] wrote:
>
> Hi,
Hi
> After looking into the new configuration code, I figured that having
> several configuration contexts organized in a hierchical manner is a
> very nice thing. This is what new configuration code does for a
> specific case (url/server...). It would be nice to have this work in a
> general case, so I'm going to try implementing that.
What do you mean?
I thought about something like this:
<something1: bla-bla>
xxx:yyy
zzz:qqq
<something2: bla2-bla2>
www:eee
rrr:ttt
</something2>
</something1>
And interface:
a=conf["something1=bla-bla:xxx"] //a=yyy
a=conf["something1=bla-bla|something2=bla2-bla2:www"] //a=eee
> Furthermore, the code in Configuration.h/.cc has been made HtDig
> specific ( by including dcServers, dcUrls and URL.h ). I would
> therefore like to split Configuration into Configuration and
> HtConfiguration, thus keeping Configuration as a general purpose
> library member and HtConfiguration that would be htdig specific.
There's a problem: url needs a pretty specific comparation.
So that we need some new class
ConfigItem something1 with virtual methods.
And url,server derived from ConfigItem with redefined search,compare
methods.
I left all these tasks fore the second iteration :)
> In the context we're developing in (mifluz), htlib is used as an
> independent library, and we don't use nor have htcommon. So our code
> doesn't compile anymore (since I cvs updated).
>
> This will probably delay my commit of the compression code for few
> days.
:(
If we are talking about config, I thought about another 2 things:
1. stronger syntaxis.
I mean avoid stupid typo: "max_dic_size" instead "max_doc_size"
2. Usage in conf.[yl] String class instead char*.
Vadim.
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
