DOCSLIB.ORG

Geolocation in the Browser from Google Gears to Geolocation Sensors

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Geolocation in the Browser from Google Gears to Geolocation Sensors Geolocation in the Browser From Google Gears to Geolocation Sensors Thomas Steiner Anssi Kostiainen Marijn Kruisselbrink Google LLC Intel Corporation Google LLC 20354 Hamburg, Germany 02160 Espoo, Finland San Francisco, CA 94105, USA [email protected] [email protected] [email protected] ABSTRACT 1 HISTORY OF BROWSER GEOLOCATION Geolocation is arguably one of the most powerful capabilities of Geolocation has been available to developers implicitly through smartphones and a lot of attention has been paid to native applica- the mapping of Internet Protocol (ip) addresses or address blocks tions that make use of it. The discontinued Google Gears plugin was to known locations. There are numerous paid subscription and one of the rst approaches to access exact location data on the Web free geolocation databases with varying claims of accuracy that as well, apart from server-side coarse location lookups based on In- range from country level to state or city level, sometimes including ternet Protocol (ip) addresses; and the plugin led directly to the now zip/post code level. A popular free way to obtain ip-based location widely implemented Geolocation api. The World Wide Web Con- data was through Google’s ajax api Loader library [2], which pro- sortium (w3c) Geolocation api specication denes a standard for vided an approximate, region-level estimate of a user’s location accessing location services in the browser via JavaScript. For a long through its google.loader.ClientLocation property. This api time, developers have also demanded more advanced features like did not require users to install any client-side software. Implicit background geolocation tracking and geofencing. The w3c Geolo- geolocation access is not subject of the paper, however, we list it cation and the Devices and Sensors Working Groups, as well as the for the sake of completeness and because it still plays an important Web Incubator Community Group (wicg), have addressed these de- role today, for example, for ip-based regional content blocking. mands with the no longer maintained Geofencing api specication for the former, and—with now (early 2019) resumed eorts—the 1.1 Google Gears Geolocation api in-ight Geolocation Sensors specication for the latter two groups. More accurate location data is available through Wi-Fi access point This paper rst provides an in-depth overview of the historical or cell tower data, as well as through Global Positioning Service development of geolocation in the browser and motivates privacy (gps) data. This data is accessible to native applications, however, decisions that were made at the time, and then gives an outlook initially, not via Web apis. The Google Gears browser plugin [9] on current and future eorts, challenges, and use cases from both for the rst time exposed exact device-based geolocation data a technology as well as from a privacy angle. to the browser. Its Geolocation api had two JavaScript methods: getCurrentPosition() made a single, one-o attempt to get a po- CCS CONCEPTS sition x, while watchPosition() watched the user’s position over • Information systems → Web applications; • Security and time, and provided an update whenever the position changed. Both privacy → Browser security. methods allowed the developer to congure which sources of lo- cation information would be used. As a simple way to get an ap- KEYWORDS proximate position x with low cost in terms of both network and battery resources, Gears also kept track of the best position x ob- Geolocation; Geofencing; Geotracking; Permissions; Privacy tained from these calls and made it available as the lastPosition property. To a contemporary JavaScript developer who may have ACM Reference Format: never used the plugin, the code in Listing 1 still looks very familiar, Thomas Steiner, Anssi Kostiainen, and Marijn Kruisselbrink. 2019. Geoloca- even more than ten years later. tion in the Browser: From Google Gears to Geolocation Sensors. In Com- panion Proceedings of the 2019 World Wide Web Conference (WWW ’19 Companion), May 13–17, 2019, San Francisco, CA, USA. ACM, New York, NY, var geo= google.gears.factory USA, 6 pages. https://doi.org/10.1145/3308560.3316538 .create( 'beta.geolocation '); function updatePosition(position){ alert( 'Current lat/lon is: ' + position.latitude+ ',' + position.longitude); } This paper is published under the Creative Commons Attribution-NonCommercial- function handleError(positionError){ NoDerivs 4.0 International (CC-BY-NC-ND 4.0) license. Authors reserve their rights to alert( 'Attempt to get location failed: ' + disseminate the work on their personal and corporate Web sites with the appropriate positionError.message); attribution. } WWW ’19 Companion, May 13–17, 2019, San Francisco, CA, USA © 2019 IW3C2 (International World Wide Web Conference Committee), published geo.getCurrentPosition(updatePosition, handleError); under Creative Commons CC-BY-NC-ND 4.0 License. ACM ISBN 978-1-4503-6675-5/19/05. Listing 1: Google Gears api (2008) https://doi.org/10.1145/3308560.3316538 From the start, user privacy was a major concern, and the plugin of the device. If the attempt is successful, the successCallback authors wrote in the Wiki [10]: must be invoked with a new Position object, reecting the current “It must be clear to users when an application is using location of the device. If the attempt fails, the errorCallback must the Geolocation api. We could implement one or both be invoked with a new PositionError object, reecting the reason of the following ui elements: for the failure. The watchPosition() method returns an identier (1) A separate dialog from the Gears security dialog that uniquely identies a watch operation and then asynchronously to enable the Geolocation api. If the general-purpose starts that watch operation. This operation must rst attempt to dialog gave access to position data, it would be easy obtain the current location of the device. Similar to the “one-shot” for users to forget they allowed access to Gears, or request, if the attempt is successful, the successCallback must to fail to realize enabling Gears also exposes their be invoked with a new Position object, reecting the current position data. location of the device, else, it must fail as described before. The (2) Some persistent ui that indicates the Geolocation watch operation then must continue to monitor the position of api is being used. For example, there could be a bar the device and invoke the appropriate callback every time this across the bottom of the browser with an icon of position changes. The watch operation must continue until the a globe or map. Perhaps this ui should be ‘active’ clearWatch() method is called with the corresponding identier, somehow, indicating that something is happening, so which immediately stops the watch operation identied by the that the user cannot forget it is being used.” identier. Listing 2 shows all methods in operation (see Listing 1 for comparison). This api is almost universally supported in browsers, In the end, they decided on approach (1), which is still how loca- Figure 1 shows the support situation at the time of writing. tion access is granted today, despite dierent underlying mechanics. The similarity of the code in Listing 1 with code one would write today is no surprise. Gears implemented the at the time current function showMap(pos){ // Showa map centered at editor’s draft of the w3c Geolocation specication, which some of //(pos.coords.latitude, pos.coords.longitude) the authors have helped to dene in collaboration with Microsoft, } Mozilla, and others. The goal for Gears was to advance browser function scrollMap(pos){ capabilities and eventually make itself a relict of time, which is // Scrolls the map so that it is centered at what has happened. //(pos.coords.latitude, pos.coords.longitude) } 1.2 Mozilla Geode function handleError(error){ // Handles the error gracefully. Mozilla Geode [1] was an experimental add-on that appeared slightly } after Gears to explore geolocation in Firefox 3 ahead of the im- plementation of the nal api in a future product release. Geode // One-shot position request navigator.geolocation.getCurrentPosition(showMap, provided an early realization of the w3c Geolocation specica- handleError); tion [14] so that developers could begin experimenting with en- // Request repeated updates abling location-aware experiences. It included a single experimental var watchId= navigator.geolocation.watchPosition( proprietary geolocation service provider called Skyhook to map scrollMap, handleError); Wi-Fi signals to locations, so that any computer with Wi-Fi could function clearPositionWatch(){ get accurate positioning data. An interesting historical fact is that // Cancel the updates when the user clicksa button the ultimate plan for Firefox was that service providers and geoloca- navigator.geolocation.clearWatch(watchId); tion methods would be pluggable [1] to provide users with as many } choices and privacy options as possible, which has not happened. Listing 2: Geolocation api 1.3 w3c Geolocation api The w3c Geolocation api specication [14] denes a high-level interface to location information associated only with the device 1.4 w3c Geofencing api hosting the implementation, such as latitude and longitude. The api The w3c Geofencing api [12] specication dened an api that itself is agnostic of the underlying location information sources, and should let Web applications set up geographic boundaries around no guarantee is given that it returns the device’s actual location. The specic
Load more

