Djangophiles, is there any kind of analysis of the above combination with regard to efficiency. It seems that mod_fastcgi must talk to the flup server through a single socket (or rather each front end apache process must do so) and the flup server spawns flup/fastcgi children(I'm using a forking flup) to respond to the requests. I think there are no bottlenecks here, but I'm not sure who's responsible for scaling up and down as requests come in. Can anybody enlighten me? -- Robin Becker
--~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
