W3C home > Mailing lists > Public > public-geolocation@w3.org > October 2008

RE: PositionOptions.timeout == 0

From: Thomson, Martin <Martin.Thomson@andrew.com>
Date: Wed, 29 Oct 2008 23:21:29 -0500
Message-ID: <E51D5B15BFDEFD448F90BDD17D41CFF10507337B@AHQEX1.andrew.com>
To: "Greg Bolsinga" <bolsinga@apple.com>
Cc: <public-geolocation@w3.org>
I'd expect that a default value would be used by the browser.  I made the suggestion that a default, or recommended, value be put in the specification [1] to set expectations.  Picking a good value is hard though, the methods available and associated times vary greatly.

For now, I'd expect that you will have to make a call on your own default.  I'd also want to consider how this might be changed and by whom.

Ta,
Martin

[1] http://lists.w3.org/Archives/Public/public-geolocation/2008Oct/0044.html


> -----Original Message-----
> From: Greg Bolsinga [mailto:bolsinga@apple.com]
> Sent: Thursday, 30 October 2008 3:17 PM
> To: Thomson, Martin
> Cc: public-geolocation@w3.org
> Subject: Re: PositionOptions.timeout == 0
> 
> What if  the JavaScript object used for PositionOptions doesn't have
> the timeout property? Does that mean it is '0'? If so, the error may
> occur very quickly, if the user has passed the PositionErrorCallback.
> If not they will fail quickly and not know why. If they do not pass a
> PostionOptions, the property is zero, isn't it?
> 
> Thanks for helping me clarify,
> -- Greg
> 
> On Oct 29, 2008, at 8:39 PM, Thomson, Martin wrote:
> 
> > The only way I can see that this wouldn't return an error is if
> > caching were used by the browser implementation.  If adequate data
> > was available already, a successful answer could be returned
> > immediately.
> >
> > Based on discussions on caching of in recent emails, the browser
> > should not cache location information.  That's the purpose of the
> > lastPosition attribute.  Each call to getCurrentPosition would
> > result in generation of data.  My experience is that this is never
> > instantaneous.  Therefore, this call would result in an error
> > indication.
> >
> > On the other hand, watchPosition is a different creature - it is
> > conceivable that when a change in location is detected, the process
> > that causes this to be detected also produces a location.  In that
> > case, a timeout of 0 could work.
> >
> > I don't think that this is the right approach, and I've already said
> > as much, but it is consistent with what is currently documented.
> >
> > Cheers,
> > Martin
> >
> >> -----Original Message-----
> >> From: public-geolocation-request@w3.org [mailto:public-geolocation-
> >> request@w3.org] On Behalf Of Greg Bolsinga
> >> Sent: Thursday, 30 October 2008 2:30 PM
> >> To: public-geolocation@w3.org
> >> Subject: PositionOptions.timeout == 0
> >>
> >>
> >> What would it mean if a user set this?
> >>
> >> Would an error occur right away?
> >>
> >> Thanks,
> >> -- Greg
> >>
> >>
> >
> > ---------------------------------------------------------------------
> ---------------------------
> > This message is for the designated recipient only and may
> > contain privileged, proprietary, or otherwise private information.
> > If you have received it in error, please notify the sender
> > immediately and delete the original.  Any unauthorized use of
> > this email is prohibited.
> > ---------------------------------------------------------------------
> ---------------------------
> > [mf2]
> 

------------------------------------------------------------------------------------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information.  
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
------------------------------------------------------------------------------------------------
[mf2]
Received on Thursday, 30 October 2008 04:22:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:52 UTC