On Wed, Oct 14, 2009 at 9:16 AM, Stefan de Konink <[email protected]> wrote:
> On Wed, 14 Oct 2009, Atif Ghaffar wrote: > > > Now instead of providing access to the mysql database we create a > dbslayer > > instance, limit it to 2 connections and provide this to the developer. > The > > app can now be deployed to 20 servers but we are sure that it will > consume > > max 2 connections of the db server and not more. > > ...again; what is the performance cost of multiple connections. > > Do not pre-optimize stuff that doesn't have to be. > Stefan, There is no _pre_ about what we are doing, we are in post-post-post-almost-dead-beaten-horse state :-) Its about allowing access to a database without worrying about some script taking it down for everyone else. You dont have to change the handler to match my needs though, I am fine with nyt dbslayer and perhaps thinking of writting one in-house so it does more fine-grained control if we need to. Your implementation is great at what it does and should perhaps let it like that. thanks. > > Stefan > > -- best regards Atif Ghaffar
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
