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
We really should have a protocol that is extendable, allowing new fields to be reported without breaking compatibility with older clients. Adding a new protocol version for every new item of data we want to add will be quite cumbersome.
A simple way to improve the current semi-colon separated fields would be to have a field count at the beginning of every group of fields. Then we could add new fields to the end of groups without breaking compatibility with older clients. Older clients wouldn't be able to display the new fields, of course, but all of the old info would still be valid.
The text was updated successfully, but these errors were encountered:
We really should have a protocol that is extendable, allowing new fields to be reported without breaking compatibility with older clients. Adding a new protocol version for every new item of data we want to add will be quite cumbersome.
A simple way to improve the current semi-colon separated fields would be to have a field count at the beginning of every group of fields. Then we could add new fields to the end of groups without breaking compatibility with older clients. Older clients wouldn't be able to display the new fields, of course, but all of the old info would still be valid.
The text was updated successfully, but these errors were encountered: