[web2py] Re: Per-user persistent database connections

2010-09-28 Thread Josh J
Massimo, I think there's an inherent scalability issue in any application that uses per-user database connections. My application is an internal application that will serve only a handful of users, so I’m not too concerned with how it will scale. We are more concerned with pushing access control

Re: [web2py] Re: Per-user persistent database connections

2010-09-27 Thread Mariano Reingart
If using PostgreSQL, take a look at pgpool or pgbouncer, they will do some of the things you're expecting, without modifing a single line of web2py (keep pool_size=1). Regards Mariano Reingart http://www.sistemasagiles.com.ar http://reingart.blogspot.com On Mon, Sep 27, 2010 at 9:48 PM, mdipie

[web2py] Re: Per-user persistent database connections

2010-09-27 Thread mdipierro
I would not know how to do this. If you have a lot of users (say 1000) how do you know when to close a connection? Do you keep all of them open? On Sep 27, 3:25 pm, Josh J wrote: > Most applications connect to the database with one set of credentials, > regardless of the user accessing the pages.