<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<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: Another migration to Rails</title>
	<link>http://agylen.com/2005/11/28/another-migration-to-rails/</link>
	<description>Ugo Cei's Weblog</description>
	<pubDate>Mon, 08 Sep 2008 08:27:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Jon Tirsen</title>
		<link>http://agylen.com/2005/11/28/another-migration-to-rails/#comment-660</link>
		<dc:creator>Jon Tirsen</dc:creator>
		<pubDate>Tue, 29 Nov 2005 00:31:37 +0000</pubDate>
		<guid>http://agylen.com/2005/11/28/another-migration-to-rails/#comment-660</guid>
		<description>By default every controller will create a session unless you explicitly specify that a controller should not.

Regardless of the "philosophy of the web" most webapps still use session state. This goes hand in hand with the aggressive use of "sensible defaults" in Rails. Since most webapps use a session it is the default, if you at a later stage find you don't need the session you can always turn it off by explicitly overriding the default (on a controller local or application global basis).</description>
		<content:encoded><![CDATA[<p>By default every controller will create a session unless you explicitly specify that a controller should not.</p>
<p>Regardless of the &#8220;philosophy of the web&#8221; most webapps still use session state. This goes hand in hand with the aggressive use of &#8220;sensible defaults&#8221; in Rails. Since most webapps use a session it is the default, if you at a later stage find you don&#8217;t need the session you can always turn it off by explicitly overriding the default (on a controller local or application global basis).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
