This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to prevent TCP/IP reception until I'm ready

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 ?

Parents
  • my previous response was related to control mechanisms of the protocol itself. at application level, can't you implemented some internal protocol to offer you more control over meaningful (that is, valuable to you) messages that are exchanged?

Reply
  • my previous response was related to control mechanisms of the protocol itself. at application level, can't you implemented some internal protocol to offer you more control over meaningful (that is, valuable to you) messages that are exchanged?

Children
No data