On Jan 29, 2008 10:04 PM, Mark Green <[EMAIL PROTECTED]> wrote: > Just curious, what's the state of connection pooling in django?
My personal opinion is that the application level (e.g., Django) is the wrong place for connection pooling and for the equivalent "front end" solution of load balancing your web servers: the less the application layer has to know about what's in front of and behind it, the more flexible it will be (since you can make changes without having to alter your application-layer code). So, for example, connection pooling for Postgres would best be handled by a dedicated pooling connection manager like pgpool; Django can connect to pgpool as if it's simply a Postgres database, which means you don't have to go specifying pooling parameters at the application level. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
