[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] sockopt inheritance?
From: |
Kieran Mansley |
Subject: |
Re: [lwip-users] sockopt inheritance? |
Date: |
Fri, 18 Sep 2009 08:41:57 +0100 |
On Fri, 2009-09-18 at 09:19 +0200, Fabian Koch wrote:
>
> Hey all,
>
> I was wondering if a Socket that is returned by accept() (or a netconn
> by netconn_accept() which I use) does inherit all the sockopts that
> were set for the listeninge/accept Socket?
> I tried to follow the code but what I found looked like it returns a
> newly allocated netconn/socket with the default options, so one would
> have to set all opts again for that one?
I'm not sure but that is what I would expect. It should be easy to
test.
> Do I have to getsockopt from the listening socket and setsockopt on
> the one that accept() returns by hand each time?
That would be a simple solution.
> Also, google didn't help me in any way how the behavior is with
> "standard" BSD sockets or their implementation on different
> platforms.
I'm not sure about the standard behaviour either, but I can see why it
might be useful to have different options on the listening and data
sockets.
Kieran