sirikata/sirikata — Issue #472: Need to track latest request handled by LocationService so HostedObjects can determine whether a given request was handled
Author: ewencp
Created: 2012-01-17 21:48:38+00:00
State: open

Currently we just try using timestamps to resolve conflicts between requested locations and reported locations. However, with latency and the fact that timestamps get pulled up to the current time, this policy doesn't actually work. Instead, we should be tracking requested locations and have the last handled request reported with location updates for objects so they can determine whether the request was handled (they should use the reported value) or not handled (they can continue to use the requested value, optimistically).

This bug is causing bad behavior for avatars when there's non-trivial latency between the object host and the space server since the requested location information is quickly overwritten with now out-of-date information, causing weird camera rotation/tracking and animation inconsistencies.