---------- Forwarded message ---------- From: Benoit Chesneau <bchesn...@gmail.com> Date: Thu, Jan 21, 2010 at 4:12 PM Subject: Re: [Web-SIG] gunicorn 0.1 - new WSGI HTTP Server To: Tres Seaver <tsea...@palladion.com>
On Wed, Jan 6, 2010 at 2:12 AM, Tres Seaver <tsea...@palladion.com> wrote: > Interesting: how are you detecting slow clients in production, given > that the WSGI server itself is only supposed to be used for fast ones? > I'm assuming that there must be some kind of heuristic-applying proxy > you run in front of unicorn/gunicorn. Or do you just not bother, and > let slow clients see failed responses? > > > Tres. Sorry for the delay to answer. Gunicorn intended to be used behind a caching upstream proxy like nginx. So it will be the responsability of nginx or such to manage slow connections which it does perfectly. In this sense it works like its alter ego unicorn on ruby. hope it helps. - benoît _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
