<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: authlogic: Another Take on Rails Authentication</title>
	<atom:link href="http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html</link>
	<description>Daily Rails news, views, tips, and joy</description>
	<lastBuildDate>Fri, 12 Mar 2010 12:24:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Amol Hatwar (rubygem)</title>
		<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/comment-page-1#comment-541</link>
		<dc:creator>Amol Hatwar (rubygem)</dc:creator>
		<pubDate>Wed, 11 Mar 2009 21:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/?p=145#comment-541</guid>
		<description>Goes to say that less is indeed more :).</description>
		<content:encoded><![CDATA[<p>Goes to say that less is indeed more :).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam</title>
		<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/comment-page-1#comment-526</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Tue, 10 Mar 2009 04:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/?p=145#comment-526</guid>
		<description>No offense to Rails core, but RESTful authentication is heavy and intrusive.  It just doesn&#039;t make any sense.  A user&#039;s session is an instance of a model, UserSession. Enough said.</description>
		<content:encoded><![CDATA[<p>No offense to Rails core, but RESTful authentication is heavy and intrusive.  It just doesn't make any sense.  A user's session is an instance of a model, UserSession. Enough said.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Johnson</title>
		<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/comment-page-1#comment-125</link>
		<dc:creator>Ben Johnson</dc:creator>
		<pubDate>Mon, 10 Nov 2008 04:40:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/?p=145#comment-125</guid>
		<description>Great post, thanks for promoting this.

reck, you make some good / obvious points. But where do sweepers lie in the MVC architecture? In my opinion, they blur the lines of the MVC structure a little bit too, but they make expiring caches extremely easy. They are connected to models, who ultimately trigger if caches expire or not. I just took that same idea and applied it to sessions.

Lastly, the UserSession doesn&#039;t have to be labeled as a model. Why not label it as a controller utility? You can extract controller logic out into a class. I recommend putting it in the models directory to emphasize that it can be used like a model, which ultimately fits into the conventional style of RESTful development. But it could just as easily fit in your lib directory. Just something to get people to look at this from a different angle, hopefully this clarifies my perspective on the library.</description>
		<content:encoded><![CDATA[<p>Great post, thanks for promoting this.</p>
<p>reck, you make some good / obvious points. But where do sweepers lie in the MVC architecture? In my opinion, they blur the lines of the MVC structure a little bit too, but they make expiring caches extremely easy. They are connected to models, who ultimately trigger if caches expire or not. I just took that same idea and applied it to sessions.</p>
<p>Lastly, the UserSession doesn't have to be labeled as a model. Why not label it as a controller utility? You can extract controller logic out into a class. I recommend putting it in the models directory to emphasize that it can be used like a model, which ultimately fits into the conventional style of RESTful development. But it could just as easily fit in your lib directory. Just something to get people to look at this from a different angle, hopefully this clarifies my perspective on the library.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: reck</title>
		<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/comment-page-1#comment-117</link>
		<dc:creator>reck</dc:creator>
		<pubDate>Thu, 06 Nov 2008 23:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/?p=145#comment-117</guid>
		<description>The fact that the User model deals with sessions and cookies concerns me a bit. I&#039;m not a purist, but it breaks the MVC lines enough to give me pause.</description>
		<content:encoded><![CDATA[<p>The fact that the User model deals with sessions and cookies concerns me a bit. I'm not a purist, but it breaks the MVC lines enough to give me pause.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Cooper</title>
		<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/comment-page-1#comment-116</link>
		<dc:creator>Peter Cooper</dc:creator>
		<pubDate>Thu, 06 Nov 2008 18:57:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/?p=145#comment-116</guid>
		<description>I haven&#039;t updated the template yet, but note that this post was written by Mike Gunderloy. One of Rails Inside&#039;s new writers :)</description>
		<content:encoded><![CDATA[<p>I haven't updated the template yet, but note that this post was written by Mike Gunderloy. One of Rails Inside's new writers :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruno Carvalho</title>
		<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/comment-page-1#comment-115</link>
		<dc:creator>Bruno Carvalho</dc:creator>
		<pubDate>Thu, 06 Nov 2008 18:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/?p=145#comment-115</guid>
		<description>Certainly a great plugin, way better than the intrusive Restful Authentication.

Thanks for sharing this...</description>
		<content:encoded><![CDATA[<p>Certainly a great plugin, way better than the intrusive Restful Authentication.</p>
<p>Thanks for sharing this...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vitor Pellegrino</title>
		<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/comment-page-1#comment-114</link>
		<dc:creator>Vitor Pellegrino</dc:creator>
		<pubDate>Thu, 06 Nov 2008 13:48:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/?p=145#comment-114</guid>
		<description>OMG, i think this is one of the best news of this year. 
I could not stand anymore the intrusive way that Restful Authentication treated this problem.</description>
		<content:encoded><![CDATA[<p>OMG, i think this is one of the best news of this year.<br />
I could not stand anymore the intrusive way that Restful Authentication treated this problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alistair Holt</title>
		<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/comment-page-1#comment-113</link>
		<dc:creator>Alistair Holt</dc:creator>
		<pubDate>Thu, 06 Nov 2008 12:05:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/?p=145#comment-113</guid>
		<description>Great. I&#039;ll give this a try!</description>
		<content:encoded><![CDATA[<p>Great. I'll give this a try!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Holden</title>
		<link>http://www.railsinside.com/plugins/145-authlogic-another-take-on-rails-authentication.html/comment-page-1#comment-111</link>
		<dc:creator>Mark Holden</dc:creator>
		<pubDate>Thu, 06 Nov 2008 07:17:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.railsinside.com/?p=145#comment-111</guid>
		<description>Thanks for posting this, this is really nice. Definitely going to be my choice for authentication in my next app.</description>
		<content:encoded><![CDATA[<p>Thanks for posting this, this is really nice. Definitely going to be my choice for authentication in my next app.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
