[PHP-DEV] Re: Sockets Extension Rework (API, etc...) VERY LONG

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > vs. > > while(($retval==socket_read($sock, $buf, $len)) > 0) { > // do something > } > if ($retval==-1) { > print strerror(socket_last_error($sock)); > } elseif ($retval==0) { > $eof=1; > print "Eof has occured!!!"; > }

Re: [PHP-DEV] Re: Sockets Extension Rework (API, etc...) VERY LONG

Coo. I never really got into the rationale behind the C API, all that kernel optimization, which is interesting. I haven't had any problems yet with fd_clear, but I don't use it intensely. (Once, maybe twice in a script.) Anyways, anything that will make the extension better is a good thing.

Re: [PHP-DEV] Re: Sockets Extension Rework (API, etc...) VERY LONG

On Thu, 2002-02-21 at 18:09, J Smith wrote: > > I'm all for fixing this extension up to make it better, Great!!! > but I'm a little > concerned with totally dropping the fd_* functions. How would you mimic > their use in something like a multiplexing using a blocking call situation > after

[PHP-DEV] Re: Sockets Extension Rework (API, etc...) VERY LONG

I'm all for fixing this extension up to make it better, but I'm a little concerned with totally dropping the fd_* functions. How would you mimic their use in something like a multiplexing using a blocking call situation after the change? I have no idea how it can be done without using the fd_*

Re: [PHP-DEV] Re: Sockets Extension Rework (API, etc...) VERY LONG

> On Wed, 2002-02-20 at 19:29, Richard Samar wrote: > Hi Jason, > Hello Richard, > I was the "extension user" talking about a few of the problems :-) > I still had not the time to take a look at all the functions. > > > 1. Consistency problems > > a. Some functions take host, some take ip,

[PHP-DEV] Re: Sockets Extension Rework (API, etc...) VERY LONG

...posting at 2:30am can lead to "interesting" sentence constructions. my appologies :-) -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] Re: Sockets Extension Rework (API, etc...) VERY LONG

Hi Jason, I was the "extension user" talking about a few of the problems :-) I still had not the time to take a look at all the functions. > 1. Consistency problems > a. Some functions take host, some take ip, some take both > b. Parts of the code use socklen_t, parts use int > c.