title: Zend Session destroyed if page requested too quick
body: <p>My application is not built on MVC pattern but it partially using Zend Framework components like Config, Loader, Session, Auth, Service and XmlRpc.</p>
  
  <p>Recently I have discovered that in some occasions, if user would navigate through pages too fast or press <kbd>F5</kbd> too quick, his session would be destroyed and he would be logged out of the system. There is a <a href="https://stackoverflow.com/questions/3753481/zend-session-expires-when-refreshed-many-times">similar question</a> but his solution did not helped me to solve this issue.</p>
  
  <h3>How the application works</h3>
  
  <p>Session Config:</p>
  
  <pre><code>cookie_domain = ".mydomain.com"
  name = "myApplicationName"
  remember_me_seconds = 864000
  save_path = "/path/to/my/session/storage/"
  save_handler = "files"
  strict = true
  use_only_cookies = true
  </code></pre>
  
  <p>On page initialisation:</p>
  
  <pre><code>$config = new Zend_Config_Ini(CONFIG_DIR . 'session.ini');
  
  Zend_Session::setOptions($config-&gt;toArray());
  
  Zend_Session::start();
  </code></pre>
  
  <p>Account Controller:</p>
  
  <pre><code>function __construct(...)
  {
      /**
       * @var $session Zend_Session_Namespace
       */
      $session = Zend_Registry::get('Zend_Auth');
  
      if(isset($session-&gt;identity))
      {
          Zend_Session::rememberMe();
      }
  }
  </code></pre>
  
  <p>Log out process:</p>
  
  <pre><code>if(isset($_GET['logout']))
  {
      Zend_Session::destroy(TRUE);
  }
  </code></pre>
  
  <p>Did any one else experienced this issue and have some clues what can be wrong and how to fix it?</p>
  
  <h3>Update</h3>
  
  <p>I have disabled <code>Zend_Session::rememberMe()</code> and everything seems to work fine now. As I understand, on every request this method refresh <code>session_id</code> and rename session file, and due to read/write performance issue it cannot find newly created session, and because of that session handler is lost.<br>
  Just wondering, would changing session storage to database could fix this issue?</p>