Re: sockets

There's only one thing it's missing -- the equivalent of socket_get_status(), which is not part of the extension, despite the name. If I set my socket to nonblocking, the only way to tell if it has died is to try to write to it, which isn't always a desirable thing to do :) Unless there's another way that I just don't understand. J Smith wrote: > > I've been using it since the first API revision and it's been working fine > for me. (Up to and including the latest API revision.) As far as I'm > concerned, it's getting pretty close to losing the experimental tag. > (Perhaps by PHP 4.3.x or so, barring any glarring problems that I've not > encountered.) > > J > > > Markus Fischer wrote: > >> Hi, >> >> Simple when enough people have tested it and it reaches the >> consensus that it's mature enough for being called stable >> (api doesn't change anymore, more testers, you name it). >> >> - Markus >> >> On Thu, Apr 25, 2002 at 07:46:30PM +0200, Michael Virnstein wrote : >>> Hi, >>> >>> as i could read in the manual, the socket functions are completely >>> experimental. >>> When do you think the API gets final and won't change >>> anymore. Any comments on this are welcome. >>> >>> Michael >>>