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

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

> Hi,
 
> > 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.

Something like this I think. Or we can mark this function ( method ) as internal one.
BTW, I think we need object's internal sitegroup "handler". 

1. Login as SG0 admin 
2. Get object from SGX
3. Update

Object's sitegroup won't be changed , but all other operations depend on mgd_sitegroup
(midgard_connection_get_sitegroup in a future ), so once you are logged in as SG0 user 
you break other records ( like quota ). 
 
> > 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.

ok , if we must use php error_reporting... :/
 
> > 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.

OK, so it's a matter of creating app's loghandler. This is what I wanted to avoid.
I need to provide loghandler's handler for midgard-schema, midgard-query, midgard-php now.
 
> > 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. 

I know, that's why I wonder how to resolve this for midgard-php.

Piotras