David Hammerton wrote:
closing a socket, whilest thread 1 is still using it for send/recv,
which causes a problem - as yes, that would be a problem in any socket
environment.
I think some socket environments support this. The result would be that
the send/recv call returns with an error message
>
>
> I agree abotu the wiki (in fact, the information there is somwhere between
> misleading and wrong), but what's vague about my email?
>
> "Both the netconn and the socket API are thread-safe as long as you don't
> share
> one netconn/socket between multiple threads (i.e. don't access it from m
David Hammerton wrote:
> I need a bit of clarification on using lwip in a multi-threaded
> environment.
> The wiki page (http://lwip.wikia.com/wiki/LwIP_and_multithreading) is a
> little vague, as is this email response: (
> http://www.mail-archive.com/lwip-users@nongnu.org/msg07800.html)
I agr
On Fri, 2011-02-11 at 14:41 +1100, David Hammerton wrote:
> I'm interested in if you can use a _single connection_ of the netconn
> api
> from two threads: one for sending, one for receiving.
No, lwIP won't work in that situation.
Kieran
___
lwip-use
Hi there,
I need a bit of clarification on using lwip in a multi-threaded environment.
The wiki page (http://lwip.wikia.com/wiki/LwIP_and_multithreading) is a
little vague, as is this email response: (
http://www.mail-archive.com/lwip-users@nongnu.org/msg07800.html)
I'm interested in if you can u
