[whatwg] Geolocation in the browser

[Ryan Sarver]

Since I am a newbie in this regard, what do you think about passing something like User-Geolocation in the header of the request so that the server has access to the information as well?

Obviously this is subject to some settings and privacy control on the UA, but it would allow the server to process the initial page content based on the user's current location.

Thoughts?

-----Original Message-----
From: David Latapie [mailto:david at empyree.org] 
Sent: Wednesday, February 21, 2007 3:56 PM
To: Ryan Sarver
Cc: whatwg at lists.whatwg.org
Subject: Re: [whatwg] Geolocation in the browser

On Wed, 21 Feb 2007 15:31:11 -0500, Ryan Sarver wrote:
>  - would it make sense to also expose it in the request headers? This
> way the server receives it on the first request as opposed to through
> the client after the initial page request
> 
>  
> 
> User-Geolocation: 43.338018, -71.817930

Surely you've heard of ICBM
(<meta name="ICBM" content="46.025507, 14.300186" />)

Could elaborate on what you like and dislike on this?
-- 
</david_latapie>             U+0F00
http://blog.empyree.org/en (English)
http://blog.empyree.org/fr (Français)
http://blog.empyree.org/sl (Slovensko)