Topic HTTP Content-Length
This board is threaded (i.e. has a tree structure). Please use the Reply button of the specific post you are referring to, not just any random button. If you want to reply to the topic in general, use the Post button near the top and bottom of the page.
In Response to PeterW
> And in theory, read should never return EWOULDBLOCK, because the code just polled the file descriptor.
Yes, but I am actively provoking one by calling recv again - this is what you want to change, don't you? And the reason is that I'm not sure that I will a proper "readable" notification before I haven't really made sure everything has been read. After all, data could arrive just after the first recv call.
And sorry. I guess I should have replaced that comment by something more informative back then. I am actually not sure anymore whether malloc played a role in this. Hm, maybe a combination: malloc returning a null pointer, then recv throwing up?
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill