Em 19-03-2014 10:49, Pomeroy, Marty escreveu:
>> BUT never can t1 and t2 both access s1 or s2.
Can someone provide a common situation which requires one socket used
on multiple threads? If not, given the effort that would be needed,
the lack of requirement, and the simplicity of working with lwIP as it
is...
A common situation is to have one thread listening synchronously
(blocking) and another task wants (for example, due to some error) to
disconntinue the comunication and close that socket.
there are situations where different threads send and recieve, but I
don't remember of any example.
but having each socket stick to it's thread if not a big problem... you
just have to pool for new data and doing a task-delay
Alain
Marty
_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
