On 2006-09-05 08:08:54 -0600, Darin McBride wrote:
On Monday 04 September 2006 22:28, Jack Faley ( The Tao of Jack ) wrote:
Thank you for your reply. If their was any way to mitigate the small exits
I would do it but I'm modifying an app that was never meant to be
extensible. So, you are
On Monday 04 September 2006 22:28, Jack Faley ( The Tao of Jack ) wrote:
Thank you for your reply. If their was any way to mitigate the small exits
I would do it but I'm modifying an app that was never meant to be
extensible. So, you are correct, Im moving the load to a daemon in the
middle
On Saturday 02 September 2006 00:21, Jack Faley ( The Tao of Jack ) wrote:
I have several ( 100 - 200 ) small exits c oming from an app that update
db2 tables. This works fine but the dba's don't like that many open
connection overheads. This isn't cgi/apache. These are all seperate
On 9/4/06, Darin McBride [EMAIL PROTECTED] wrote:
On Saturday 02 September 2006 00:21, Jack Faley ( The Tao of Jack ) wrote:
I have several ( 100 - 200 ) small exits c oming from an app that update
db2 tables. This works fine but the dba's don't like that many open
connection overheads. This
I have several ( 100 - 200 ) small exits c oming from an app that update db2
tables. This works fine but the dba's don't like that many open connection
overheads. This isn't cgi/apache. These are all seperate terminating
processes. From what I gather there is no way to pass the dbh between