[dev] [commits] Horde branch master updated. 1d8ff2de823315dc95e72b00ffe5e73595d31e17

[Gunnar Wrobel]

Hi Micheal,

Quoting Michael M Slusarz <slusarz at horde.org>:

> Quoting Gunnar Wrobel <p at rdus.de>:
>
>> Would it be okay to extract Horde_Session from "Core" into its own  
>> package? "Kolab_Session" works with the session object and depends  
>> on its interface. But as the framework packages must not depend on  
>> "Core" having Horde_Session in there is a problem. I assume there  
>> might be other packages working with the session as well.
>>
>> I checked the dependencies of Horde_Session and it looks like such  
>> an extraction should be no problem.
>>
>> Or is the intention to handle all session data retrieval/storage  
>> within "Core"?
>
> The intention of Horde_Session is that it is horde/Core specific.   
> The design idea was that if you need session access in another  
> package, write a session storage driver that directly accesses  
> $_SESSION.  For use of this package in Horde, we use a  
> Horde-specific session storage driver that instead uses Horde_Session.
>
> See, e.g., Horde_Prefs_Cache_Session and Horde_Core_Prefs_Cache_Session.

ah, okay. I was mislead by the many $GLOBALS['session']->get('horde',  
... we still have in the code. Thanks for the Prefs example, I'll fix  
the areas I'll be touching accordingly.

Cheers,

Gunnar

>
> michael
>
> -- 
> ___________________________________
> Michael Slusarz [slusarz at horde.org]
>
>
>
> -- 
> Horde developers mailing list - Join the hunt: http://horde.org/bounties/
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>