I have written a small embedded TCP/IP server application but it needs to work lock-step: one query then one response.
My problem is that the client (not under my control) making the requests is running ahead and I don't have the resources to buffer-up an arbitrarily large number of queries.
When a query comes in to the server, it arrives in the tcp_callback function. Data is arriving before I've fully sent the response to the previous one.
How do I impose some flow control on incoming data so that I can do things lock-step ?
Ah, thank you. That seems like just what I wanted. I am currently working on an out-of-date version of RL-ARM anyway, due to management messing about where I work.
I will convince my boss that I need a more up-to-date version of RL-ARM.