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, this was necessary as win32 socket fd's are
different from bsd style socket fd's.
as this change would already have broken the extension i decided to update
the api as well, mainly the functions names, but also some return types.
if the actual behaviour is unwanted it should be changed, i myself find the
api now much more useable (userfriendly).
the extension works pretty well under win32 now, but if there are functions
that are broken under posix i suggest that someone with more knowledge of
the bsd sockets than i has a look at them.
i'd vote not for changing the api back, rather than updating/extending the
yet available (tiny) sockets documentation.
daniel
>--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 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 filters which filters
> >>all emails which have 'Bug' in the Subject I have to mail this again..
> >>(Hint: There is X-PHP-Bug: header in those emails that come from bug
> system)
> >>
> >>Anyway, we have a problem. The sockets extension is seriously fucked up
> >>now. Some functions don't work at all and some work differently than
> >>before the renaming of the function names. ie. they return FALSE
> >>on errors now..before they returned -1. Good example: socket_listen()
> >>
> >>This is really bad thing and breaks every single script out there
> >>which uses these functions. It would be acceptable that the function
> >>names only needed to be changed, but now there has to be really big
> >>changes in the whole logic the scripts work.
> >>
> >>(even our example scripts on manual don't work)
> >>
> >>--Jani
> >>
> >>
> >>On 22 Jun 2001 [EMAIL PROTECTED] wrote:
> >>
> >> >From: [EMAIL PROTECTED]
> >> >Operating system: Slackware-current / Kernel 2.4.5
> >> >PHP version: 4.0 Latest CVS (2001-06-22)
> >> >PHP Bug Type: Sockets related
> >> >Bug description: Socket function examples scripts aren't working with
> >> latest CVS
> >> >
> >> >After checking the renamed socket functions, i tried to get the sockets
> >> >example script running. It works fine under 4.0.5, so i renamed the
> >> >functions to the new ones, und tried to get it running. It started, and i
> >> >could connect without problems, but instead of being an echo server, i
> >> >just got disconnectet.
> >> >When are the new sockets function getting documented with an example
> >> script ?
> >> >thx in advance
> >>
> >>
> >>--
> >>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]
> >
/*--
daniel beulshausen - [EMAIL PROTECTED]
searching job: application development with php
using php on windows? http://www.php4win.de
--
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]
