(no subject)

Hi Alec,

On Fri, Aug 29, 2008 at 6:04 AM, Alec Berntson
<alecb@windows.microsoft.com> wrote:
> Andrei,
>
>   After looking at the geolocation API spec more closely, I was hoping we
> could clarify the watchPosition() process. Does the 2 step flow below imply
> the watchPosition() first fires a 'single shot' request to get the current
> location, and then listens to updates?

Yes, the idea is that watchPosition() must tell the caller what is the
user's current position and then must notify the caller again every
time the user's position changes (what constitutes a change is not
currently specified and is left to the implementation to decide).

>
> The watchPosition() takes one, two or three arguments. When called, it must
> immediately return and then asynchronously start a watch process defined as
> the following set of steps:
>
> Acquire a new Position object. If successful, invoke the associated
> successCallback with a Position object as an argument. If the attempt fails,
> and the method was invoked with a non-null errorCallback argument, this
> method must invoke the errorCallback with a PositionError object as an
> argument.

This effectively says that the implementation must first call back
with the current position.

> Acquire a new Position object and invoke the appropriate callback every time
> the implementation determines that the position of the hosting device has
> changed.
>

This says that the implementation must call back every time the
position changes.

First of all, do you agree with this behavior? If so, I can try to
re-word this paragraph to make it more clear. Suggestions are always
welcome :)


Thanks,
Andrei

Received on Friday, 29 August 2008 06:33:59 UTC