Re: [dev-serveez] Avoiding code fork/duplication of serveez cfg code

[stefan]

On 26 Nov 2002, Andreas Rottmann wrote:

> Hi!

Hello!

> Another option would be to re-write the config stuff of serveez for
> greater generality, abstracting it, so it's not tied up so closely with
> the servertype code. What i have in mind is an interface like that:
>
> svz_config_t *svz_config_instantiate(svz_config_prototype_t *);
> void svz_config_change(svz_config_t *, svz_config_modifier_t *);
> ...
>
> That could then be used by the servertype code (probably retaining at
> least a good deal of API compatibilty).
>
> Before I start hacking serveez, I wanted to hear some comments (/me
> goes to put flamethrower-resistant clothes on ;-)).

If I understand correctly:  You are missing some kind configuration
possibility in Serveez?  What is it exactly?  Maybe we can add that in a
future release...

I always thought we covered *all* kinds of configuration items.  The only
thing I can imagine are encapsulated structures which are missing.  If
this is your point, I may think about getting it into Serveez someday.

Cheers,
        address@hidden