Re: MidgardConnection (Was: [midgard-cvs] CVS update: /midgard/src/core/midgard/midgard/)

"Jukka Zitting" <[email protected]> wrote:

> Hi,

> > 1. I removed set_sitegroup as this should be done in mgd_auth function
> > or other way for hosts. I am not sure if such feature should be handled by such API.
> 
> 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 ;)

> > 2. I still keep set(get) loghandler. Of course we can remove it if g_remove_loghandler
> > doesn't need to be used.
> >
> > 3. loglevel is still kept as there should be possibility to change loglevel from any level.
> > And such change should affect also midgard-core , which uses the same connection
> > with loglevel info.
> 
> -1. Let me repeat, midgard-core should *not* attempt to handle the log
> messages it creates. It is the task of the application that registers
> the log handler to determine the log level to be used.

Just easy, I still misunderstand something.

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?

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

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

Piotras