Re: [PHP4BETA] MySQL module #2
| From: | Zeev Suraski | Date: | Sat, 04 Sep 1999 21:37:50 +0000 |
| Subject: | Re: [PHP4BETA] MySQL module #2 | ||
| References: | 1 2 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-4096@lists.php.net to get a copy of this message | ||
At 17:47 04/09/1999 , Andreas Karajannis wrote:
Zeev Suraski wrote:Look at the persistent connect code. At the end of a persistent connect, the resource is saved in the regular resource list, and thus it's 100% transparent. Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/ For a PGP public key, finger bourbon@netvision.net.ilWhen adding a new persistent connection, the MYSQL struct gets added to the persistent list - but not to the 'normal' list (probably register_resource does this). In zend_fetch_resource_ex(), only list is searched, so unless on request initialization resources from the plist are copied over to list, you won't be able to access persistent connection data after the request it was created.Nothing changed in the logic of that code, only implementation. The persistent resource methodology introduced in the MySQL module treats persistent resources (persistent links in this case) just like non-persistent resources. The only difference is in connect time. I'm still confused, since I still can't see how and if persistent resources make their way into the global, nonpersistent list - from where zend_fetch_resource_ex gets them.