Martin Aspeli <optilude+li...@gmail.com> writes:
> On 7 June 2012 07:20, Michael Howitz <m...@gocept.com> wrote:
>> Am 06.06.2012 um 19:58 schrieb Hanno Schlichting:
>>> As I said above, my main concern is keeping publisher events and
>>> exception views intact. Some of these events need to happen in code
>>> that's currently inside repoze.* middleware. Like "before transaction
>>> commit", "publication failure" or "publication success".
>> +1 to re-add these events. In our WSGI projects it hurts that they are gone
> There was a thread on this a while ago, and I did some in-depth
> research on the current state of WSGI publishers.
> See http://old.nabble.com/Zope-2-WSGI-investigation-to33063118.html#a33063118.
> Summary: use infrae.wsgi for now.
FYI, while working on the Plone WebPI installer, I tried both
infrae.wsgi and the Zope2 WSGI publisher. I couldn't get infrae.wsgi to
work for a few different reasons:
Fix problem with hanging requests and orphaned python processes.
Opening ZMI or the `@@plone-addsite` view worked fine, but a vanilla
Plone site would cause the browser to start getting a response but it
never finished and the Python FCGI process would be orphaned from IIS.
Switching back to the Zope2 WSGI server I found that Diazo themeing
seems to work just fine anyways so I don't think we need it.
So the Zope2 WSGI publisher works for plone.app.themeing when I was told
that it wouldn't work without events. *Shrug*
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -