"Wez Furlong" <[EMAIL PROTECTED]> writes:
> Which part of "EXPERIMENTAL" in the docs at
> http://www.php.net/manual/en/function.socket-select.php
> don't you understand?
>
> If you're so desparate to have things cemented, write a patch,
> post it here and we'll commit it.
> If you don't have the skills, you might consider offering those that
> do some positive incentive to do it for you.
The problem, Wez, is that this extension has been "experimental" for nigh on
two years, now. The API has been completely changed three times and never in
compatible ways. It is about time someone finished *one* cut of this thing!
Finish it off, work out the bugs, and even if it is a nasty mirror of the C
socket interface, at least there will be something supported. If you can't
make up your mind, rework it for socket2, which can replace the
then-deprecated socket extension. Every other scripting language has worked
this out, so it can't be too difficult. Clean it up and push it out the door
and let us have a working extension. At this point, I'm going to have to fork
it for internal use because we need a reliable interface for communicating
with our back-end systems.
It should not have to be up to the user to dig through CVS log entries and
php-dev postings to figure out when an age-old extension is going to be
solidified.
I apologize for the tone and frustration oozing out of these messages; I am
responsible for building PHP for our development and production environments,
as well as coding applictations that use the extension. I am unable to keep
up.
B
--
Brian Lalor | http://introducingthelalors.org/
[EMAIL PROTECTED] (email) | [EMAIL PROTECTED] (jabber)
N33°27.369' W111°56.304' (Earth)
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
