new method/signal suggestions

[Jussi Kukkonen]

Talking to myself here, sorry...

Jussi Kukkonen wrote:
> 2. last_position idea (you mentioned something like this already)
 ...
>  One option is to have a last_position-method in the API, and an
> accompanying last_position_error, which could rise over time. Clients
> that are interested in just getting an approximate position (that might
> be a bit old) should always use this method.
>  Another option would be adding parameter to current_position that
> allows sending "old data" (and make position_error behave as described
> previously).

Keith, your "timestamp" addition into current_position implies that
current_position should send older data in some situations... Do you
have a vision of how this should work?

-jussi

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 307 bytes
Desc: OpenPGP digital signature
Url : http://lists.freedesktop.org/archives/geoclue/attachments/20070811/c0893d0a/attachment.pgp