If that's the case (actually, if it's the case for Linux which I personally
only care about), then I guess I won't miss it :) I was thinking maybe a
stream_socket_set_option() would be nice, but I personally only used it to
for SO_REUSEADDR, which seems to be default behaviour for a socket stream
n
IIRC, quite a few OSs also ignore whatever you pass to listen()
At 08:19 AM 8/9/2004 +0100, Wez Furlong wrote:
The listen(2) backlog? It defaults to 5, and there is no way to alter
this, yet.
Exposing more lower level features is a TODO item; you're welcome to
suggest which ones you need.
--Wez.
O
The listen(2) backlog? It defaults to 5, and there is no way to alter
this, yet.
Exposing more lower level features is a TODO item; you're welcome to
suggest which ones you need.
--Wez.
On Mon, 9 Aug 2004 09:01:43 +0200, Ron Korving <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm using the socket str
Hi,
I'm using the socket stream and it seems to work just great for me, but with
the stream_socket functions some original socket features seem lost. Is
there any way to work around this? Maybe there is need for a
stream_socket_set_option function? I personally bumped into this lack of
features wh
