SUP vs. INF SU
Posted: 24 Mar 2013, 14:27
The post SUP vs. INF SU clarifies the use of features in the SUP vs INF SU. Basically, the SUP is for how messages are sent between two parties while the INF SU specify which messages may be sent. . I'd like to propose the inclusion of this distinction in the specification.
This should be added in the Features section so that it would completely be;Features advertised in the SUP specify 'how' messages in the current connection may be sent. E.g., encryption or compression of the stream of data.
Features advertised in the INF SU field specify 'what' messages are (or may) be sent. E.g., user commands or bloom filters.
=== Features
Features are used to indicate support for protocol commands or functionality.
The server may use any feature that the client indicates support for regardless of its own SUP and vice versa. A client can announce features in the SUP regardless of the INF's SU field and vice versa.
Features advertised in the SUP specify 'how' messages in the current connection may be sent. E.g., encryption or compression of the stream of data.
Features advertised in the INF SU field specify 'what' messages may be sent. E.g., user commands or bloom filters.
A feature name consists of four uppercase letters, where the last letter may be changed to a number to indicate a revised version of the feature.
A central register of known features is kept to avoid clashes, see below features in this protocol and the features in the extension document.