Open quity opened 5 months ago
If a path is a/b/c/name[key1=val1][key2=val2] for a gRPC GET request, the order of keys(alphabetical order) here in response should be maintained by client or server ?
Notification[0]: timestamp : 662426695970000000 prefix : – Update[000] : Path : "a" "b" "c" "name[key1=val1][key2=val2]"
as mentioned in spec - If multiple keys exist for a particular element, they MUST be specified sorted alphabetically by the key name.
This should be implemented at the server side for both Subscribe and Get in my view.
Subscribe
Get
Thanks @robshakir .
If a path is a/b/c/name[key1=val1][key2=val2] for a gRPC GET request, the order of keys(alphabetical order) here in response should be maintained by client or server ?
AsyncGet(GetResponse) =>
Notification[0]: timestamp : 662426695970000000 prefix : – Update[000] : Path : "a" "b" "c" "name[key1=val1][key2=val2]"