Re: Re: [PEPr] Comment on System::System_Socket
| From: | Michael Wallner | Date: | Sun, 11 Apr 2004 08:53:07 +0000 |
| Subject: | Re: Re: [PEPr] Comment on System::System_Socket | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-27414@lists.php.net to get a copy of this message | ||
Jon Parise wrote:
On Sun, Apr 11, 2004 at 01:52:40AM +0200, Michael Wallner wrote:
Sorry Jon, I might have been a bit too "hot". System_Socket is probably not able to do the work Net_Socket is supposed to do, because fsockopen('https://secure-site', $port); which is easily done with Net_Socket means to implement SSL communication in PHP code yourself, at least I guess. Regards, MichaelDispite that I also guess that PHPs builtin stream wrappers don't apply to sockets/connections created with System_Socket, so a SSL connection could not be established.I'm cool with a "competing" System_Socket package, but I also think there's value in calling this new code Net_Socket2 and superceding the "stale" Net_Socket(1) code base. That way, we get a new, maintained Net_Socket package, and we don't have two competing socket packages (the existing, but unsupported Net_Socket package and the new, maintained System_Socket package).