Hi, Sorry for the delay to reply. Thank you for the answer.
I think this was happening because the session.save_handler was set to memcache, instead of files. In any case, the clear session solution fixed the problem. Regards, Fernando Morgenstern [email protected] Em 24/05/2011, às 15:29, Marco Pivetta escreveu: > This happens because you're using the session storage, which writes at the > end of the request. You can enforce a logout by doing something like: > > Zend_Auth::getInstance()->clearIdentity(); > Zend_Session::close(); > > That should do the job and commit the logout to the session. > Otherwise, you'll have to implement your own auth storage. > > Marco Pivetta > @Ocramius > http://marco-pivetta.com > > > > On 23 May 2011 20:15, Fernando Marcelo <[email protected]> wrote: > Hi, > > I am having some issues with Zend_Auth. I have an application that sends Ajax > requests every X seconds to server. Depending on what happened, this request > can take a few seconds to be processed. > > What i realize is that clearIdentity doesn't work if there is another request > for the same user. > > To test this what i did was to prepare two actions: > > 1) Logout action: a simple call for clearIdentity() > 2) Process action: an action that have a very long sleep() call > > If i call only logout action, it works ok. > > But if i can logout action at the same time that the process action is being > ran, them logout simply doesn't work. I can call hasIdentity() right away and > it will return true. > > I was wondering if someone else had this problem and if there is a good > solution? > > Regards, > > Fernando Morgenstern > [email protected] > > > > > > -- > List: [email protected] > Info: http://framework.zend.com/archives > Unsubscribe: [email protected] > > >
