the method i described gives the user/app a potential way of establsihing/maintaining/using the same connection thoughout the life of the web app/session...
with this approach, one could possible have the 'persistent' conection handle to the db that i've been talking about... which would then allow for transactional processing across multiple pages within a web app.... -----Original Message----- From: Curt Zirzow [mailto:[EMAIL PROTECTED] Sent: Saturday, July 31, 2004 8:59 AM To: [EMAIL PROTECTED] Subject: Re: [PHP] db transactions across multiple pages... * Thus wrote bruce: > yeah... > > i saw that write up. i've also inquired with bugs.mysql as to if/whether > this might be reinserted.. we'll see. You don't need persistant connections with the method you describe. The pool app simply manages multiple connections. Curt -- First, let me assure you that this is not one of those shady pyramid schemes you've been hearing about. No, sir. Our model is the trapezoid! -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
