Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="http://framework.zend.com/manual/en/zend.session.global_session_management.html" rel="nofollow">Zend session management</a> has the option to <a href="http://framework.zend.com/manual/en/zend.session.advanced_usage.html" rel="nofollow">expire</a> namespaces by 'hop' or time-based, you can also write lock the session via Zend_Session::writeclose or destroy it using Zend_Session::destroy() (ref: <a href="http://framework.zend.com/manual/en/zend.session.global_session_management.html" rel="nofollow">http://framework.zend.com/manual/en/zend.session.global_session_management.html</a>)</p> <p>destroy():</p> <blockquote> <p>destroy(bool $remove_cookie = true, bool $readonly = true) Zend_Session::destroy() destroys all of the persistent data associated with the current session. However, no variables in PHP are affected, so your namespaced sessions (instances of Zend_Session_Namespace) remain readable. To complete a "logout", set the optional parameter to TRUE (the default) to also delete the user agent's session id cookie. The optional $readonly parameter removes the ability to create new Zend_Session_Namespace instances and for Zend_Session methods to write to the session data store. </p> </blockquote> <p>writeClose():</p> <blockquote> <p>writeClose($readonly = true) Shutdown the session, close writing and detach $_SESSION from the back-end storage mechanism. This will complete the internal data transformation on this request. The optional $readonly boolean parameter can remove write access by throwing an exception upon any attempt to write to the session via Zend_Session or Zend_Session_Namespace. </p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload