FreeLists / openbeosnetteam / [openbeosnetteam] Re: socketpair() implementation

[Jérôme Duval <korli@xxxxxxxx>]

Selon Philippe Houdoin <philippe.houdoin@xxxxxxx>:

> Well, as it's missing for POSIX 1003.1 compliance, I guess supporting it will
> be
> great. Not mandatory for R1, thought, but it's not like it's that hard to
> implement.

Indeed, though it's needed for some http/ftp servers, it would be helpful
anyway.

>
> > I added a socketpair() prototype in our header sys/socket.h.
>
> I saw this, yes.
>
> > My opinion about implementation would be to have a socketpair() in
> > src/kits/network/libsocket/socket.c which does (for AF_INET at least):
> > - calls socket() twice to have two sockets.
> > - call a new ioctl to have the network stack do the socketpair hard job :
> > bind(), listen(), connect(), accept()
> > - close the listening socket.
>
> Sounds good to me, indeed.
> BTW, these sockets are supposed to be unbounded.

It's unclear to me what means "unbounded", I just understand "connected".

>
> > As I never tested the Haiku network part, maybe I'm not the right person to
> > code this.
>
> Then just implement a noop socketpair() in socket.c (both in libsocket and in
> libnet variant) and I'll self assign the task to implement it later.

Then ok :)

>
> I don't consider this as urgent as reaching beta stage of OpenGL Kit and the
> network stack missing features: DHCP, 802.11 support.
> Maybe that's because I never used socketpair() so far ;-)
>

Don't know much about this ...
Bye,
Jérôme