yeah...
i saw that write up. i've also inquired with bugs.mysql as to if/whether
this might be reinserted.. we'll see.
that said, it appears that there would need to be an approach similar to the
apache::dbi mod for perl, where you have an app that essentially does
connection pooling. in this model, an intermediate app becomes the app that
has the connection with the mysql server, and never shuts down. the web app
would 'talk' to the intermediate app to get the connection id/handle,
ensuring that the web app could get the same handle for all subsequent mysql
interaction on the pages of the web app....
ie....
+<----------->app1>>>>+
| v
mysql <----------- pool app
| ^
+<----------->app2>>>>+
in this case app1/app2 are both web apps running on apache
app1/app2 would talk to the 'pool app' to get the initial mysql db 'handle'.
the handle is stored/maintained for the life of the client web app.
once the pool app gets the handle, the web app fetches the handle at the
start of every page that has to perform db functions with mysql. subsequent
db functions for the page are then performed between the web app and mysql,
using the handle provided by the pool app....
that's the theory, not sure how it would work, or what other issues would
be. but if it did work, it could be extended to support any given web
app/server that needed to be able to maintain the connection with the db
over multiple pages...
-bruce
-----Original Message-----
From: Jim Grill [mailto:[EMAIL PROTECTED]
Sent: Friday, July 30, 2004 10:48 PM
To: [EMAIL PROTECTED]; 'John Nichel'; [EMAIL PROTECTED]
Subject: Re: [PHP] db transactions across multiple pages...
It's my understanding that persistent connections via the old ext/mysql was
a flawed misfeature to begin with. This was one of several misfeatrures
corrected by the new mysqli extension. There is some information on the
subject here: http://www.zend.com/php5/articles/php5-mysqli.php
It would be my guess that pconnect will be a thing of the past. It's sort of
a drag, but running out of connections - as pconnect can cause - is a real
drag too. ;)
Jim Grill
Web-1 Hosting
http://www.web-1hosting.net
----- Original Message -----
From: "bruce" <[EMAIL PROTECTED]>
To: "'John Nichel'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, July 31, 2004 12:10 AM
Subject: RE: [PHP] db transactions across multiple pages...
> you also won't see the mysqli pconnect function... which tells me that at
> least for now, it's not there...
>
> -bruce
>
>
> -----Original Message-----
> From: John Nichel [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 30, 2004 8:44 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [PHP] db transactions across multiple pages...
>
>
> bruce wrote:
> > not sure if it's php/mysqli... but if you check the php.net for the
> "mysqli"
> > not "mysql" functions... you won't see the persistent attribute listed
for
> > the php.ini attributes...
>
> I wouldn't worry too much about that though. I mean if persistant
> connections are required for transactions, I'm sure it will be there.
> The only reason we may not be seeing it now is because the PHP5
> documentation is full of holes (with it not being a production release
> yet). I know of a few items that are available in PHP5 that aren't
> documented on php.net yet.
>
> --
> By-Tor.com
> It's all about the Rush
> http://www.by-tor.com
>
> --
> 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
>
>
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
