Software in distributed systems

A basic rule learnt in the Internet Community in the US is that in communicating systems, software should be ;SPM_quot;conservative;SPM_quot; in what it transmits;SPM_quot; and ;SPM_quot;liberal;SPM_quot; in what it receives. This means that if some large number of optional parameters are feasible when invoking a particular operation, avoid them unless they are required. However, on receiving an operation, be prepared to parse/check all possible options for sanity/correctness. A basic set of rules emerge for sanity checking: