|
> David, thanks for sharing your code... But I have a question... What > are the benifits of connection pooling, and when would I use them? Overhead of initial connection (connection job startup, user authentication, etc) is all done up front, not when you are trying to establish the connection. When you start to run out of connection management jobs on the 400 (QZDASOINIT), the pool will detect this and startup new ones (within certain parameters). System resources can be controlled ... if you have a runaway job, that keeps opening connections & never closes them, you can specify a maximum number of connections so you don't hammer your system into the ground. There may be others, but these are the benefits that pop to the top of my head. david -- David Gibbs Sr. Software Engineer / R&D / MKS Inc., www.mks.com Lombard, IL, USA; tel: 630-495-2108; fax: 630-495-3591 Build Better Software
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
