|
|
|
[
Permlink
| « Hide
]
Wil Sinclair - 18/Apr/08 01:11 PM
This doesn't appear to have been fixed in 1.5.0. Please update if this is not correct.
How does this benefit over using a smarter naming convention for the namespaces? For example like
$user = new Zend_Session_Namespace("user-auth"); OR over $user = new Zend_Session_Namespace("user-auth"); $user->auth->node2 = 'value'; ? The bigger problem with adding more/deeper nodes is that the serialized version will take up more space in the file/database whatever. Ill categorize as nice to have / next minor, but at currently I am not completely convinced yet. Perhaps talk it over in #zftalk.dev with some other people. -ralph That's what I've been doing these days but it involves a lot of consistent code and work to maintain data in appropriate nodes. If we have the namespace created in a deeper node, keys added to the namespace automatically appear in the child node of the namespaced node and so it becomes much easier to maintain data and focus on business logic. Furthermore, the items under the namespace node can now be counted, can be disabled from adding more keys than a specified threshold, configured to expire, etc. and so we can create categorized namespaces with typical behaviors for the data inside the namespaces.
Interesing feature, but I am not sure we'll have time to implement this within the 1.0 branch.
We concede that this component needs a rewrite, so ideas are being logged here: http://framework.zend.com/wiki/display/ZFDEV/Zend_Session+2.0 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||