On 3/7/07, Ian Bicking <[EMAIL PROTECTED]> wrote: > In theory you can set up Zope 3 using something like: > > [app:main] > paste.app_factory = some_function_yet_to_be_written > > I thought zope.paste did this, but it's a little wonky now that I look > at it.
Well, you're probably missing something then, from [1]: """ [app:Paste.Main] paste.app_factory = zope.paste.application:zope_publisher_app_factory """ > It seems to basically read INSTANCE_HOME and create a single > Zope WSGI app, and then kind of minimally plug into it. It's actually a mixed bag. It looks for INSTANCE_HOME to know where to find paste.ini. The second thing it does is to help register an IServerType factory so that you can actually run the WSGI app created with the included-in-zope3 Twisted WSGI server. I don't recall if it runs with ZServer too, probably does. So, to some extent, it wasn't meant to make Zope 3 a WSGI that can be run anywhere, it was just meant to make it possible to use paste to compose 'a' WSGI app that uses zope.app.publication that could be run by Twisted or ZServer. Now, I'm not saying that it can't evolve into something that makes Zope 3 run as a WSGI anywhere. It just wasn't the original intent. [1] http://awkly.org/2006/01/25/zopepaste-wsgi-applications-in-zope-3-using-pastedeploy/ -- Sidnei da Silva Enfold Systems http://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 _______________________________________________ Web-SIG mailing list [email protected] Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
