Handle unused update_token's from replaces that get out of order

Safe2COVIDApp / bct-server

Bluetooth Contact Tracing for Covid19 - server

5 stars 1 forks source link

Handle unused update_token's from replaces that get out of order #80

Closed mitra42 closed 4 years ago

mitra42 commented 4 years ago

This is an obscure one ...

Client A sends status to Server 1
Client B sends update to Server 2
- it cant update a record that it doesnt have - its current saved in unused_update_tokens
Server 1 sends update (with original data points) to Server 2
- Server 2 should now see these data points, check against unused_update_tokens and update them.

jmday commented 4 years ago

This may overlap with the partial period contagious update issue discussed here (https://docs.google.com/document/d/1_uBrn07sA1khIhWcn4d4qao4SopWX_UAIuOE6yCIV4o/edit?disco=AAAAGdSjpTo).

mitra42 commented 4 years ago

That's pretty much the only issue left on the spec doc, pending disussion, but I dont' think its related to this point which is about how we handle a valid update when we are out of sync.