| 2016-06-29 21:14:02 |
Chad Smith |
description |
Juj2ubeta10 underwent lower-casing of most websockets api parameters, as a result there is now an inconsistency in how machine change deltas list of 'Addresses' are represented versus the list of 'servers' in the login response. Addresses uses camelcase Scope, Type, SpaceName, Value, etc. Login response 'servers' uses lowercase scope, type, port value.
As an api consumer, we have been using the same logic to parse Addresses and servers from the different responses, it adds a little complexity to cope with the inconsistencies in response structure. |
Juj2ubeta10 underwent lower-casing of most websockets api parameters, as a result there is now an inconsistency in how machine change deltas list of 'Addresses' are represented versus the list of 'servers' in the login response. Addresses uses camelcase Scope, Type, SpaceName, Value, etc. Login response 'servers' uses lowercase scope, type, port value.
As an api consumer, we have been using the same logic to parse 'Addresses' from watcher deltas response and 'servers' list from the Login response. It seems beta10 renames cause divergence in the parameter names in these responses adding to complexity when parsing such responses. |
|
