ISSUE-82: "Repeated" vs. "Asynchronous" updates

"Repeated" vs. "Asynchronous" updates

Raised by:
Allan Thomson
Opened on:
"This suggests a periodic update rather than what I think it is intended to suggest is asynchronous updates. It is not clear from the document when and what causes an asynchronous location update to occur. It is movement? Time? Suggest that you change "repeated position updates" to "asynchronous updates" and clarify what triggers the updates to be sent."

Related Actions Items:
No related actions
Related emails:
No related emails

Related notes:

The spec says: "In step 5.2.2 of the watch process, the successCallback is only invoked when a new position is obtained and this position differs signifficantly from the previously reported position. The definition of what consitutes a significant difference is left to the implementation. Furthermore, in steps 5.2.2 and 5.2.3, implementations may impose limitations on the frequency of callbacks so as to avoid inadvertently consuming a disproportionate amount of resources."

Lars Erik Bolstad, 4 Nov 2010, 10:55:59

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 82.html,v 1.1 2017/05/30 09:54:32 carine Exp $