Digest attributes should be sent as a map
Reported by Ben Hood | October 20th, 2011 @ 07:15 PM | in 1.0 (closed)
Currently we have the (potentially premature) optimization that partition attributes are sent out as a list of the values. The convention is that these values should be sent in the lexicographical order of the names these values pertain to. Whilst being terser, this approach is prone to buggy participant implementations and in some cases the false ordering could go unnoticed for quite some time. Hence we should reverse this optimization and make participants send a map of attributes to be as explicit as possible.
Comments and changes to this ticket
-
Ben Hood November 1st, 2011 @ 02:39 PM
- Milestone set to “1.0”
- Milestone order changed from “138” to “0”
-
Paul Jones November 6th, 2011 @ 10:40 PM
- Assigned user set to “Ben Hood”
- State changed from “new” to “resolved”
- Milestone order changed from “3” to “0”
The format of the events was changed in #409, so I believe that this has now been resolved.
-
-
Paul Jones November 7th, 2011 @ 12:54 AM
The outbound participant requests are done as keyed query parameters, and the ScanResultEntry is a map. Is there anywhere else I'm missing?
-
Ben Hood November 7th, 2011 @ 11:43 AM
- State changed from “resolved” to “closed”
Yes, my memory is hazy - I think we might have said previously that for infrequent scan operations, the optimization is pointless anyway, but that the more frequent change events need the terser format. So if that was the case, then the only place the sequence was being passed was with the ChangeEvents -> closing this ticket.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.
Ben Hood