Thanks for the example. It worked just fine on my Linux box.
I was just being a bit too lazy I guess.. :)
On Sun, 24 Jun 2001, Brian Tanner wrote:
>Just thought I'd pipe up on this topic, cause its very applicable.
>I'm a 4th year Honours CompSci student. I've written some client server
>stuff in C (hence a little sockets experience), and I have been using PHP
>for a year now.
>My *only* complaint of PHP is that all the really fun stuff (memory sharing,
>sockets, couple of others) doesn't work for Windows.
>I've coded sockets for *nix in C before, but I am rusty. It took me 30
>minutes to get familiar and start coding with the new API. The changes are
>are very straightforward, and make the socket extension work more like the
>rest of PHP. Returning "0" for success and negative numbers just isn't how
>PHP does things.
>Considering a very low % of PHP programmers have extensive C socket
>experience, I wouldn't worry too much about making it inconvenient. You
>guys are just a little biased (IMHO), because you are all talented,
>experienced, C programmers.
>Anyway.. basically just wanted to say that I have used the new API, it works
>well, and I was very happy to see sockets making it to windows.
>From: Sascha Schumann [mailto:[EMAIL PROTECTED]]
>Sent: June 24, 2001 2:19 PM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: [PHP-DEV] About ext/sockets/
>> For lower-scale and home-use you can argue it is easier
>> than *nix. So when possible, you should try to support windows.
>> > [looked like C, was easier for ppl with C-background]
>> I don't think you should target php at C-ppl.
> PHP has been since its inception strongly influenced by C.
> And as a tool originally conceived on Unix, it should
> maintain its roots and continue to provide people familiar
> with Unix APIs a convenient way for scripting.
> Thus, improved Windows support should not come at the expense
> of Unix support without a perfect reason. I'm missing that
> reason here.
> I haven't looked deeply at what API changes have been
> introduced lately, but I'd suggest to use the standard BSD
> sockets return value semantics (-1 for failure, >= 0 for
> success). Those semantics also prevail in the Winsock
> implementation, so they should be quite natural.
> - Sascha Experience IRCG
> http://schumann.cx/ http://schumann.cx/ircg
>PHP Development Mailing List <http://www.php.net/>
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>To contact the list administrators, e-mail: [EMAIL PROTECTED]
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]