> 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 javascript to do the longpoll > - the wsgi modules can do a POST request to the push-module
that's exactly what should do > Are there any threads / urls explaining the sweet spots of nginx / > apache / wsgi modules? There're a lot of blog posts about this. AFAIR Graham posted one recently on this group. > contents I had to provide behind one external https port > - static contents without auythenification (nginx?) yes. nginx is very efficient when handling static content, and you'll free resources in apache to handle the dynamic parts. You could even have nginx serve non-public static files with something like http://wiki.nginx.org/HttpSecureLinkModule > - dynamic contents wsgi > - static contents with user based authentification (nginx? apache?) > - static contents with fine grain session based access control > (wsgi grants permission and sends xsendfile headers? to apache > or nginx?) http://wiki.nginx.org/X-accel > - contents requiring htps client certificates (??) Thats something I don't know about, you'll have to research yourself. -- 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.
