Formal specification and analysis of accelerated heartbeat protocols
Proceedings of the 2010 Summer Computer Simulation Conference
| Hi-index | 0.00 |
We consider communication primitives that can be executed by anapplication process to exchange messages with another applicationprocess over a TCP/IP network. A communication primitive is calledalert iff it satisfies two conditions. First, if during anyexecution of the primitive no failure occurs, then the executioncompletes successfully. Second, if during any execution of theprimitive some failure occurs, then the execution is aborted andthe process that initiated the execution is informed of thefailure. Clearly alert communication primitives are useful indesigning reliable distributed applications. We argue that the sendprimitive over TCP is alert, but the receive primitive over TCP isnot. Then, we propose three new receive primitives over TCP andshow that each of them is alert. We also discuss how to implementthese three primitives and compare their performance.