Comments on: CakePHP and RememberMe — AutoLogins for the soul http://blog.japanesetesting.com/2009/09/11/cakephp-and-rememberme-autologins-for-the-soul/ Design and Programming of a mISV Site Sat, 07 Jan 2012 06:25:47 +0900 http://wordpress.org/?v=2.8.4 hourly 1 By: Gilmar http://blog.japanesetesting.com/2009/09/11/cakephp-and-rememberme-autologins-for-the-soul/comment-page-1/#comment-383 Gilmar Mon, 07 Nov 2011 23:46:52 +0000 http://blog.japanesetesting.com/?p=48#comment-383 <strong>Gilmar...</strong> [...]CakePHP and RememberMe — AutoLogins for the soul » Adventures in Japanese Programming[...]... Gilmar…

[...]CakePHP and RememberMe — AutoLogins for the soul » Adventures in Japanese Programming[...]…

]]> By: Harisenbon http://blog.japanesetesting.com/2009/09/11/cakephp-and-rememberme-autologins-for-the-soul/comment-page-1/#comment-36 Harisenbon Sun, 04 Oct 2009 13:11:16 +0000 http://blog.japanesetesting.com/?p=48#comment-36 Dr. Lecter ;) No problem about the being busy! I definitely know the feeling! I would like to put the _post_login() function in the model but I didn't for two reasons: 1) I had a lot of cookie, auth->user and redirecting logic that I needed to take care of in addition to the regular data manipulation, so I couldn't take care of all of it in-model without passing a lot of references to controller-only functions. If I was dealing only with data logic, then I would have stuck it all in the model, but the cookies and Auth access is what stopped me.</li> 2) I wanted to show people how to forcibly add a controller. ;) I'm trying more and more to get the logic out of my controllers and into my models, but I find that a lack of access to cookies, session and Auth really hurt that. I hate having to pass a ton of variables whenever I want to call a simple function. I find that it ends up taking more code to prepare and pass the data to the model than it would to use a built-in model function such as find() or save() and just create the query variables in-controller. And every time I do it, I feel like a bad baker. ;) Also, regarding the cookie, I was noticing that the supplied cookie name wasn't working, nor were my attempts to change the cookie name in the config file. The line I added was merely a cheap hack to solve a problem that I really couldn't figure out. :/ Dr. Lecter ;)

No problem about the being busy! I definitely know the feeling!

I would like to put the _post_login() function in the model but I didn’t for two reasons:

1)
I had a lot of cookie, auth->user and redirecting logic that I needed to take care of in addition to the regular data manipulation, so I couldn’t take care of all of it in-model without passing a lot of references to controller-only functions. If I was dealing only with data logic, then I would have stuck it all in the model, but the cookies and Auth access is what stopped me.

2)
I wanted to show people how to forcibly add a controller. ;)

I’m trying more and more to get the logic out of my controllers and into my models, but I find that a lack of access to cookies, session and Auth really hurt that.
I hate having to pass a ton of variables whenever I want to call a simple function. I find that it ends up taking more code to prepare and pass the data to the model than it would to use a built-in model function such as find() or save() and just create the query variables in-controller.

And every time I do it, I feel like a bad baker. ;)

Also, regarding the cookie, I was noticing that the supplied cookie name wasn’t working, nor were my attempts to change the cookie name in the config file. The line I added was merely a cheap hack to solve a problem that I really couldn’t figure out. :/

]]> By: dr. Hannibal Lecter http://blog.japanesetesting.com/2009/09/11/cakephp-and-rememberme-autologins-for-the-soul/comment-page-1/#comment-33 dr. Hannibal Lecter Sun, 04 Oct 2009 00:38:25 +0000 http://blog.japanesetesting.com/?p=48#comment-33 Hi there! Sorry for my *very* late reaction, I've been slightly busy lately... Now about your modifications; wouldn't it be better to move _post_login() function to your User model? I mean, if everything you do in it is actually handling data and doesn't really have anything to do with application logic, a model is a much more logical place, don't you agree? Also, the line you added in the check() function [$this->Cookie->name = 'rememberme';] defeats the purpose of component's "cookieName" var, which should be used for customization. I don't think it should work either, I don't see it being used..? What's your opinion? Hi there!

Sorry for my *very* late reaction, I’ve been slightly busy lately…

Now about your modifications; wouldn’t it be better to move _post_login() function to your User model? I mean, if everything you do in it is actually handling data and doesn’t really have anything to do with application logic, a model is a much more logical place, don’t you agree?

Also, the line you added in the check() function [$this->Cookie->name = 'rememberme';] defeats the purpose of component’s “cookieName” var, which should be used for customization. I don’t think it should work either, I don’t see it being used..?

What’s your opinion?

]]>