[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [patch #5914] Move sockopt processing into tcpip_thread

From: Simon Goldschmidt
Subject: [lwip-devel] [patch #5914] Move sockopt processing into tcpip_thread
Date: Fri, 04 May 2007 15:41:57 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20070309 Firefox/

Follow-up Comment #12, patch #5914 (project lwip):

>That's why, to my point of view, an LWIP_SOCKETS option and a
netconn_options() function is a better solution, but if you don't like it...

Jonathan wrote:
>In due course I'm sure it makes sense for netconn to also have a way to set
options, although I wouldn't want to channel them all through a single
function like BSD does.

I must say I agreee with Jonathan. For netconn API, I wouldn't put all
options in one function but create more functions eliminating all the
parameter-checking (set/getsockopt() are quite big...). An LWIP_SOCKETS
options is not necessary, I think. If you don't use sockets, just don't
include sockets.c in your app. As netconn API is always included, I think we
wouldn't gain anything from such a define, or would we?


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]