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

2001-06-25 Thread Joey Smith
Not to beat a dead horse, but I'm glad someone else noticed this. I almost went back to bed, thinking the whole world had gone mad. :) On Mon, 25 Jun 2001, Jani Taskinen wrote the following to Zeev Suraski : > >tagged as experimental makes it easier for us to change the API to a > >PHP-like API,

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

2001-06-24 Thread Andi Gutmans
At 08:21 PM 6/24/2001 +0200, Jani Taskinen wrote: >What new functionality? Why the hell should the API change? >Only the function names should have been changed, not break >the whole extension! It's a rewrite which is more in the PHP spirit. i.e. return true/false and not -1/0 and stuff like th

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

2001-06-24 Thread Zeev Suraski
At 03:23 25/6/2001, Brian Tanner wrote: >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. Not all of us a

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

2001-06-24 Thread Jani Taskinen
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. > >-Brian Tanner > > > > > >-Original Message----- >From: Sascha

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

2001-06-24 Thread Jani Taskinen
On Mon, 25 Jun 2001, Zeev Suraski wrote: >At 22:10 24/6/2001, Jani Taskinen wrote: >>So this is broken now only on *nix? Nice. >>Previously it worked only on unices, now it works only on win32? >>What an improvement. > >Let's keep cynicism off this list, please... :-p >About the socket extensio

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

2001-06-24 Thread Brian Tanner
rom: 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/ Jeroen, > For lower-scale and home-use you can argue it is easier > than *nix. So when possible, you should try to support w

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

2001-06-24 Thread Zeev Suraski
Sascha, PHP is an established language on its own now, with failure semantics of its own. Failure in PHP is noted by false and resource (i.e. anything which is not a language primitive or composite type) are contained in IS_RESOURCE handles. The original socket implementation was wrong in th

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

2001-06-24 Thread Zeev Suraski
At 22:10 24/6/2001, Jani Taskinen wrote: >So this is broken now only on *nix? Nice. >Previously it worked only on unices, now it works only on win32? >What an improvement. Let's keep cynicism off this list, please... About the socket extension - this was discussed, and agreed upon that the way

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

2001-06-24 Thread Sascha Schumann
Jeroen, > 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 i

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

2001-06-24 Thread Lukas Beeler
> -Original Message- > From: sterling hughes [mailto:[EMAIL PROTECTED]] > Sent: Sunday, June 24, 2001 9:49 PM > To: Lukas Beeler > Cc: [EMAIL PROTECTED] > Subject: RE: [PHP-DEV] About ext/sockets/ > > > On 24 Jun 2001 21:40:19 +0200, Lukas Beeler wrote: &g

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

2001-06-24 Thread jeroen
> [don't break the API!] > >i'd vote not for changing the api back, rather than > updating/extending the > >yet available (tiny) sockets documentation. > > I vote we get the old api back. I don't care if it doesn't > support win32. 1) IMHO the new API is better (the 'write' function is really a

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

2001-06-24 Thread sterling hughes
On 24 Jun 2001 21:40:19 +0200, Lukas Beeler wrote: > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]] On Behalf Of Jani Taskinen > > Sent: Sunday, June 24, 2001 9:11 PM > > To: Daniel Beulshausen > > Cc: [

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

2001-06-24 Thread Lukas Beeler
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Jani Taskinen > Sent: Sunday, June 24, 2001 9:11 PM > To: Daniel Beulshausen > Cc: [EMAIL PROTECTED] > Subject: Re: [PHP-DEV] About ext/sockets/ > > > On Sun, 2

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

2001-06-24 Thread Daniel Beulshausen
At 21:10 24.06.2001 +0200, Jani Taskinen wrote: >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

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

2001-06-24 Thread Jani Taskinen
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 onl

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

2001-06-24 Thread Daniel Beulshausen
At 20:58 24.06.2001 +0200, Daniel Beulshausen wrote: >jani, > >At 20:21 24.06.2001 +0200, Jani Taskinen wrote: > >>What new functionality? Why the hell should the API change? >>Only the function names should have been changed, not break >>the whole extension! > >the issue that made the extension b

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

2001-06-24 Thread jeroen
> > Because of the experimental status, I don't think phpdev should worry too > > much about the > > incompatibility, it's the user's own reponsibility to use an experimental > > module. > > Taking a look at the changes to the sockets extension, some break things > on a Linux system, some don't wo

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

2001-06-24 Thread Daniel Beulshausen
jani, At 20:21 24.06.2001 +0200, Jani Taskinen wrote: >What new functionality? Why the hell should the API change? >Only the function names should have been changed, not break >the whole extension! the issue that made the extension break was the step from resources to longs for the socket fd's

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

2001-06-24 Thread Jani Taskinen
What new functionality? Why the hell should the API change? Only the function names should have been changed, not break the whole extension! --Jani On Sun, 24 Jun 2001, Andi Gutmans wrote: >Maybe we should wait with this whole API change until a new sub-version? >4.1? Or keep the old function

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

2001-06-24 Thread sterling hughes
On 24 Jun 2001 17:43:02 +0200, [EMAIL PROTECTED] wrote: > The documentation has just been updated, stating that the sockets-module is > still experimental. > As has any module having an EXPERIMENTAL file in it's directory. > > Because of the experimental status, I don't think phpdev should worry

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

2001-06-24 Thread jeroen
The documentation has just been updated, stating that the sockets-module is still experimental. As has any module having an EXPERIMENTAL file in it's directory. Because of the experimental status, I don't think phpdev should worry too much about the incompatibility, it's the user's own reponsibil

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

2001-06-24 Thread Andi Gutmans
Maybe we should wait with this whole API change until a new sub-version? 4.1? Or keep the old functionality right now and just add the new functions? We can deprecate the old ones in 4.1. Andi At 03:03 PM 6/24/2001 +0200, Jani Taskinen wrote: >Since everybody seems to be using some stupid fil