<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: RAILS 2.0 Sessions</title>
	<link>http://corralesonline.com/rails-20-sessions/2008/02/13/</link>
	<description>corralesonline.com</description>
	<pubDate>Sat, 31 Jul 2010 14:44:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: brian.corrales</title>
		<link>http://corralesonline.com/rails-20-sessions/2008/02/13/#comment-1697</link>
		<dc:creator>brian.corrales</dc:creator>
		<pubDate>Thu, 14 Feb 2008 16:07:09 +0000</pubDate>
		<guid>http://corralesonline.com/rails-20-sessions/2008/02/13/#comment-1697</guid>
		<description>Yeah, you can still use whatever system you want, but I found it interesting that the rails team decided to make cookies the default.  It's definitely an improvement.</description>
		<content:encoded><![CDATA[<p>Yeah, you can still use whatever system you want, but I found it interesting that the rails team decided to make cookies the default.  It&#8217;s definitely an improvement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jimmy</title>
		<link>http://corralesonline.com/rails-20-sessions/2008/02/13/#comment-1694</link>
		<dc:creator>Jimmy</dc:creator>
		<pubDate>Thu, 14 Feb 2008 13:44:48 +0000</pubDate>
		<guid>http://corralesonline.com/rails-20-sessions/2008/02/13/#comment-1694</guid>
		<description>You can still use the old file system based session store or the database session store if you configure it correctly in the config. However, cookie sessions will help cut down maintenance issues of having to clear out old sessions.</description>
		<content:encoded><![CDATA[<p>You can still use the old file system based session store or the database session store if you configure it correctly in the config. However, cookie sessions will help cut down maintenance issues of having to clear out old sessions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
