I was informed from a local provider about the following issue concerning
pconnects with php:
----------------------------------------------------------------------------
"A pconnect has a running time of 8 hours. A close function will be ignored.
Apache has a threading concept, which doesn't cancel the thread. You can
configure it but the thread will live till the last connection is closed.
( 8 hours after a pconnect ).
Every new URL rquest will lead to a new thread with a new database connection
with a live evalution of 8 houers.
To say it simple: "if 10 user clicks on 5 sites with php scripts
-> 50 pconnects will be active."
----------------------------------------------------------------------------
To be honest: I don't have a clue how a pconnect is executed on a LAMP-System.
All I know is the I can limit the count of pconnects in the
php.ini.
The Question I now have is if it's true that scripts should contain a mysql_connect
instead of a pconnect or can I avoid this overhead ?
--
Best Regards,
Mark
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
