<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>develoPy: continuations ..</title>
    <link>http://blog.karlsch.com/articles/2006/11/24/continuations</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>special K is speaking</description>
    <item>
      <title>continuations ..</title>
      <description>&lt;p&gt;I&amp;#8217;m a great fan of &lt;a href="http://en.wikipedia.org/wiki/Continuation"&gt;continuations&lt;/a&gt; and frameworks like &lt;a href="http://www.seaside.st/"&gt;Seaside&lt;/a&gt;. Sadly they will be dropped from Ruby in the future. (Or Not?) &lt;a href="http://www.interact-sw.co.uk/iangblog/2006/05/21/webcontinuations"&gt;Ian Griffiths has some nice arguments against using continuation for webframeworks&lt;/a&gt;. I share some of his doubts, but I would not be suprised if some smart guy can solve most of the problems.  For example the mentioned &amp;#8220;back&amp;#8221; problem is a &amp;#8220;where do you store the continuation&amp;#8221; problem I think. You have at least some options not to store everything on the server like hidden fields, cookies, URLs or a combination of server and client side storage. A nifty idea to make this more handable  may be &lt;a href="http://www.myvideo.de/watch/317869"&gt;composable continuation&lt;/a&gt;.&lt;/p&gt;
</description>
      <pubDate>Fri, 24 Nov 2006 21:04:00 +0100</pubDate>
      <guid isPermaLink="false">urn:uuid:49d238f8-2aa4-4dc4-a7cf-82502fe055c8</guid>
      <author>martin.karlsch</author>
      <link>http://blog.karlsch.com/articles/2006/11/24/continuations</link>
      <category>Software and so on</category>
      <trackback:ping>http://blog.karlsch.com/articles/trackback/13</trackback:ping>
    </item>
  </channel>
</rss>
