1) I agree with your thoughts concerning the remember* methods. But I
think the point is not that this implementation relies on the expiration
time instead of the modification time because this could be changed very
easily.
As Ralf Eggert already posted on
http://framework.zend.com/wiki/display/ZFPROP/Zend_Session_SaveHandler_Db+-+Jordan+Raub
it could be useful to be able to store permanent sessions which should
be done using remember* and forgetMe hooks.
2) Would require the user to configure 'session.save_path' instead of
'name' which doesn't make sense.
3) I think this shouldn't be implemented this way. If the user wants
this behaviour he can pass ini_get('session.name') to the configuration.
Jordan Raub schrieb:
I have a couple thoughts and concerns about The
Zend_Session_SaveHandler_Interface in general and what the
Zend_Session_SaveHandler_Db (see
http://framework.zend.com/wiki/display/ZFPROP/Zend_Session_SaveHandler_Db+-+Jordan+Raub):
1) In Zend_Session there are the methods remember*. These currently set cookie
times. Would it be better to have a hook into the SaveHandler so that the
expire time could be changed as well? I know with file system it doesn't really
matter, but with this DB implementation the future expire time is set instead
of relying on the modified time. So, maybe keep a reference to the SaveHandler
and if it is set, tell it to change its expire time.
2) What if session.save_path is used as the default for the
Zend_Session_SaveHandler_Db table name? I'm thinking a path in a file system is
analogous to a table in a database.
3) This one might be more contrived, session.name could be the default name of the data column in a Zend_Session_SaveHandler_Db database table.
Thank you,
Jordan Raub
He that teaches himself hath a fool for his master. -- Benjamin Franklin
Poor is the pupil who does not surpass his master. -- Leonardo da Vinci.
--
Felix Jendrusch <[EMAIL PROTECTED]>
