Re: Re: [PEPr] Comment on System::System_Socket
| From: | Jon Parise | Date: | Sun, 11 Apr 2004 05:37:53 +0000 |
| Subject: | Re: Re: [PEPr] Comment on System::System_Socket | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-27413@lists.php.net to get a copy of this message | ||
On Sun, Apr 11, 2004 at 01:52:40AM +0200, Michael Wallner wrote:
> >However, I do wonder whether it would be possible to apply this new
> >work to the existing Net_Socket class (and perhaps release it as
> >Net_Socket2?).
>
> Well, I guess it could be done, but don't take me wrong, this rather
> sounds like an excuse for not fixing existing Net_Socket for over half a
> year now. I'd for shure do the needed work on Net_Socket if the leads
> of the package are not willing/able to. I'm wondering why this rather
> simple but severe bug # 87 has not been fixed before getting stuck in
> the discussion on why (not) to rtrim data in readLine()? Sorry for the
> rant, but this particular issue is one typical of those needlessly
> rendering PEAR ridiculous. Dispite 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).
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)