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 ?
Richard, I had a quick look at the docs for RL-ARM TCP/IP library here: http://www.keil.com/support/man/docs/rlarm/rlarm_tn_tcpip_prot.htm
It does appear that with this API there is no way to stall reception of TCP data without stalling all TCP activity. Basically, you must process the incoming data as soon as it arrives. This appears to be a severe limitation of this library. One could argue that for some applications this simply cannot work.
- mike