<?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"
	>
<channel>
	<title>Comments on: Working on the Rails Road</title>
	<atom:link href="http://comments.deasil.com/2007/03/12/working-on-the-rails-road/feed/" rel="self" type="application/rss+xml" />
	<link>http://comments.deasil.com/2007/03/12/working-on-the-rails-road/</link>
	<description>escape colon w q</description>
	<pubDate>Sat, 22 Nov 2008 03:45:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: felix</title>
		<link>http://comments.deasil.com/2007/03/12/working-on-the-rails-road/#comment-201</link>
		<dc:creator>felix</dc:creator>
		<pubDate>Mon, 12 Mar 2007 16:28:35 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/03/12/working-on-the-rails-road/#comment-201</guid>
		<description>No general rule, but as an example. In the ruby book, session information is keyed off a cookie (which is how I understand most reasonably places do it now - url mungeing is so late 90's). So to get your cart information you first lookup your cart id in the session, which equates to looking up the session key in a table to get the cart id and then look that up. I would simply put the session id directly into the cart - this saves you a database hit and gives you some flexibility to play around with session key - convert that into a longer term key that doesn't expire over the sesion, etc.

Also, storing some info in cookies. This is a more than reasonable way to store a small amount of information, it also helps make you frugal in your attempts to impart state to this wonderfully stateless protocol. Now that I think about it, I like my web url's to kind of be Functional in the sense of Functional Programming. Some state is ok, but keep it minimal and use cookies and direct links in the database to handle those needs.</description>
		<content:encoded><![CDATA[<p>No general rule, but as an example. In the ruby book, session information is keyed off a cookie (which is how I understand most reasonably places do it now - url mungeing is so late 90&#8217;s). So to get your cart information you first lookup your cart id in the session, which equates to looking up the session key in a table to get the cart id and then look that up. I would simply put the session id directly into the cart - this saves you a database hit and gives you some flexibility to play around with session key - convert that into a longer term key that doesn&#8217;t expire over the sesion, etc.</p>
<p>Also, storing some info in cookies. This is a more than reasonable way to store a small amount of information, it also helps make you frugal in your attempts to impart state to this wonderfully stateless protocol. Now that I think about it, I like my web url&#8217;s to kind of be Functional in the sense of Functional Programming. Some state is ok, but keep it minimal and use cookies and direct links in the database to handle those needs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://comments.deasil.com/2007/03/12/working-on-the-rails-road/#comment-200</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Mon, 12 Mar 2007 15:32:28 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/03/12/working-on-the-rails-road/#comment-200</guid>
		<description>What would you use in place of sessions?  Not ruby-specific but in general?</description>
		<content:encoded><![CDATA[<p>What would you use in place of sessions?  Not ruby-specific but in general?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Klein</title>
		<link>http://comments.deasil.com/2007/03/12/working-on-the-rails-road/#comment-198</link>
		<dc:creator>Scott Klein</dc:creator>
		<pubDate>Mon, 12 Mar 2007 15:14:18 +0000</pubDate>
		<guid isPermaLink="false">http://comments.deasil.com/2007/03/12/working-on-the-rails-road/#comment-198</guid>
		<description>You crack me up, man.

&lt;blockquote&gt;The whole time Iâ€™m reading this, Iâ€™m shaking and sweating and wondering if Iâ€™m going to have to put the book down because I am allergic to sessions in web applications.&lt;/blockquote&gt;

I like this blog generally, but I think you really upshift when you're reviewing tech books.</description>
		<content:encoded><![CDATA[<p>You crack me up, man.</p>
<blockquote><p>The whole time Iâ€™m reading this, Iâ€™m shaking and sweating and wondering if Iâ€™m going to have to put the book down because I am allergic to sessions in web applications.</p></blockquote>
<p>I like this blog generally, but I think you really upshift when you&#8217;re reviewing tech books.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
