Content deleted Content added
Citation bot (talk | contribs) Removed parameters. | You can use this bot yourself. Report bugs here. | Activated by Neko-chan | Category:Application programming interfaces | via #UCB_Category |
|||
Line 20:
==Implementation==
Though the implementation is not specified, W3C Geolocation API is built on extant technologies, and is heavily influenced by Google Gears Geolocation API. Example: Firefox's Geolocation implementation<ref>{{cite web |url=https://www.mozilla.org/en-US/firefox/geolocation/ |title=Location-Aware Browsing |work=Mozilla Firefox |publisher=Mozilla}}</ref> uses Google's network ___location provider.<ref>{{cite web |url=https://code.google.com/apis/gears/geolocation_network_protocol.html |title=Geolocation API Network Protocol: Gears API |work=Google Code
Google Gears Geolocation works by sending a set of parameters that could give a hint as to where the user's physical ___location is to a network ___location provider server, which is by default the one provided by Google (code.l.google.com).<ref>{{cite web |url=http://webscannotes.com/?page_id=425 |title=WebScanNotes.com: W3C Geolocation API |work=WebScanNotes.com}}</ref> Some of the parameters are lists of sensed mobile cell towers and Wi-Fi networks, all with sensed signal strengths. These parameters are encapsulated into a JavaScript Object Notation ([[JSON]]) message and sent to the network ___location provider via HTTP POST. Based on these parameters, the network ___location provider can calculate the ___location. Common uses for this ___location information include enforcing access controls, localizing and customizing content, analyzing traffic, [[contextual advertising]] and preventing identity theft.<ref>{{cite web |ssrn=1622411 |title=Personal Jurisdiction, Internet Commerce, and Privacy: The Pervasive Legal Consequences of Modern Geolocation Technologies |first=Kevin F. |last=King |date=8 June 2010}}</ref>
| |||