<?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: Discovering WSGI and XSLT as middleware</title>
	<atom:link href="http://decafbad.com/blog/2005/07/18/discovering-wsgi-and-xslt-as-middleware/feed" rel="self" type="application/rss+xml" />
	<link>http://decafbad.com/blog/2005/07/18/discovering-wsgi-and-xslt-as-middleware</link>
	<description>It's all spinning wheels and self-doubt until the first pot of coffee.</description>
	<lastBuildDate>Fri, 19 Mar 2010 00:06:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
	<item>
		<title>By: Bill Seitz</title>
		<link>http://decafbad.com/blog/2005/07/18/discovering-wsgi-and-xslt-as-middleware/comment-page-1#comment-9719</link>
		<dc:creator>Bill Seitz</dc:creator>
		<pubDate>Tue, 11 Apr 2006 12:17:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.decafbad.com/blog/?p=670#comment-9719</guid>
		<description>&lt;p&gt;Are you running WSGI behind Apache? If so, using what Apache plugin protocol? SCGI?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Are you running WSGI behind Apache? If so, using what Apache plugin protocol? SCGI?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Bicking</title>
		<link>http://decafbad.com/blog/2005/07/18/discovering-wsgi-and-xslt-as-middleware/comment-page-1#comment-1776</link>
		<dc:creator>Ian Bicking</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.decafbad.com/blog/?p=670#comment-1776</guid>
		<description>&lt;p&gt;It&#039;s cool to see this -- I had actually just mentioned an XSLT
middleware a day ago in an email on Web-SIG about WSGI and possible
middleware, and then there it is.  Incidentally, looking at your code,
if you want to get rid of the filesystem &quot;hack&quot; you can just create a
whole new request and capture the output.  An example of that is
paste.recursive (you&#039;d probably want to just borrow the technique, maybe not the specific module):
http://svn.pythonpaste.org/Paste/trunk/paste/recursive.py&lt;/p&gt;

&lt;p&gt;And if you want a place to put
this code, there&#039;d certainly be a place in Paste for it as well.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It&#8217;s cool to see this &#8212; I had actually just mentioned an XSLT<br />
middleware a day ago in an email on Web-SIG about WSGI and possible<br />
middleware, and then there it is.  Incidentally, looking at your code,<br />
if you want to get rid of the filesystem &#8220;hack&#8221; you can just create a<br />
whole new request and capture the output.  An example of that is<br />
paste.recursive (you&#8217;d probably want to just borrow the technique, maybe not the specific module):<br />
<a href="http://svn.pythonpaste.org/Paste/trunk/paste/recursive.py" rel="nofollow">http://svn.pythonpaste.org/Paste/trunk/paste/recursive.py</a></p>
<p>And if you want a place to put<br />
this code, there&#8217;d certainly be a place in Paste for it as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
