For anyone interested, the modified package lies here:
http://scaprile.ldir.com.ar/cms/category/os/lwhttpd/
Regards
--
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
BUT never can t1 and t2 both access s1 or s2.
Practically speaking, a socket is a stream of data, and it doesn't make
sense for tasks to contend for that stream. You would need to provide
additional coordination mechanisms at the application level to make sure
t1 is not getting t2's data
Pomeroy, Marty wrote:
BUT never can t1 and t2 both access s1 or s2.
Practically speaking, a socket is a stream of data, and it doesn't make sense
for tasks to contend for that stream.
Close, but not exactly. A socket is *two* streams of data, TX and RX. And even
if I can't tell you
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
