[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: Kieran Mansley
Subject: [lwip-devel] [task #6935] Problems to be solved with the current socket/netconn API
Date: Thu, 24 May 2007 12:17:21 +0000
User-agent: Opera/9.21 (X11; Linux i686; U; en)

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

The suggestions you make seem to be along the lines of fixing up the existing
sockets API.

There seems to be a lot of support at the moment for implementing a new
sockets API on top of the raw API rather than the netconn API.  I think this
is worthy of further investigation, and on the condition that we can (i) do a
better job of supporting the sockets API than we have already; (ii) and not
require additional stuff inside the stack to support it on the raw API; then
I think it would be worth trying.  However, this is very low priority.

Note, I would still retain the netconn API even if the sockets API on top of
it was removed.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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