From: jose <jo...@cy...> - 2003-09-30 04:22:00
|
Hi all, I've got a quick question. If I establish a dbpool connection in my sitepage with say: Class sitePage(Page): def __init__(self): Page.__init__(self) self.db = DBPool(MySQLdb, 5, user=user....) Instead of doing it in the context initialization, is there any real problem to leaving the threads running? I've noticed that most people initialize dbpool with the context and have a application shutdown method to close it down. But since servlets stay in memory is this really necessary? Is there any harm in leaving them running (which is what I am assuming will happen the way I've outlined doing it)? Thanks for the info in advance Jose |
From: Aaron H. <aaron@MetroNY.com> - 2003-09-30 15:30:20
|
Each instance each page will now have a pool of 5 threads. So if you have three pages all built on sitePage, and you have 10 threads ruunning you will have (3*10*5) 150 possible connections, but you will only be able to use (3*5) 15 of them, since Webware creats one thread per request. Move the self.db line to the module level in sitePage db = DBPool..... Class sitePage(Page): def writeContent(self): conn = db.getConnection..... jose wrote: >Hi all, I've got a quick question. If I establish a dbpool connection >in my sitepage with say: > >Class sitePage(Page): > def __init__(self): > Page.__init__(self) > self.db = DBPool(MySQLdb, 5, user=user....) > >Instead of doing it in the context initialization, is there any real >problem to leaving the threads running? I've noticed that most people >initialize dbpool with the context and have a application shutdown >method to close it down. But since servlets stay in memory is this >really necessary? Is there any harm in leaving them running (which is >what I am assuming will happen the way I've outlined doing it)? > >Thanks for the info in advance > >Jose > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >Webware-discuss mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/webware-discuss > > -- -Aaron http://www.MetroNY.com/ "I don't know what's wrong with my television set. I was getting C-Span and the Home Shopping Network on the same station. I actually bought a congressman." - Bruce Baum |
From: jose <jo...@cy...> - 2003-10-01 04:22:55
|
Thanks arron now it makes sense. I actually tried what you said and sure enough with each page that I loaded (based on my sitepage) I ended up opening up more and more connections, not what I wanted. But by moving the DBPool out to the module level it works just like it is supposed to (I actually give it its own module - just made more sense to me) Thanks again for setting me straight on this Jose -----Original Message----- From: web...@li... [mailto:web...@li...] On Behalf Of Aaron Held Sent: Tuesday, September 30, 2003 8:30 AM To: jose Cc: 'Webware discuss' Subject: Re: [Webware-discuss] DBPool connections question Each instance each page will now have a pool of 5 threads. So if you have three pages all built on sitePage, and you have 10 threads ruunning you will have (3*10*5) 150 possible connections, but you will only be able to use (3*5) 15 of them, since Webware creats one thread per request. Move the self.db line to the module level in sitePage db = DBPool..... Class sitePage(Page): def writeContent(self): conn = db.getConnection..... jose wrote: >Hi all, I've got a quick question. If I establish a dbpool connection >in my sitepage with say: > >Class sitePage(Page): > def __init__(self): > Page.__init__(self) > self.db = DBPool(MySQLdb, 5, user=user....) > >Instead of doing it in the context initialization, is there any real >problem to leaving the threads running? I've noticed that most people >initialize dbpool with the context and have a application shutdown >method to close it down. But since servlets stay in memory is this >really necessary? Is there any harm in leaving them running (which is >what I am assuming will happen the way I've outlined doing it)? > >Thanks for the info in advance > >Jose > > > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf _______________________________________________ >Webware-discuss mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/webware-discuss > > -- -Aaron http://www.MetroNY.com/ "I don't know what's wrong with my television set. I was getting C-Span and the Home Shopping Network on the same station. I actually bought a congressman." - Bruce Baum ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list Web...@li... https://lists.sourceforge.net/lists/listinfo/webware-discuss |
From: Victor Ng <vn...@ma...> - 2003-10-01 05:24:23
|
Is UserKit being actively maintained or should I consider just rolling my own security/login system for WebWare? What are the rest of you Webware folks using for security? Are there any other Python/Webware developers around Toronto or Kitchener/Waterloo/Guelph? vic |
From: Ian B. <ia...@co...> - 2003-10-01 06:44:44
|
On Wednesday, October 1, 2003, at 12:24 AM, Victor Ng wrote: > Is UserKit being actively maintained or should I consider just rolling > my own security/login system for WebWare? > > What are the rest of you Webware folks using for security? I would recommend rolling your own, it's what I generally do. There's some stuff in the Sandbox (webware-sandbox.sf.net) if you want to think about something more reusable. Ian |