I'd like your feedback on this proposal for a new operation set:
Operation Set Basic Instant Messaging Transport.
This operation set is defined for querying operational data on a
protocol's transport channel of a particular basic instant messaging
implementation. It can be used to query the boundaries and other
properties of this particular transport such that we can discover its
characteristics. Obviously, the Operation Set may be extended with
On a side note, by providing a new operation set that extends from
OperationSetBasicInstantMessaging it makes the implementation optional,
so it will not disturb protocol implementations that have no need for it.
Specifically for my use case, OperationSetBasicInstantMessagingTransport
is used to query the IRC protocol implementation for its maximum
supported message size in order to provide reliable message
fragmentation for the OTR plugin. In the case of IRC, its transport
supports messages of at most 512 bytes. Of these 512 bytes, 2 bytes are
used for the message ending (CRLF) and the message itself contains a
command and the receiving contact's address, which is variable in
length. Furthermore, the IRC server will prefix the message with the
identity string of the sender which contains a host name. All in all, we
need to compute how much capacity there is actually left for the
"payload", i.e. the actual message.
The (initial) version of the Operation Set can be found here:
The application of the operation set within the OTR plugin can be found
I'd like to push the changes in a few days and will take into account
the feedback that I get from this.