Yes I saw those but what it made me think, what's the point of a persistent socket if you can't use it again? And that very last comment
"I did not find an (easy) solution to this problem." to me implies there is a solution out there, it's just not easy. Well I hope there is one about. Anyway back to google :) > -----Original Message----- > From: Michael J. Pawlowsky [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 02, 2003 5:10 PM > To: Gareth Hastings; [EMAIL PROTECTED] > Subject: RE: [PHP] Some questions regarding pfsocketopen() > > > Two comments from the manual that are interesting: > > > php dot net at domainofdarkness dot com > 29-Jan-2001 04:26 > > OK, WRT to the p* functions opening a new connection when one already > exists. It is my understanting that (under Apache anyways) this is on a > per-process basis. If you do a 'ps auxw|grep httpd' on your server you > will see more than one process. What p* does is make a p-connection on one > of those processes only, the one that actually handles your request. > Chances are that when you hit the page again it will be answered by a > different process. I'm guessing if you keep hitting reload you'll get > around to the original process again and there will be no error message or > second connection open. Anyhow, this is true of all p* functions; they > open not one connection per server, but one connection per server > _process_. > > > venuti at sissa dot it > 13-Sep-2001 11:48 > > Don't expect to be able to open a persistent connection within a script > and resume it from a different script, not even if you save the value of > $fp with session_register (in fact, $fp is a resource id and cannot be > saved in this way). I did not find an (easy) solution to this problem. > > > > > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
