Comments on: Symfony Session Timeout Annoyance… http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/ Technology Holdings Company Tue, 06 Jan 2009 08:35:34 +0000 http://wordpress.org/?v=2.5.1 By: mcnicholl http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2603 mcnicholl Mon, 02 Jun 2008 09:31:49 +0000 http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2603 Hi toolagio! Thanks for the code. I think I would expand the code slightly to test if the namespace exists (if the user is logged in) and if not - then create it by default so that all the rest of my classes don't need to think about creating the namespace if/when they need to store something there. But its all semantics :-) Hi toolagio!

Thanks for the code.
I think I would expand the code slightly to test if the namespace exists (if the user is logged in) and if not - then create it by default so that all the rest of my classes don’t need to think about creating the namespace if/when they need to store something there.

But its all semantics :-)

]]> By: mcnicholl http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2602 mcnicholl Mon, 02 Jun 2008 09:28:50 +0000 http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2602 Hi thichquay, Terribly sorry for the tardy reply - but here goes : You can find the myUser class in your application directory : your_project/apps/your_app/lib The file is called myUser.class.php. Hope this helps. Hi thichquay,

Terribly sorry for the tardy reply - but here goes :

You can find the myUser class in your application directory :

your_project/apps/your_app/lib

The file is called myUser.class.php.

Hope this helps.

]]> By: toolagio http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2563 toolagio Mon, 26 May 2008 14:25:16 +0000 http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2563 halfer is correct. The best way to do this would be to keep all items you want to expire (upon logout) in one namespace... for example loggedInUser. See below public function initialize($context, $parameters = array()) { parent::initialize($context, $parameters = array()); if($this->isTimedOut()) { $this->getAttributeHolder()->removeNamespace('loggedInUser'); } } halfer is correct. The best way to do this would be to keep all items you want to expire (upon logout) in one namespace… for example loggedInUser. See below

public function initialize($context, $parameters = array()) {
parent::initialize($context, $parameters = array());
if($this->isTimedOut()) {
$this->getAttributeHolder()->removeNamespace(’loggedInUser’);
}
}

]]> By: thichquay http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2555 thichquay Sun, 25 May 2008 15:58:54 +0000 http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2555 hello, how can I refernce the new myUser class instead of the original sfBasicSecurityUser? Also, where should I place this class at? Is it supposed to be under the same sfBasciSecurityUser folder? Thanks newbiew hello,
how can I refernce the new myUser class instead of the original sfBasicSecurityUser? Also, where should I place this class at? Is it supposed to be under the same sfBasciSecurityUser folder?

Thanks

newbiew

]]> By: mcnicholl http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2442 mcnicholl Wed, 30 Apr 2008 18:01:11 +0000 http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2442 Hi Halfer, I see what you mean. Handling the 'logout' action is simple enough. The issue described here references the timeout side of ending an authenticated session - which could not be properly handled in an action. But, yeah - application specific namespaces would be a good idea as it bundles all attributes in one space. Hi Halfer,

I see what you mean.

Handling the ‘logout’ action is simple enough. The issue described here references the timeout side of ending an authenticated session - which could not be properly handled in an action.

But, yeah - application specific namespaces would be a good idea as it bundles all attributes in one space.

]]> By: halfer http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2439 halfer Wed, 30 Apr 2008 10:59:12 +0000 http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2439 One thing you can do is to store all session attributes in an application-specific namespace. Then upon logging out, remove the namespace, rather than specific attributes, so that it clears everything. This means that as new attributes are introduced into the system, you don't have to remember to clear them up as well. One thing you can do is to store all session attributes in an application-specific namespace. Then upon logging out, remove the namespace, rather than specific attributes, so that it clears everything. This means that as new attributes are introduced into the system, you don’t have to remember to clear them up as well.

]]> By: mcnicholl http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2432 mcnicholl Sun, 27 Apr 2008 18:10:19 +0000 http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2432 Hi Fork, Good idea. Plugins for Symfony are the future... Hi Fork,

Good idea. Plugins for Symfony are the future…

]]> By: forkmantis http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2428 forkmantis Sat, 26 Apr 2008 05:04:59 +0000 http://blog.mcnicholl.com/2008/04/25/symfony-session-timeout-annoyance/#comment-2428 If this is something you'll be using in multiple projects, I'd recommend making a plugin. In our projects, I'm using sfGuardPlugin, and my own additional plugin that extends sfGuardPlugin. If this is something you’ll be using in multiple projects, I’d recommend making a plugin. In our projects, I’m using sfGuardPlugin, and my own additional plugin that extends sfGuardPlugin.

]]>