> 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 incoming port > -- a max of about 100 web browsers might be connected at the same time
This means you will have 100 mod_wsgi threads blocked with client connections, possible but not optimal at all. > Are there any other suggestions how to setup such a server in a way, > that it doesn't waste too many resources? There're a lot of ways to make this. One is to use nginx and the optional push module[1]. With it, nginx keeps the long-poll connections active, and you just http POST to a special (private) url to notify all the clients. The good thing is that this can work with any backaend language. And it's generally preferential to use nginx in front of Apache anyway. Other option is to use some specially crafted backend (python gevent, erlang?) to handle the long-polls. There are also special servers that are supposed to generically handle long-poll connections (but they seem complicated). [1] http://pushmodule.slact.net/ -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
