<?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: CherryPy v. Pylons</title>
	<atom:link href="http://kenkinder.com/2009/10/18/cherrypy-v-pylons/feed/" rel="self" type="application/rss+xml" />
	<link>http://kenkinder.com/2009/10/18/cherrypy-v-pylons/</link>
	<description>Ken Kinder&#039;s personal website</description>
	<lastBuildDate>Wed, 02 Jun 2010 07:46:06 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ken Kinder</title>
		<link>http://kenkinder.com/2009/10/18/cherrypy-v-pylons/comment-page-1/#comment-597</link>
		<dc:creator>Ken Kinder</dc:creator>
		<pubDate>Wed, 04 Nov 2009 18:54:41 +0000</pubDate>
		<guid isPermaLink="false">http://kenkinder.com/?p=194#comment-597</guid>
		<description>Robert, another issue I found:

http://tools.cherrypy.org/wiki/XmlRpcIntrospection

If you run this example, and use the xmlrpclib test it shows at the bottom, you actually get 404 errors from CherryPy. I created a ticket:

http://cherrypy.org/ticket/967
</description>
		<content:encoded><![CDATA[<p>Robert, another issue I found:</p>
<p><a href="http://tools.cherrypy.org/wiki/XmlRpcIntrospection" rel="nofollow">http://tools.cherrypy.org/wiki/XmlRpcIntrospection</a></p>
<p>If you run this example, and use the xmlrpclib test it shows at the bottom, you actually get 404 errors from CherryPy. I created a ticket:</p>
<p><a href="http://cherrypy.org/ticket/967" rel="nofollow">http://cherrypy.org/ticket/967</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Kinder</title>
		<link>http://kenkinder.com/2009/10/18/cherrypy-v-pylons/comment-page-1/#comment-595</link>
		<dc:creator>Ken Kinder</dc:creator>
		<pubDate>Wed, 28 Oct 2009 05:41:44 +0000</pubDate>
		<guid isPermaLink="false">http://kenkinder.com/?p=194#comment-595</guid>
		<description>Yes, actually, that is a vast improvement. Especially the headings under the Request Cycle. Thanks!</description>
		<content:encoded><![CDATA[<p>Yes, actually, that is a vast improvement. Especially the headings under the Request Cycle. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Brewer</title>
		<link>http://kenkinder.com/2009/10/18/cherrypy-v-pylons/comment-page-1/#comment-592</link>
		<dc:creator>Robert Brewer</dc:creator>
		<pubDate>Wed, 21 Oct 2009 19:05:02 +0000</pubDate>
		<guid isPermaLink="false">http://kenkinder.com/?p=194#comment-592</guid>
		<description>Is http://www.cherrypy.org/wiki/TableOfContents better now? There&#039;s obviously a bunch of re-org we could do with the individual pages, but at least there are full-phrase headings now.</description>
		<content:encoded><![CDATA[<p>Is <a href="http://www.cherrypy.org/wiki/TableOfContents" rel="nofollow">http://www.cherrypy.org/wiki/TableOfContents</a> better now? There&#8217;s obviously a bunch of re-org we could do with the individual pages, but at least there are full-phrase headings now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Kinder</title>
		<link>http://kenkinder.com/2009/10/18/cherrypy-v-pylons/comment-page-1/#comment-591</link>
		<dc:creator>Ken Kinder</dc:creator>
		<pubDate>Mon, 19 Oct 2009 22:05:05 +0000</pubDate>
		<guid isPermaLink="false">http://kenkinder.com/?p=194#comment-591</guid>
		<description>Hey Robert, thanks for reading and replying to my blog post. What strikes me is that the Table of Contents is built with an existing knowledge of how CherryPy works:

http://www.cherrypy.org/wiki/TableOfContents

For example, it makes sense that url mapping is part of the request cycle, but I have to know ahead of time that CherryPy calls the objects that map URLs to controllers, &quot;dispatchers.&quot; And shouldn&#039;t ReturnVsYield be in the &quot;request cycle&quot; too?

I&#039;d go for more of a generally worded, more structured table of contents with headings like Basic Development that would cover Controllers, cookies, and the like. Then another section for extending CherryPy. Then maybe another on deploying, under which BehindApache, WSGI, etc would be placed.

Also, I would use full phrases as headings, not just wiki stubs. Take a look at the Django or Pylons documentation and it&#039;s broken up by version and purpose. Not that CherryPy&#039;w wiki approach doesn&#039;t have advantages, but it&#039;s harder to navigate.</description>
		<content:encoded><![CDATA[<p>Hey Robert, thanks for reading and replying to my blog post. What strikes me is that the Table of Contents is built with an existing knowledge of how CherryPy works:</p>
<p><a href="http://www.cherrypy.org/wiki/TableOfContents" rel="nofollow">http://www.cherrypy.org/wiki/TableOfContents</a></p>
<p>For example, it makes sense that url mapping is part of the request cycle, but I have to know ahead of time that CherryPy calls the objects that map URLs to controllers, &#8220;dispatchers.&#8221; And shouldn&#8217;t ReturnVsYield be in the &#8220;request cycle&#8221; too?</p>
<p>I&#8217;d go for more of a generally worded, more structured table of contents with headings like Basic Development that would cover Controllers, cookies, and the like. Then another section for extending CherryPy. Then maybe another on deploying, under which BehindApache, WSGI, etc would be placed.</p>
<p>Also, I would use full phrases as headings, not just wiki stubs. Take a look at the Django or Pylons documentation and it&#8217;s broken up by version and purpose. Not that CherryPy&#8217;w wiki approach doesn&#8217;t have advantages, but it&#8217;s harder to navigate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Kinder</title>
		<link>http://kenkinder.com/2009/10/18/cherrypy-v-pylons/comment-page-1/#comment-590</link>
		<dc:creator>Ken Kinder</dc:creator>
		<pubDate>Mon, 19 Oct 2009 21:54:06 +0000</pubDate>
		<guid isPermaLink="false">http://kenkinder.com/?p=194#comment-590</guid>
		<description>Very nice. I&#039;ll give it a try. Thanks!</description>
		<content:encoded><![CDATA[<p>Very nice. I&#8217;ll give it a try. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sylvain Hellegouarch</title>
		<link>http://kenkinder.com/2009/10/18/cherrypy-v-pylons/comment-page-1/#comment-589</link>
		<dc:creator>Sylvain Hellegouarch</dc:creator>
		<pubDate>Mon, 19 Oct 2009 19:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://kenkinder.com/?p=194#comment-589</guid>
		<description>Here is an example:
http://tools.cherrypy.org/wiki/PasteEvalException</description>
		<content:encoded><![CDATA[<p>Here is an example:<br />
<a href="http://tools.cherrypy.org/wiki/PasteEvalException" rel="nofollow">http://tools.cherrypy.org/wiki/PasteEvalException</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sylvain Hellegouarch</title>
		<link>http://kenkinder.com/2009/10/18/cherrypy-v-pylons/comment-page-1/#comment-588</link>
		<dc:creator>Sylvain Hellegouarch</dc:creator>
		<pubDate>Mon, 19 Oct 2009 18:52:15 +0000</pubDate>
		<guid isPermaLink="false">http://kenkinder.com/?p=194#comment-588</guid>
		<description>If I&#039;m not mistaken you can have the same error handling feature from CherryPy by using the WSGI paste middleware for it</description>
		<content:encoded><![CDATA[<p>If I&#8217;m not mistaken you can have the same error handling feature from CherryPy by using the WSGI paste middleware for it</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Brewer</title>
		<link>http://kenkinder.com/2009/10/18/cherrypy-v-pylons/comment-page-1/#comment-587</link>
		<dc:creator>Robert Brewer</dc:creator>
		<pubDate>Mon, 19 Oct 2009 18:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://kenkinder.com/?p=194#comment-587</guid>
		<description>Thanks, Ken. Always good to get feedback so we can improve.

Question for ya: you mentioned that the CherryPy RoutesDispatcher documentation is sort of in the wrong place. What would be the right place in your estimation?</description>
		<content:encoded><![CDATA[<p>Thanks, Ken. Always good to get feedback so we can improve.</p>
<p>Question for ya: you mentioned that the CherryPy RoutesDispatcher documentation is sort of in the wrong place. What would be the right place in your estimation?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
