On Wed, Mar 9, 2011 at 11:29 AM, Kenneth Gonsalves <law...@thenilgiris.com> wrote: > On Wed, 2011-03-09 at 11:26 +0000, Tom Evans wrote: >> These are to be expected in this sort of scenario. If you want to >> support this sort of architecture, use a different hosting solution >> for development, eg mod_wsgi, mod_fastcgi etc. > > you could even proxy nginx to devserver and get the best of both > worlds ;-)
Note that this doesn't solve all the issues - the dev server can still only handle one request at a time. It may solve the OPs issue, since logically the video would be streamed from nginx, not from django, but it would not solve a view trying to make a web service call to the server the view is being served from. Also note that nginx is not doing anything particularly clever here, apache and other webservers are more than capable of acting as a reverse proxy. If you already use apache, no need to learn nginx also. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
