<?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: The State of State on the Web</title>
	<atom:link href="http://www.untyped.com/untyping/2009/03/20/the-state-of-state-on-the-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.untyped.com/untyping/2009/03/20/the-state-of-state-on-the-web/</link>
	<description>Weblog of Untyped, software developers for internet, desktop and mobile.</description>
	<lastBuildDate>Wed, 10 Jun 2009 09:20:03 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Untyping &#187; More State on the Web</title>
		<link>http://www.untyped.com/untyping/2009/03/20/the-state-of-state-on-the-web/comment-page-1/#comment-367</link>
		<dc:creator>Untyping &#187; More State on the Web</dc:creator>
		<pubDate>Thu, 26 Mar 2009 13:35:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.untyped.com/untyping/?p=205#comment-367</guid>
		<description>[...] a followup to The State of State on the Web I want to mention stateless servlets, a relatively new feature of the PLT web server that make [...]</description>
		<content:encoded><![CDATA[<p>[...] a followup to The State of State on the Web I want to mention stateless servlets, a relatively new feature of the PLT web server that make [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Noel</title>
		<link>http://www.untyped.com/untyping/2009/03/20/the-state-of-state-on-the-web/comment-page-1/#comment-356</link>
		<dc:creator>Noel</dc:creator>
		<pubDate>Wed, 25 Mar 2009 17:29:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.untyped.com/untyping/?p=205#comment-356</guid>
		<description>Interesting analogy. Typically another mechanism would be used. A database is the traditional choice. With continuations you might use your language&#039;s inter-thread/process communication mechanisms (in PLT Scheme, this would be channels). Using cookies is certainly viable but not typical.</description>
		<content:encoded><![CDATA[<p>Interesting analogy. Typically another mechanism would be used. A database is the traditional choice. With continuations you might use your language&#8217;s inter-thread/process communication mechanisms (in PLT Scheme, this would be channels). Using cookies is certainly viable but not typical.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: apoirier</title>
		<link>http://www.untyped.com/untyping/2009/03/20/the-state-of-state-on-the-web/comment-page-1/#comment-337</link>
		<dc:creator>apoirier</dc:creator>
		<pubDate>Mon, 23 Mar 2009 17:33:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.untyped.com/untyping/?p=205#comment-337</guid>
		<description>As the lead developer of Nagare, I need to say Nagare is the wrong example to start your post with, because it has the exact same techniques for state management than you use with PLT web: using an history of continuations, saved on the server, is the natural and easier way to code with Nagare. But, then, you can map significative &quot;RESTful&quot; URL on important resources if you want, using CLOS-like generic methodes.

An example on how to map such significatives URL to a Wiki starts at http://www.nagare.org/wiki/wiki7/1 (note how this RESTFul URL points to step #1 of the 7th example of the wiki tutorial).

Also, Nagare comes with several security managers, the form based one using cookies.

That why the complete sentences decribing Nagare are &quot;no *explicit* URL routing&quot; and &quot;No REST *by default*&quot;. But I know the actual lack of document about RESTFul URLs can create miscomprehension.

Else, of course, I totally agree with the rest of your post about the benefits of these different state management policies.

Regards</description>
		<content:encoded><![CDATA[<p>As the lead developer of Nagare, I need to say Nagare is the wrong example to start your post with, because it has the exact same techniques for state management than you use with PLT web: using an history of continuations, saved on the server, is the natural and easier way to code with Nagare. But, then, you can map significative &#8220;RESTful&#8221; URL on important resources if you want, using CLOS-like generic methodes.</p>
<p>An example on how to map such significatives URL to a Wiki starts at <a href="http://www.nagare.org/wiki/wiki7/1" rel="nofollow">http://www.nagare.org/wiki/wiki7/1</a> (note how this RESTFul URL points to step #1 of the 7th example of the wiki tutorial).</p>
<p>Also, Nagare comes with several security managers, the form based one using cookies.</p>
<p>That why the complete sentences decribing Nagare are &#8220;no *explicit* URL routing&#8221; and &#8220;No REST *by default*&#8221;. But I know the actual lack of document about RESTFul URLs can create miscomprehension.</p>
<p>Else, of course, I totally agree with the rest of your post about the benefits of these different state management policies.</p>
<p>Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dysfunctor</title>
		<link>http://www.untyped.com/untyping/2009/03/20/the-state-of-state-on-the-web/comment-page-1/#comment-318</link>
		<dc:creator>dysfunctor</dc:creator>
		<pubDate>Sat, 21 Mar 2009 20:56:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.untyped.com/untyping/?p=205#comment-318</guid>
		<description>Thanks Noel.  Most informative.

It strikes me that, when you use continuations, the multi-window problem starts to look like the multi-threading problem, with cookies being the data structures shared between threads.

Is this a reasonable analogy?</description>
		<content:encoded><![CDATA[<p>Thanks Noel.  Most informative.</p>
<p>It strikes me that, when you use continuations, the multi-window problem starts to look like the multi-threading problem, with cookies being the data structures shared between threads.</p>
<p>Is this a reasonable analogy?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
