RE: [PHP-DEV] About ext/sockets/

> -----Original Message----- > From: sterling hughes [mailto:sterling@designmultimedia.com] > Sent: Sunday, June 24, 2001 9:49 PM > To: Lukas Beeler > Cc: php-dev@lists.php.net > Subject: RE: [PHP-DEV] About ext/sockets/ > > > On 24 Jun 2001 21:40:19 +0200, Lukas Beeler wrote: > > > > > > > -----Original Message----- > > > From: jani@zoidberg.pentap.net > > > [mailto:jani@zoidberg.pentap.net] On Behalf Of Jani Taskinen > > > Sent: Sunday, June 24, 2001 9:11 PM > > > To: Daniel Beulshausen > > > Cc: php-dev@lists.php.net > > > Subject: Re: [PHP-DEV] About ext/sockets/ > > > > > > > > > On Sun, 24 Jun 2001, Daniel Beulshausen wrote: > > > > > > >the issue that made the extension break was the step from > > > resources to > > > >longs for the socket fd's, this was necessary as win32 > > > socket fd's are > > > >different from bsd style socket fd's. > > > > > > So this is broken now only on *nix? Nice. > > > Previously it worked only on unices, now it works only on win32? > > > What an improvement. > > it isn't broken, i've just compiled the latest cvs, and the > > "new" sockets example script performed well, also with using > > pcntl to fork the "servers" > > > > well, it depends what you consider broken, when the extension was > commited, parts of it (*nix) were accessing integers like they were > structures... I've gone through the source code and will be committing > improvements, today or tommorow (i hope), there are a few functions > which are "broken". > > -Sterling of course it always depends on how you define broken as already said, i would classify it "experimental" and leave the "old" sockets extension as it is in upcoming releases till completion of the "new" sockets extension Lukas Beeler