Re: MidgardConfig comments (Was: [midgard-dev] Automake and directories)

Hi,

On 2/18/06, Piotras <[email protected]> wrote:
> > Will the configuration files within that directory have a suffix (.ini/.conf/...) or not?
> > These need to be decided and documented.
>
> I think this should be a matter of convention. Both should work IMO.
> 'filename' and 'filename.conf' passed as argument

Its better if there is just one clearly defined mechanism. Having
equivalent alternatives is usually a bad thing in an API.

My suggestion would be to pass just a generic configuration "name" as
an argument and let the implementation decide the location and name of
the corresponding configuration file. A possible Windows port might
well want to use a different directory layout and naming convention.

> I fully agree with you. What I would like to suggest is to change ini file syntax
> that way so we could use current parser and make GKeyFile support after 1.8.

I'm fine as long as the config file syntax follows a well specified
standard already in 1.8.

> ok , just tell me how can I know using three log files that this query is executed
> before this php function and after this apache call?

In fact the situation at the moment is that you have three different
log files: the Apache error log, the Midgard log, and the MidCOM log.
It's possible to have them all pointing to the same place but
currently that needs special attention. It would be better if all the
logs would go to the Apache log and follow the Apache LogLevel by
default, but you could still point the logs elsewhere if you really
wanted to.

To illustrate my point I found your own comment (carelessly taken out
of context :-) from December: "Typical midcom log file is empty and I
have no idea how to define new log file or even log level." (See
http://permalink.gmane.org/gmane.comp.web.midgard.devel/6345)

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - [email protected]
Software craftsmanship, JCR consulting, and Java development