You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An autoskip features does not solve version missmatches, it seems better to define version boundaries in the following manner:
1. Introduce a "Since" column for options to track version
2. Introduce a compatibility field in info-data.
Set in server: This informs the client which rcp-version is actually in use by the application (vs. the rcp-version the rcp-server supports). The compatibility rcp version is derived from the entry in the "since version"-column of the options in use.
Set in client: this informs the server about the clients backwards compatibility and can only be major versions. This is the case because adding options only increases the minor version. Major version changes indicate a breaking change in the protocol (e.g.: changing an options datatype).
Client and server can implement different code paths for different major versions to be backward compatible.
How can a parser skip unknown options - by encoding the option-type in the option-id or by introducing a option-type id as a separate byte
The text was updated successfully, but these errors were encountered: