[Top][All Lists]

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

[lwip-devel] Netconn events?

From: Freddie Chopin
Subject: [lwip-devel] Netconn events?
Date: Thu, 06 Oct 2016 21:09:26 +0200


Is there a specific reason why netconn events cannot be called in a
straightforward way? Why can't we just have events like "received",
"accepted", "acknowledged", "connected", "closed", etc. instead of all
this crazy stuff with "receive plus" meaning almost the same as
"receive minus", both meaning something different depending on whether
length is zero or not (in the former case this event can actually mean

There only explanation of these events that I've found online is on the
eCos website


I must say that this is far from being clear and I really don't get the
difference between "plus" and "minus" variants, not to mention the mess
with receive with zero length...

BTW - would this be possible to have a function/macro to set/clear
callback for a created netconn? For example I'm only interested in
having a callback in the netconn of the connection (returned by
netconn_accept()), not in the one created with netconn_new().

I'm sending this whole message because I've been thinking about doing a
netconn thread that can do non-blocking receive, while other thread
will do infrequent sends (everything serialized with a mutex), together
with the requirement to close the netconn from this second thread,
requires the use of callbacks, but this seemingly trivial thing seems
so extremely complicated (lack of good examples doesn't help), that
I've thought there's a room for improvement here...


reply via email to

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