Hi,

On 3/8/06, Piotras <ppinfoglob.com> wrote:
> > OK. The connection sitegroup is always linked to
the connection user,
> > so it makes sense to provide an API just to set
the connection user
> > and have the sitegroup deduced from the connection
user.
>
> I have no idea how to set sitegroup from apache vhot
and anonymous request though ;)

Good point. So we *do* need a
midgard_connection_set_sitegroup() method.

> 1. Loglevel
> Can I set debug or info loglevel from *php* level while
application started
> with warn leglevel then? And use debug messages from
core?

Yes. If we set up a log handler in midgard-php that routes
the
messages to the PHP log handler, then the level can simply
be
controlled with the PHP error_reporting() function.

> 2. Loghandler
> Should I use g_remove_loghandler when I change
loghandler? Or can I forget about it?

Easy, use the g_remove_loghandler() when you no longer want
to have
the messages sent to that log handler.

> Both.
> Can we have some generic GLogFunc in core so I
shouldn't worry about writing
> one GLogFunc per one application?

Yes, we can, but... There are hardly even two different
Midgard
applications that would have the same logging requirements.
Logging
under Apache is very much different from logging in a
standalone
application. A log handler is normally less than 20 lines of
code, so
I think the greater flexibility of not forcing a single
logging
mechanism on all clients greatly outweights the benefit of a
built-in
log handler.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - infoyukatan.fi
Software craftsmanship, JCR consulting, and Java
development