RFC: How to decide which backend(s) to use

[Jussi Kukkonen]

keith preston wrote:
> This is a really difficult question.   One that I didn't know how to do.
> Originally, I had planned on accuracy as the defining point.    Each
> backend
> would signal a master process about it's accuracy and when it got more
> accurate.   From this the clients would chnge over to the more accurate
> backends.
>
> I thought this would suffice, but the civic location idea does bring up
> problems.   What if different backends implement different methods?   I
> still vote for allowing more control from the programmers, but maybe
> providing examples on how to change between providers and such.
> 

Backends offering different functionality is not the only problem. GPS
is a great example of the many problems that are going to pop up:
 * It's often an external device and the battery may be dead
 * the gps device may not be connected just now (out of bluetooth range)
 * if the device is indoors, there's no fix

I agree with you and Andrew that the problem is not trivial, but I'm
guessing the situations I listed are _very common_ and I think that we
should provide an automatic "backend-switcher" if it's possible. Some
applications will naturally want to select backends on their own, and
that's fine too.


I'll think this through, and get back if/when I have something more
concrete.

-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/20070620/3b95453d/attachment.pgp