[Top][All Lists]

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

[lwip-devel] [task #6935] Problems to be solved with the current socket/

From: Simon Goldschmidt
Subject: [lwip-devel] [task #6935] Problems to be solved with the current socket/netconn API
Date: Thu, 24 May 2007 13:52:42 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20070309 Firefox/

Follow-up Comment #7, task #6935 (project lwip):

>I vote for re-implementing the sockets API from scratch directly on top of
the raw API using mutexes for synchronization.

Me too. Only I think we should first shrink the list of bugs, patches and
tasks. Then we can decide if the rewrite is going to be before or after the
next release.

> Function-like macros could be used to control it so that we don't have a
mess of ifdefs - depending on the user's chosen options, some will evaluate
to nothing.

That's the way I'd do it. Only (as I said before) I would also integrate some
of those macros into the core. That way, ARP doesn't get locked while TCP is
still copying segments.


Reply to this item at:


  Nachricht geschickt von/durch Savannah

reply via email to

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