An error occurred fetching the project authors.
- 05 Aug, 2015 2 commits
-
-
Gerhard Weis authored
-
Gerhard Weis authored
-
- 16 Jun, 2015 1 commit
-
-
Gerhard Weis authored
-
- 30 May, 2011 2 commits
-
-
Brian Sutherland authored
-
Brian Sutherland authored
Previously an addAfterCommitHook was used, but this is not run on transaction aborts. Now a Synchronizer is used which unconditionally closes the request after a transaction is finished. Not closing the request seems to have caused the database connections to be kept open and these nasty log messages: CRITICAL ZODB.DB DB.open() has 42 open connections with a pool_size of 7 42 being the wrong answer in this case.
-
- 26 Mar, 2011 2 commits
-
-
Malthe Borch authored
-
Malthe Borch authored
-
- 08 Aug, 2010 1 commit
-
-
Hanno Schlichting authored
-
- 21 Jun, 2010 1 commit
-
-
Christian Theune authored
-
- 01 Jun, 2010 2 commits
-
-
Tres Seaver authored
- Full test coverage for ZPublisher.WSGIPublisher. - Add 'add_user' script and finder help, borrowed from 'repoze.zope2'. - Add call to 'setDefaultSkin(request)' to fix view lookups. - Override the 'write' method in 'WSGIHTTPReponse' to avoid inappropriate stringification, allowing things like the Plone resource registry to work properly. - Defer closing the request until the transaction commits, if and only if we know that middleware is handling the transaction. - Make the WSGI publish function deal with three special cases: - App returns a file-like object as the response body (keep the app from stringifying it). - App raises an Unauthorized exception (just set the response status, to let middleware handle issuing a challenge). - App raises a Redirect exception (just call redirect on the response). - Adapt test code to the new signature of 'HTTPResponse._cookie_list', which now returns a list of two-tuples, rather than rendered strings. - Get quickstart page rendering under plain paste config. - Make WSGIResponse.__str__ raise and exception, preventing an 'attractive nuisance.' The real logic is in finalize and listHeaders now, and the publish* functions call those directly. - Move finalization logic out of HTTPResponse.listHeaders. - Refactor WSGIHTTPResponse to avoid the need to use str() and parse. o Instead, compute status and headers directly. - Chop out error and transaction handling from the 'publish*' functions: the point of doing WSGI is to move that stuff out of the application, and out into middleware. - One backward incompatibility: the special "shutdown" behavior is gone here. It should be replaced by something in view code. - Factor out computation of the list of response headers from stringifying them, allowing WSGIHTTPResponse do reuse them as tuples. - Chop out copy-and-paste fossils irrelevant to WSGI publication. - Replace contorted logic for case-normalizing response headers with idiomatic Python. - More PEP8 conformance.
-
Tres Seaver authored
- Start test coverage for WSGIPublisher.
-