Re: [lwip-users] Aborting and restarting a TCP request

2015-12-02 Thread Sergio R. Caprile
My understanding is that it is not safe to stop calling sys_check_timeouts(). Even after a connection is closed, there is housekeeping to be done due to the nature of TCP. As per the wiki, I'm just another user but a contributor to the wiki. Running AdBlock Plus I can live with wikia. You can sugg

Re: [lwip-users] Aborting and restarting a TCP request

2015-12-01 Thread Andy Pont
Hi Sergio, > Your problem with resending requests seems to be the subtleties of the > HTTP and TCP protocols. In TCP, you either have a connection > established and can send data, or you don't. If you need to close the > connection, then call the close function, if you need to send data again, >

Re: [lwip-users] Aborting and restarting a TCP request

2015-11-30 Thread Sergio R. Caprile
Please read the wiki; your error callback will be called or an error condition signalled on your receive callback when the connection is lost. Your problem with resending requests seems to be the subtleties of the HTTP and TCP protocols. In TCP, you either have a connection established and can send

[lwip-users] Aborting and restarting a TCP request

2015-11-27 Thread Andy Pont
Hello, As explained in some of the previous emails I have implemented (using examples from the internet) a simple HTTP client sat on top of the raw interface. The program flow is roughly as follows... - main() calls a function called http_send_request() which registers the callback functions and