<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: zope.paste &#8211; wsgi applications in zope 3 using paste.deploy</title>
	<atom:link href="http://blog.sidneidasilva.com/2006/01/25/zopepaste-wsgi-applications-in-zope-3-using-pastedeploy/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sidneidasilva.com/2006/01/25/zopepaste-wsgi-applications-in-zope-3-using-pastedeploy/</link>
	<description></description>
	<lastBuildDate>Mon, 14 Feb 2011 05:53:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Philipp von Weitershausen</title>
		<link>http://blog.sidneidasilva.com/2006/01/25/zopepaste-wsgi-applications-in-zope-3-using-pastedeploy/#comment-156</link>
		<dc:creator><![CDATA[Philipp von Weitershausen]]></dc:creator>
		<pubDate>Mon, 06 Feb 2006 08:16:49 +0000</pubDate>
		<guid isPermaLink="false">http://omsg.wordpress.com/2006/01/25/zopepaste-wsgi-applications-in-zope-3-using-pastedeploy/#comment-156</guid>
		<description><![CDATA[&lt;strong&gt; WSGI and Paste rock -- if they can cope with complex apps &lt;/strong&gt; 
WSGI and Paste rock. It&#039;s definitely time that Python catches up with Java wrt making the app server independent of the web server. What I like about WSGI and Paste is how light-weight they are (Paste Deploy is so simple, its documentation tricked me into believing it was something totally complicated).

The only thing that we need to make sure is that WSGI and Paste will be able to handle complex requirements that large frameworks such as Zope have: logging, other protocols, etc.

Lastly a minor nitpick: The zcml:condition attribute doesn&#039;t need to be on a &lt;configure /&gt; element. It can be on any element and it&#039;s evaluated before anything else. Therefore, the two utility directives above can simply read::

    &lt;utility
        zcml:condition=&quot;have zserver&quot;
        name=&quot;Paste.Main&quot;
        component=&quot;._server.http&quot;
        provides=&quot;zope.app.server.servertype.IServerType&quot;
        /&gt;
    &lt;utility
        zcml:condition=&quot;have twisted&quot;
        name=&quot;Paste.Main&quot;
        component=&quot;._twisted.http&quot;
        provides=&quot;zope.app.twisted.interfaces.IServerType&quot;
        /&gt;

Perhaps I should just check it into the SVN :).]]></description>
		<content:encoded><![CDATA[<p><strong> WSGI and Paste rock &#8212; if they can cope with complex apps </strong><br />
WSGI and Paste rock. It&#8217;s definitely time that Python catches up with Java wrt making the app server independent of the web server. What I like about WSGI and Paste is how light-weight they are (Paste Deploy is so simple, its documentation tricked me into believing it was something totally complicated).</p>
<p>The only thing that we need to make sure is that WSGI and Paste will be able to handle complex requirements that large frameworks such as Zope have: logging, other protocols, etc.</p>
<p>Lastly a minor nitpick: The zcml:condition attribute doesn&#8217;t need to be on a &lt;configure /&gt; element. It can be on any element and it&#8217;s evaluated before anything else. Therefore, the two utility directives above can simply read::</p>
<p>    &lt;utility<br />
        zcml:condition=&quot;have zserver&quot;<br />
        name=&quot;Paste.Main&quot;<br />
        component=&quot;._server.http&quot;<br />
        provides=&quot;zope.app.server.servertype.IServerType&quot;<br />
        /&gt;<br />
    &lt;utility<br />
        zcml:condition=&quot;have twisted&quot;<br />
        name=&quot;Paste.Main&quot;<br />
        component=&quot;._twisted.http&quot;<br />
        provides=&quot;zope.app.twisted.interfaces.IServerType&quot;<br />
        /&gt;</p>
<p>Perhaps I should just check it into the SVN :).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Everitt</title>
		<link>http://blog.sidneidasilva.com/2006/01/25/zopepaste-wsgi-applications-in-zope-3-using-pastedeploy/#comment-155</link>
		<dc:creator><![CDATA[Paul Everitt]]></dc:creator>
		<pubDate>Thu, 26 Jan 2006 11:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://omsg.wordpress.com/2006/01/25/zopepaste-wsgi-applications-in-zope-3-using-pastedeploy/#comment-155</guid>
		<description><![CDATA[&lt;strong&gt; Very good writeup &lt;/strong&gt; 
Thanks for taking the time to do this writeup, Sidnei.  There aren&#039;t that many docs out there on how do do WSGI things.  This page, by saying in detail the step-by-step things to do, helps folks like me get started.  Of course, the XSLT part is a honeypot to which I&#039;m lured in. [wink]]]></description>
		<content:encoded><![CDATA[<p><strong> Very good writeup </strong><br />
Thanks for taking the time to do this writeup, Sidnei.  There aren&#8217;t that many docs out there on how do do WSGI things.  This page, by saying in detail the step-by-step things to do, helps folks like me get started.  Of course, the XSLT part is a honeypot to which I&#8217;m lured in. [wink]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