Recommended publications
  • Effects and Opportunities of Native Code Extensions For
    Effects and Opportunities of Native Code Extensions for Computationally Demanding Web Applications DISSERTATION zur Erlangung des akademischen Grades Dr. Phil. im Fach Bibliotheks- und Informationswissenschaft eingereicht an der Philosophischen Fakultät I Humboldt-Universität zu Berlin von Dipl. Inform. Dennis Jarosch Präsident der Humboldt-Universität zu Berlin: Prof. Dr. Jan-Hendrik Olbertz Dekan der Philosophischen Fakultät I: Prof. Michael Seadle, Ph.D. Gutachter: 1. Prof. Dr. Robert Funk 2. Prof. Michael Seadle, Ph.D. eingereicht am: 28.10.2011 Tag der mündlichen Prüfung: 16.12.2011 Abstract The World Wide Web is amidst a transition from interactive websites to web applications. An increasing number of users perform their daily computing tasks entirely within the web browser — turning the Web into an important platform for application development. The Web as a platform, however, lacks the computational performance of native applications. This problem has motivated the inception of Microsoft Xax and Google Native Client (NaCl), two independent projects that fa- cilitate the development of native web applications. Native web applications allow the extension of conventional web applications with compiled native code, while maintaining operating system portability. This dissertation determines the bene- fits and drawbacks of native web applications. It also addresses the question how the performance of JavaScript web applications compares to that of native appli- cations and native web applications. Four application benchmarks are introduced that focus on different performance aspects: number crunching (serial and parallel), 3D graphics performance, and data processing. A performance analysis is under- taken in order to determine and compare the performance characteristics of native C applications, JavaScript web applications, and NaCl native web applications.
    [Show full text]
  • HTML5 and the Open Web Platform
    HTML5 and the Open Web Platform Stuttgart 28 May 2013 Dave Raggett <[email protected]> The Open Web Platform What is the W3C? ● International community where Members, a full-time staff and the public collaborate to develop Web standards ● Led by Web inventor Tim Berners-Lee and CEO Jeff Jaffe ● Hosted by MIT, ERCIM, Keio and Beihang ● Community Groups open to all at no fee ● Business Groups get more staff support ● Technical Working Groups ● Develop specs into W3C Recommendations ● Participants from W3C Members and invited experts ● W3C Patent process for royalty free specifications 3 Who's involved ● W3C has 377 Members as of 11 May 2013 ● To name just a few ● ACCESS, Adobe, Akamai, Apple, Baidu, BBC, Blackberry (RIM), BT, Canon, Deutsche Telekom, eBay, Facebook, France Telecom, Fujitsu, Google, Hitachi, HP, Huawei, IBM, Intel, LG, Microsoft, Mozilla, NASA, NEC, NTT DoCoMo, Nuance, Opera Software, Oracle, Panasonic, Samsung, Siemens, Sony, Telefonica, Tencent, Vodafone, Yandex, … ● Full list at ● http://www.w3.org/Consortium/Member/List 4 The Open Web Platform 5 Open Web Platform ● Communicate with HTTP, Web Sockets, XML and JSON ● Markup with HTML5 ● Style sheets with CSS ● Rich graphics ● JPEG, PNG, GIF ● Canvas and SVG ● Audio and Video ● Scripting with JavaScript ● Expanding range of APIs ● Designed for the World's languages ● Accessibility with support for assistive technology 6 Hosted and Packaged Apps ● Hosted Web apps can be directly loaded from a website ● Packaged Web apps can be locally installed on a device and run without the need for access to a web server ● Zipped file containing all the necessary resources ● Manifest file with app meta-data – Old work on XML based manifests (Web Widgets) – New work on JSON based manifests ● http://w3c.github.io/manifest/ ● Pointer to app's cache manifest ● List of required features and permissions needed to run correctly ● Runtime and security model for web apps ● Privileged apps must be signed by installation origin's private key 7 HTML5 Markup ● Extensive range of features ● Structural, e.g.
    [Show full text]
  • Platform Independent Web Application Modeling and Development with Netsilon Pierre-Alain Muller, Philippe Studer, Frédéric Fondement, Jean Bézivin
    Platform independent Web application modeling and development with Netsilon Pierre-Alain Muller, Philippe Studer, Frédéric Fondement, Jean Bézivin To cite this version: Pierre-Alain Muller, Philippe Studer, Frédéric Fondement, Jean Bézivin. Platform independent Web application modeling and development with Netsilon. Software and Systems Modeling, Springer Ver- lag, 2005, 4 (4), pp.424-442. 10.1007/s10270-005-0091-4. inria-00120216 HAL Id: inria-00120216 https://hal.inria.fr/inria-00120216 Submitted on 21 Feb 2007 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Platform Independent Web Application Modeling and Development with Netsilon PIERRE-ALAIN MULLER INRIA Rennes Campus de Beaulieu, Avenue du Général Leclerc, 35042 Rennes, France pa.muller@ uha.fr PHILIPPE STUDER ESSAIM/MIPS, Université de Haute-Alsace, 12 rue des Frères Lumière, 68093 Mulhouse, France ph.studer@ uha.fr FREDERIC FONDEMENT EPFL / IC / UP-LGL, INJ œ Station 14, CH-1015 Lausanne EPFL, Switzerland frederic.fondement@ epfl.ch JEAN BEZIVIN ATLAS Group, INRIA & LINA, Université de Nantes, 2, rue de la Houssinière, BP 92208, 44322 Nantes, France jean.bezivin@ lina.univ-nantes.fr Abstract. This paper discusses platform independent Web application modeling and development in the context of model-driven engineering.
    [Show full text]
  • Introducing 2D Game Engine Development with Javascript
    CHAPTER 1 Introducing 2D Game Engine Development with JavaScript Video games are complex, interactive, multimedia software systems. These systems must, in real time, process player input, simulate the interactions of semi-autonomous objects, and generate high-fidelity graphics and audio outputs, all while trying to engage the players. Attempts at building video games can quickly be overwhelmed by the need to be well versed in software development as well as in how to create appealing player experiences. The first challenge can be alleviated with a software library, or game engine, that contains a coherent collection of utilities and objects designed specifically for developing video games. The player engagement goal is typically achieved through careful gameplay design and fine-tuning throughout the video game development process. This book is about the design and development of a game engine; it will focus on implementing and hiding the mundane operations and supporting complex simulations. Through the projects in this book, you will build a practical game engine for developing video games that are accessible across the Internet. A game engine relieves the game developers from simple routine tasks such as decoding specific key presses on the keyboard, designing complex algorithms for common operations such as mimicking shadows in a 2D world, and understanding nuances in implementations such as enforcing accuracy tolerance of a physics simulation. Commercial and well-established game engines such as Unity, Unreal Engine, and Panda3D present their systems through a graphical user interface (GUI). Not only does the friendly GUI simplify some of the tedious processes of game design such as creating and placing objects in a level, but more importantly, it ensures that these game engines are accessible to creative designers with diverse backgrounds who may find software development specifics distracting.
    [Show full text]
  • Seamless Offloading of Web App Computations from Mobile Device to Edge Clouds Via HTML5 Web Worker Migration
    Seamless Offloading of Web App Computations From Mobile Device to Edge Clouds via HTML5 Web Worker Migration Hyuk Jin Jeong Seoul National University SoCC 2019 Virtual Machine & Optimization Laboratory Department of Electrical and Computer Engineering Seoul National University Computation Offloading Mobile clients have limited hardware resources Require computation offloading to servers E.g., cloud gaming or cloud ML services for mobile Traditional cloud servers are located far from clients Suffer from high latency 60~70 ms (RTT from our lab to the closest Google Cloud DC) Latency<50 ms is preferred for time-critical games Cloud data center End device [Kjetil Raaen, NIK 2014] 2 Virtual Machine & Optimization Laboratory Edge Cloud Edge servers are located at the edge of the network Provide ultra low (~a few ms) latency Central Clouds Mobile WiFi APs Small cells Edge Device Cloud Clouds What if a user moves? 3 Virtual Machine & Optimization Laboratory A Major Issue: User Mobility How to seamlessly provide a service when a user moves to a different server? Resume the service at the new server What if execution state (e.g., game data) remains on the previous server? This is a challenging problem Edge computing community has struggled to solve it • VM Handoff [Ha et al. SEC’ 17], Container Migration [Lele Ma et al. SEC’ 17], Serverless Edge Computing [Claudio Cicconetti et al. PerCom’ 19] We propose a new approach for web apps based on app migration techniques 4 Virtual Machine & Optimization Laboratory Outline Motivation Proposed system WebAssembly
    [Show full text]
  • The Viability of the Web Browser As a Computer Music Platform
    Lonce Wyse and Srikumar Subramanian The Viability of the Web Communications and New Media Department National University of Singapore Blk AS6, #03-41 Browser as a Computer 11 Computing Drive Singapore 117416 Music Platform [email protected] [email protected] Abstract: The computer music community has historically pushed the boundaries of technologies for music-making, using and developing cutting-edge computing, communication, and interfaces in a wide variety of creative practices to meet exacting standards of quality. Several separate systems and protocols have been developed to serve this community, such as Max/MSP and Pd for synthesis and teaching, JackTrip for networked audio, MIDI/OSC for communication, as well as Max/MSP and TouchOSC for interface design, to name a few. With the still-nascent Web Audio API standard and related technologies, we are now, more than ever, seeing an increase in these capabilities and their integration in a single ubiquitous platform: the Web browser. In this article, we examine the suitability of the Web browser as a computer music platform in critical aspects of audio synthesis, timing, I/O, and communication. We focus on the new Web Audio API and situate it in the context of associated technologies to understand how well they together can be expected to meet the musical, computational, and development needs of the computer music community. We identify timing and extensibility as two key areas that still need work in order to meet those needs. To date, despite the work of a few intrepid musical Why would musicians care about working in explorers, the Web browser platform has not been the browser, a platform not specifically designed widely considered as a viable platform for the de- for computer music? Max/MSP is an example of a velopment of computer music.
    [Show full text]
  • Introduction to Google Gears
    Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, Google Google Gears Dion Almaer code.google.com ajaxian.com Dion Almaer — Google Gears Slide 1 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, Google Offline Web via Open Web • Why just solve this problem for Google? • Why not solve it for others? • Solution: Make it open source with a liberal license • New BSD Dion Almaer — Google Gears Slide 2 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, Google Why? “How often are you on a plane?” • Reliability • 1% of downtime can hurt at the wrong time • Performance • Local acceleration • Convenience • Not having to find a connection • You are offline more than you think! Dion Almaer — Google Gears Slide 3 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, Google What is the philosophy? •One application, one URL •Seamless transitions between online and offline •Ability to use local data, even when online •Available to all users on all platforms •... and a pony Dion Almaer — Google Gears Slide 4 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, Google What is the philosophy? Browser plugin: IE, Firefox, Safari (almost!) Dion Almaer — Google Gears Slide 5 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, Google What is the philosophy? Dion Almaer — Google Gears Slide 6 Colorado Software Summit: October 21 – 26, 2007 © Copyright 2007, Google What is the philosophy? Do for offline what XMLHttpRequest did for web apps Ajax Libraries Gears Libraries Dojo,
    [Show full text]
  • Learning HTML5 Game Programming Addison-Wesley Learning Series
    Learning HTML5 Game Programming Addison-Wesley Learning Series Visit informit.com/learningseries for a complete list of available publications. The Addison-Wesley Learning Series is a collection of hands-on programming guides that help you quickly learn a new technology or language so you can apply what you’ve learned right away. Each title comes with sample code for the application or applications built in the text. This code is fully annotated and can be reused in your own projects with no strings attached. Many chapters end with a series of exercises to encourage you to reexamine what you have just learned, and to tweak or adjust the code as a way of learning. Titles in this series take a simple approach: they get you going right away and leave you with the ability to walk off and build your own application and apply the language or technology to whatever you are working on. Learning HTML5 Game Programming A Hands-on Guide to Building Online Games Using Canvas, SVG, and WebGL James L. Williams Upper Saddle River, NJ • Boston • Indianapolis • San Francisco New York • Toronto • Montreal • London • Munich • Paris • Madrid Cape Town • Sydney • Tokyo • Singapore • Mexico City Many of the designations used by manufacturers and sellers to distinguish their products Associate are claimed as trademarks. Where those designations appear in this book, and the publish- Publisher er was aware of a trademark claim, the designations have been printed with initial capital Mark Taub letters or in all capitals. Senior Acquisitions The author and publisher have taken care in the preparation of this book, but make no Editor expressed or implied warranty of any kind and assume no responsibility for errors or omis- Trina MacDonald sions.
    [Show full text]
  • Advanced NFV Features Applied to Multimedia Real-Time Communications Use Case
    Advanced NFV Features Applied to Multimedia Real-Time Communications Use Case Ana Pol ∗, Anton Roman ∗, Panagiotis Trakadas†, Panagiotis Karkazis†, Evgenia Kapassa‡, Marios Touloupou‡, Dimosthenis Kyriazis‡, Juan L. de la Cruz§, Pol Alemany§, Ricard Vilalta§, Raul Munoz§ ∗Quobis, O Porrino, Spain, Email: [ana.pol,anton.roman]@quobis.com †Synelixis Solutions S.A. 157, Perissou, str., 14343, Athens, Greece, Email: [ptrak,pkarkazis]@synelixis.com ‡Department of Digital Systems, University of Piraeus, Piraeus, Greece, Email: [ekapassa, mtouloup,dimos]@unipi.gr §CTTC, Castelldefels, Spain, Email:[jdelacruz,palemany,rvilalta,rmunoz]@cttc.es Abstract — Real-time communications are services with very application service on top of the SONATA (powered by demanding requirements in terms of reliability and Quality of 5GTANGO) service platform. Service (QoS) that is not easy to be reached. 5G technologies provide tools and techniques that promise to overcome the The remaining of the paper is organized as follows. Section current shortcomings and thus give the opportunity to service II presents the state of the art of this work, while Section III providers to offer better services to the end users. This paper introduces the overall SONATA (powered by 5GTANGO) aims at describing how an existing real-time communications Service Platform. Section IV describe in detail then enhanced service can leverage the innovative features offered by the proposed features, specially focusing on the recently new- SONATA Service Platform (SP), such as network slicing, added features such as QoS and multi-WIM support. This automated monitoring management and Service Level section describes also the principles of SONATA (powered Agreement (SLA) enforcement, to meet the challenging requirements of the service.
    [Show full text]
  • Will HTML 5 Restandardize the Web?
    TECHNOLOGY NEWS Will HTML 5 Restandardize the Web? Steven J. Vaughan-Nichols The World Wide Web Consortium is developing HTML 5 as a stan- dard that provides Web users and developers with enhanced func- tionality without using the proprietary technologies that have become popular in recent years. n theory, the Web is a resource enhanced functionality without using “Microsoft is investing heavily in that is widely and uniformly proprietary technologies. the W3C HTML 5 effort, working with usable across platforms. As Indeed, pointed out Google our competitors and the Web commu- such, many of the Web’s researcher Ian Hickson, one of the nity at large. We want to implement key technologies and archi- W3C’s HTML 5 editors, “One of our ratified, thoroughly tested, and stable Itectural elements are open and goals is to move the Web away from standards that can help Web interop- platform-independent. proprietary technologies.” erability,” said Paul Cotton, cochair of However, some vendors have The as-yet-unapproved standard the W3C HTML Working Group and developed their own technologies takes HTML from simply describing Microsoft’s group manager for Web that provide more functionality than the basics of a text-based Web to creat- services standards and partners in Web standards—such as the ability to ing and presenting animations, audio, the company’s Interoperability Strat- build rich Internet applications. mathematical equations, typefaces, egy Team. Adobe System’s Flash, Apple’s and video, as well as providing offline At the same time though, Web QuickTime, and Microsoft’s Silverlight functionality. It also enables geoloca- companies say their proprietary tech- are examples of such proprietary tion, a rich text-editing model, and nologies are already up and running, formats.
    [Show full text]
  • Document Object Model
    Document Object Model Copyright © 1999 - 2020 Ellis Horowitz DOM 1 What is DOM • The Document Object Model (DOM) is a programming interface for XML documents. – It defines the way an XML document can be accessed and manipulated – this includes HTML documents • The XML DOM is designed to be used with any programming language and any operating system. • The DOM represents an XML file as a tree – The documentElement is the top-level of the tree. This element has one or many childNodes that represent the branches of the tree. Copyright © 1999 - 2020 Ellis Horowitz DOM 2 Version History • DOM Level 1 concentrates on HTML and XML document models. It contains functionality for document navigation and manipulation. See: – http://www.w3.org/DOM/ • DOM Level 2 adds a stylesheet object model to DOM Level 1, defines functionality for manipulating the style information attached to a document, and defines an event model and provides support for XML namespaces. The DOM Level 2 specification is a set of 6 released W3C Recommendations, see: – https://www.w3.org/DOM/DOMTR#dom2 • DOM Level 3 consists of 3 different specifications (Recommendations) – DOM Level 3 Core, Load and Save, Validation, http://www.w3.org/TR/DOM-Level-3/ • DOM Level 4 (aka DOM4) consists of 1 specification (Recommendation) – W3C DOM4, http://www.w3.org/TR/domcore/ • Consolidates previous specifications, and moves some to HTML5 • See All DOM Technical Reports at: – https://www.w3.org/DOM/DOMTR • Now DOM specification is DOM Living Standard (WHATWG), see: – https://dom.spec.whatwg.org
    [Show full text]
  • Silo: Exploiting Javascript and DOM Storage for Faster Page Loads
    Silo: Exploiting JavaScript and DOM Storage for Faster Page Loads James Mickens Microsoft Research [email protected] Abstract fast-loading pages result in happier users, longer visit times, and higher revenues for page owners. For exam- A modern web page contains many objects, and fetch- ple, when the e-commerce site Shopzilla reduced its av- ing these objects requires many network round trips— erage load time from 5 seconds to 1.5 seconds, it boosted establishing each HTTP connection requires a TCP page views by 25% and revenue by 10% [4]. Faster loads handshake, and each HTTP request/response pair re- also lead to more advertising impact, since Google’s Ad- quires at least one round trip. To decrease a page’s load Words system preferentially displays ads whose target time, designers try to minimize the number of HTTP re- pages load quickly [9]. Search engines also make load- quests needed to fetch the constituent objects. A com- ing speed a factor in their page rankings [22]. mon strategy is to inline the page’s JavaScript and CSS Given all of this, web designers have accumulated a files instead of using external links (and thus separate series of techniques for decreasing load times. Souder’s HTTP fetches). Unfortunately, browsers only cache ex- influential book High Performance Web Sites lists 14 of ternally named objects, so inlining trades fewer HTTP these techniques [23], with the most important one be- requests now for greater bandwidth consumption later if ing to minimize the number of HTTP requests needed a user revisits a page and must refetch uncacheable files.
    [Show full text]