Me being ignorant. What is the difference between using nginx push
module and simply proxying nginx to a gunicorn running with eventlet
worker so coroutines used instead of threads. Or is the push module a
special variant of proxy module that is friendly to long polling
backends and doesn't
On 12 June 2011 18:49, Damjan gdam...@gmail.com wrote:
I never looked at nginx, but is this what you propose (assuming only one
external port can be used)?
- nginx listening on external port
- use the nginx ush module for the 'long poll' urls
- hide apache behind nginx
- use mod_wsgi behind
I never looked at nginx, but is this what you propose (assuming only one
external port can be used)?
- nginx listening on external port
- use the nginx ush module for the 'long poll' urls
- hide apache behind nginx
- use mod_wsgi behind apache
- the web clients will use a tiny piece of
On 06/09/2011 03:50 PM, Graham Dumpleton wrote:
In short, Apache is not necessarily the best platform for long polling
(comet) style applications. Possible for smaller numbers of concurrent
requests, bit not when number of concurrent requests can balloon out.
The important thing to note is
Thus I thought about long polling.
As I never used this technology I am not sure about the load such an
implementation would put on the server host and whether I could use
mod_wsgi for such an appliation
My setup / intended application.
- the web server has only port 443 (https) as
In short, Apache is not necessarily the best platform for long polling
(comet) style applications. Possible for smaller numbers of concurrent
requests, bit not when number of concurrent requests can balloon out.
The important thing to note is that although you may have certain URLs
which require
