Get the status code from the response once so we can use it to check the need
for the connection header later without parsing the string each time we need it.
Raise a StopIteration rather than returning so that the keep-alive
loop is terminated. If gunicorn has closed the socket there is no
sense in trying to read another request and it may cause spurious
EBADF errors to try.
Using gunicorn with paster command line causes the application to
load before gunicorn. In this case, there is no choice but to preload
the application. Document this fact.
Fixes#528.
This commit closes the loop on fd6c712.
Aforementioned commit fixed observable problems in my testing with
gevent 1.0 release candidates but the explanation given at the time
was curiously bogus. It came from a misreading of pools and servers
as used in the ggevent worker.
With this change, both versions of gevent should support graceful
and non-graceful shutdown.
This change should improve interaction with reloaders and ensure that
ports are not stuck open if the arbiter gets a hard kill signal or
otherwise exits during any graceful or non-graceful shutdown.
It is now possible to specify a file with "config" as an application
configuration key in a paste deploy configuration file. This allows
paster applications to use the full range of gunicorn settings even
when using paste/pserve rather than gunicorn_paster.
Fixes#540.
Not: With this release, the versionning of Gunicorn is changing.
Gunicorn is stable since a long time and there is no point to release a
"1.0" now. It should have been done since a long time. Also from the
beginning we have only 2 kind of releases:
- major release: releases with major changes or huge features added
- interval releases: fixes and minor features added
So from now we will apply the following versionning
R<major>.<interval>
for example R17.5 means we are relasing an interval release on the 17th
major version.
