Method processing ack/heartbeats

Under certain extreme conditions (out of memory situations, particularly) it is possible for a message to be successfully sent (in a TCP sense) from a client and received by the server, but not make it to the Intrepid layer. This can result in a situation where the client is hung waiting for a method return and the server doesn't know it should be processing the call.

To avoid this, an ack/heartbeat message should be introduced:

When a method invocation is received, the server should send an ack
Periodically while processing the method call, the server should send a heartbeat message to indicate that it is still working on the method.

The client can use this information to blow out the method call when appropriate.

Comments (1)