anyone know what timer is used in the lwip stack for reading tcp/ip packets?
I got the following problem: posting a message which is fragmentated by the client will result in more then 1 message as the stack deliveres a not completed message. I already made a workaround to glue a messages framentated in 2 parts, but now i got a situation that a message even when is it count is low like 600 bytes, is framentated in 100, 20 and 500 bytes.
I use this code to read a post len = pConnectedSock->recv(buff,1800);. the buffer itself is long enough, it is just that the client send a framentated parts.
If i try the same in Ubunto, it works fine, as this is only 1 complete message. Mac Os will also split a message in parts.
It must be a setting in the liwp somewhere with a timer which wait for a certain time before it outputs the message to process.
Please log in to post a reply.
mbed, the fastest way to prototype with ARM based microcontrollers.
^ back to top