<?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: Life without cookies (or URL rewriting)</title>
	<atom:link href="http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/</link>
	<description>XML and the Web.</description>
	<pubDate>Thu, 20 Nov 2008 21:54:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Chris</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-17201</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 22 Nov 2006 18:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-17201</guid>
		<description>I love cookies / I HATE cookies.

Privacy aside, users on my site like to login as more than one user at the same time (They pay me so I cant say no).  With session cookies this works fine in 2 seperate browsers, but if both are opened in the same browser instance (tabs or file&#124;new) the cookies are shared and everything goes downhill from there...</description>
		<content:encoded><![CDATA[<p>I love cookies / I HATE cookies.</p>
<p>Privacy aside, users on my site like to login as more than one user at the same time (They pay me so I cant say no).  With session cookies this works fine in 2 seperate browsers, but if both are opened in the same browser instance (tabs or file|new) the cookies are shared and everything goes downhill from there&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-13609</link>
		<dc:creator>david</dc:creator>
		<pubDate>Wed, 20 Sep 2006 11:41:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-13609</guid>
		<description>The trouble with URL rewriting for session management is that bookmarks stop working (because your session is stale the next time you visit).</description>
		<content:encoded><![CDATA[<p>The trouble with URL rewriting for session management is that bookmarks stop working (because your session is stale the next time you visit).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mudgal</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-13599</link>
		<dc:creator>Mudgal</dc:creator>
		<pubDate>Wed, 20 Sep 2006 08:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-13599</guid>
		<description>Well I personally find cookies a bit problematic but URL Rewriting is just wonderful things. Its kinda must for SEO and looks very neat.</description>
		<content:encoded><![CDATA[<p>Well I personally find cookies a bit problematic but URL Rewriting is just wonderful things. Its kinda must for SEO and looks very neat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliotte Rusty Harold</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-1856</link>
		<dc:creator>Elliotte Rusty Harold</dc:creator>
		<pubDate>Thu, 10 Nov 2005 22:24:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-1856</guid>
		<description>Check out the comment system on http://cafe.elharo.com
No cookies and no URL rewriting</description>
		<content:encoded><![CDATA[<p>Check out the comment system on <a href="http://cafe.elharo.com" rel="nofollow">http://cafe.elharo.com</a><br />
No cookies and no URL rewriting</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-1486</link>
		<dc:creator>david</dc:creator>
		<pubDate>Fri, 14 Oct 2005 10:56:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-1486</guid>
		<description>The main problem with AJAX is that many implementations break bookmarks and the back button, though I understand that there are workarounds available.</description>
		<content:encoded><![CDATA[<p>The main problem with AJAX is that many implementations break bookmarks and the back button, though I understand that there are workarounds available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sjoerd Visscher</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-1485</link>
		<dc:creator>Sjoerd Visscher</dc:creator>
		<pubDate>Fri, 14 Oct 2005 09:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-1485</guid>
		<description>The solution is simple: use a single page which leaves the session on the client and interacts with the server using AJAX or similar technology.</description>
		<content:encoded><![CDATA[<p>The solution is simple: use a single page which leaves the session on the client and interacts with the server using AJAX or similar technology.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Baker</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-1484</link>
		<dc:creator>Mark Baker</dc:creator>
		<pubDate>Fri, 14 Oct 2005 03:26:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-1484</guid>
		<description>"[...]violates the REST principle that n requests with the same URL should return the same object"

Hmm, I'm not exactly sure what you're referring to there, but REST has no problem with GET requests to the same URL returning different things at different times, or as a function of information in the message itself (which is what the HTTP Vary header explicitly accomodates).</description>
		<content:encoded><![CDATA[<p>&#8220;[...]violates the REST principle that n requests with the same URL should return the same object&#8221;</p>
<p>Hmm, I&#8217;m not exactly sure what you&#8217;re referring to there, but REST has no problem with GET requests to the same URL returning different things at different times, or as a function of information in the message itself (which is what the HTTP Vary header explicitly accomodates).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-1483</link>
		<dc:creator>david</dc:creator>
		<pubDate>Fri, 14 Oct 2005 02:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-1483</guid>
		<description>The authentication information is voluntarily supplied by the user.  Increasingly, cookies can be handled the same way -- I turn them off by default in Firefox, and then grant them (sparingly) on a case-by-case basis to individual sites -- but that's a little beyond the average browser user right now.</description>
		<content:encoded><![CDATA[<p>The authentication information is voluntarily supplied by the user.  Increasingly, cookies can be handled the same way &#8212; I turn them off by default in Firefox, and then grant them (sparingly) on a case-by-case basis to individual sites &#8212; but that&#8217;s a little beyond the average browser user right now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henning Koch</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-1482</link>
		<dc:creator>Henning Koch</dc:creator>
		<pubDate>Fri, 14 Oct 2005 01:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-1482</guid>
		<description>But why is it play to customize a page response when based on one part of the HTTP header (the user authentication) but not when based on another (the session ID in the cookie)?</description>
		<content:encoded><![CDATA[<p>But why is it play to customize a page response when based on one part of the HTTP header (the user authentication) but not when based on another (the session ID in the cookie)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.megginson.com/blogs/quoderat/2005/10/13/life-without-cookies-or-url-rewriting/#comment-1481</link>
		<dc:creator>david</dc:creator>
		<pubDate>Thu, 13 Oct 2005 22:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/?p=66#comment-1481</guid>
		<description>Cookies have serious privacy issues (and many users block them), while URL rewriting messes up bookmarks.</description>
		<content:encoded><![CDATA[<p>Cookies have serious privacy issues (and many users block them), while URL rewriting messes up bookmarks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
