Date: 08/28/00
- Next message: Jani Taskinen: "Re: [PHP-DOC] About QUICK REF"
- Previous message: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions network.xml"
- In reply to: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions network.xml"
- Next in thread: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions network.xml"
- Reply: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions network.xml"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I say go ahead. Especially since it's something that has to be enabled at
compile time. Socket work can be complex and I think that a well written
<partinfo> would be very helpful. Especially to explain any differences
there might be between the C socket calls and the PHP socket calls.
Let me know if you would like some help. I was actually considering
starting the Socket docs myself, but I wasn't sure if someone had already
been working on it.
Daniel
----- Original Message -----
From: "Lars Torben Wilson" <torben <email protected>>
To: "Daniel Beckham" <danbeck <email protected>>
Cc: <phpdoc <email protected>>
Sent: Monday, August 28, 2000 1:13 PM
Subject: Re: [PHP-DOC] cvs: phpdoc /en/functions network.xml
> Daniel Beckham writes:
> > Should the new Sockets extensions be in a separate section? Unless,
they
> > work properly with existing network functions, they should really be
> > separated. There are a large number of functions in that new extension
and
> > they could be lost in the crowd.
> >
> > Daniel
>
> I actually started that way...and I've still got the files lying
> around if we decide to change it. I moved it all into the Network
> section because I was looking at it and thinking that...well, the
> socket functions *are* network-type functions for the most part. And
> so it went.
>
> That said, I'm not really happy with having them in the Network
> section. together. Reasons: a) Sockets don't necessarily have
> anything to do with the network (AF_UNIX), b) These functions are all
> part of an extension which must be enabled separately at compile time,
> and c) I have no idea whether they are meant to play nicely with the
> existing socket code. :)
>
> So I have no problem splitting them back out. It'd make it much nicer
> to have a separate <partintro> for this anyway. :) Unless anyone else
> has objections, I'll try to get it done today.
>
>
> Cheers,
>
> Torben
>
> --
> +----------------------------------------------------------------+
> |Torben Wilson <torben <email protected>> Netmill iTech|
> |http://www.coastnet.com/~torben http://www.netmill.fi|
> |Ph: 1 250 383-9735 torben <email protected>|
> +----------------------------------------------------------------+
>
- Next message: Jani Taskinen: "Re: [PHP-DOC] About QUICK REF"
- Previous message: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions network.xml"
- In reply to: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions network.xml"
- Next in thread: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions network.xml"
- Reply: Lars Torben Wilson: "Re: [PHP-DOC] cvs: phpdoc /en/functions network.xml"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

