http://code.google.com/p/datastorage/

Xavier Pérez

Recently, I have created a new singleton class (datastorage), similar as Zend_Registry, but with namespaces and persistence included.

Would be interesting in extends Zend_Registry to make the same as my datastorage class ? Can be done ?

Thanks,

Xavier Pérez

Latest is 1.10.4 but it doesn’t look like there were any changes to Zend_Session on the latest release.

So far there’s no issues between my extension class and ZF 1.10

Any idea how it will work

If you needed config vars defined in global scope to be available within functions/class methods then all you had to do was use $GLOBALS['varname']; or the global keyword (http://php.net/manual/en/language.variables.scope.php)

I used to keep all my config vars in a globally defined $CONFIG array and access them like:
$conf = getConf();
echo $conf['dev']['email']

Or write all your classes with dependency injection in mind and make sure you pass $CONFIG to the constructor for classes that need it when you instantiate objects from them.

I also recently switched to using a singleton config class but I still access it through a function that returns the reference to the object.
echo Config()->Admin['email'];
Config()->NewsletterUrl = ‘foo.com/newsletter’;
// no, a new object isn’t created every time the config function is called

Mine still has issues tho. I’ve run into problems getting it to work with static calls (Registry::get(’foo’)) and trying to make a class that extends it still returns the base registry class instead of the child class…

Interesting question you ask re: Zend_Session_Namespace. I am actually using it too, but for simplicity didn’t discuss it in my post. I’m handling all session vars with Zend_Session_Namespace and then loading the namespace into Zend_Registry as an object.

I chose this approach because my wrapper class still gives me a one line, one statement way to access the namespace properties. To access using Zend_Session, I have to intantiate the namespace first, which creates a second (unnecessary) line of code in every place I need to access the session.

I realize my approach is overkill, but so far I’m pleased with the result.

1. You mentioned the trashing of the “singleton” pattern. Sometimes those that make arguments do it out of context. There really is no problem with the singleton pattern per-se; however, the problem is with developer mis-use/over-use of the pattern. The registry pattern is one good way to apply the singleton pattern. Another good use of the singleton pattern is with having a single entrypoint to a database connection object.

2. I have to ask: why did you chose the solution written about over simply using Zend_Session/Zend_Session_Namespace? I could be missing something but I’m not sure I understand the merit.

Again, thanks for sharing and your article was well-written.

-Wil Moore III