I think we found it didnt work - if you are running midgard with apache,
then the first time php loads the module (from the root file), it will
reserve all the class names and function names for all sessions. - the
memory built in functions/classes is stored in is not thread independant. -
The only option really is to use the cli or cgi version called from the
apache (eg. as a cgi-bin or exec('/usr/bin/php somescript.php'); )
regards
alan
Matthias Englert wrote:
> Emiliano wrote:
>
>> mod_midgard only sets up the database connection for requests that it
>> determines are midgard requests. So if MidgardEngine is not set, it
>> won't. But since the functions *will* be defined, I imagine they will
>> clash with the functions declared by midgard-lite.
>
>
>
> Yes but there is a solution. I run midgard and midgard-lite on the
> same machine by including midgard.so in the midgard_root file and not
> in php.ini.
>
> Matthias
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
