Generally described, computing devices and communication networks can be utilized to exchange information. In a common application, a computing device can request content from another computing device via the communication network. For example, a user at a personal computing device can utilize a software application process, typically referred to as a browser, to request a Web page from a server computing device via the Internet. In such embodiments, the user computing device can be referred to as a client computing device, and the server computing device can be referred to as a content provider.
With reference to an illustrative example, a requested Web page may be associated with a number of additional resources, including static content and dynamic content. For dynamic content, such as video images or video streaming, client computing devices receiving a continuous transmission of content from a content provider require consistent processing of the incoming dynamic content, such as decoding encoded content. From the perspective of a user utilizing a client computing device, a user experience can be defined in terms of the performance and latencies associated with obtaining a Web page, processing embedded resource identifiers, and rendering content on the client computing device. Latencies and performance limitations of any of the above processes may diminish the user experience. Additionally, latencies and inefficiencies may be especially apparent on computing devices such as netbooks, tablets, smartphones, and the like, which may have limited resources in terms of processing power, memory, or network connectivity.
The foregoing aspects and many of the attendant advantages will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
Generally described, aspects of the present disclosure are directed to the processing and display of Web content by a client computing device. More specifically, aspects of the present disclosure are directed to systems, methods, and computer-readable media related to remote processing of dynamic content associated with Web pages. Additionally, aspects of the present disclosure further relate to synchronization of data transmissions between a client computing device having a browser application and a network-based computing device having a browser application in order to render dynamic content on the client computing device.
With reference to an illustrative example, a user may cause a client computing device to load and execute a software browser application (henceforth referred to as a “browser”) for accessing content provided by one or more content providers. Illustratively, the accessed content may include a collection of one or more network resources (e.g., a Web page) and embedded resources corresponding to content considered to be static in nature such as images, text, and the like. The embedded resources can also include content considered to be dynamic in nature, such as video, audio, executable code, and compilable scripts. Scripts may illustratively be written in JavaScript™, ECMAScript™, Jscript™, ActionScript™, Dart™, VBScript™, or other scripting languages. The dynamic content can be transmitted to the browser application as a series of one or more transmission for storage and processing on the client computing device. Alternatively, the dynamic content can be transmitted as a series of continuous transmissions, often referred to as a content stream or streaming, that can be processed by the browser without requiring (or allowing) the content to be stored on the client computing device.
Subsequent to the browser being loaded, a user or automated browser process may cause the client computing device to transmit a request to access content from a content provider (“content request”). The browse session request may include information identifying one or more sources for the requested content. The identifiers can be in the form of network addresses of network resources, such as a Web site or other network accessible piece of content. For example, the user may select or enter a URL (e.g., http://www.example.com) into a browser window, causing the client computing device to transmit a request for a new browse session to the content provider, including the selected URL. Illustratively, the content request from the client computing device may not be transmitted directly to a respective content provider. Rather, the content request from client computing device may be transmitted to a browser application instantiated on a network-based server and configured to work in conjunction with the client-based browser application. In this embodiment, the server-based browser application obtains the content request and transmits a content request to the content provider from the server-based browser application based on the content request transmitted by the client-based browser.
In an illustrative embodiment, the server-based browser may receive content from the content provider in response to the request. The browser may include, for example, a layout engine or rendering engine that parses the received content to identify and process various elements, such as HTML layout information, CSS information, embedded objects including static content and dynamic content. More specifically, in accordance with aspects of the present disclosure, the server-based browser processes at least a portion of the received content to generate at least the dynamic content that is to be displayed with the requested resource. Additionally, the server-based browser application then further processes the requested content, including the dynamic content to generate vector-based rendering instructions. Illustratively, the vector-based rendering instructions correspond to a set of instructions that cause a browser application utilizing a graphics library to be able to render content on a display. For example, the vector-based rendering instructions can correspond to a vector of instructions utilizing the Skia Graphics Engine and associated graphics library. In such embodiments, the vector based instructions distill complicated dynamic content, such as graphics, into simple components, such as lines, squares, circles, gradients, and the like.
After processing the received content, the server-based browser transmits the vector-based processing instructions (e.g., the encoded content) to the client-based browser. Utilizing a corresponding graphics engine and graphics library, the client-based browser processes that vector-based instructions (e.g., decodes) to render content for display to a user associated with the client computing device.
In some embodiments, the content provider can continue to transmit requested content to the server-based browser application, such as in the case of dynamic content that is transmitted via a series of transmissions or dynamic content that is continuously streamed from the content provider (or other designated source). In other embodiments, the execution of instructions, such as scripts included in the original content, can cause a change in the content to be displayed on the browser application. In accordance with aspects of the present application, as dynamic content changes, or causes changes, to the content to be displayed, the server-based browser application against processes the content to generate updated vector-based rendering instructions corresponding to the updated content. Additionally, the server-based browser application can further compare the vector-based rendering instructions corresponding to the updated content to identify a set of differences in the vector-based rendering instructions. The server-based browser application can then limit at least a portion of the subsequent transmissions to the client-based browser application to the differences in vector-based rendering instructions to limit the data required to generate the updated content on the client computing device. In some cases, the server-based browser may choose to transmit the full set of vector-based rendering instructions to the client-based browser, such as in a periodic refresh of content, if the differences exceed a threshold, based on a request from the client-based browser, based on instructions from the content provider and the like.
Although various aspects of the embodiments described in the present disclosure will focus, for purposes of illustration, on the remote processing of dynamic content associated with a web browser, one skilled in the art will appreciate that the techniques disclosed herein may be applied to any number of software processes or applications. Further, although various aspects of the disclosure will be described with regard to illustrative examples and embodiments, one skilled in the art will appreciate that the disclosed embodiments and examples should not be construed as limiting
In an illustrative embodiment, the client 102 includes necessary hardware and software components for establishing communications over the communications network 140. For example, the client 102 may be equipped with a network interface 110 that facilitates communications via the network 140. The network 140 can be a publicly accessible network of linked networks, possibly operated by various distinct parties, such as the Internet. In other embodiments, the network 140 may include a private network, local area network (“LAN”), wide area network (“WAN”), cable network, satellite network, wireless telecommunications network, any other medium of computer data transfer, or some combination thereof.
The client 102 may also have varied local computing resources such as a central processing unit 104, data store 106, input/output devices 108, a bus interface 130, memory 112, and so forth. One skilled in the art will appreciate that the client 102 may have more or fewer components than those depicted in illustrative
Similar to the client computing device 102, the networked computing device 152 illustratively includes necessary hardware and software components for establishing communications over the communications network 140, such as a central processing unit 154, data store 156, memory 162, bus interface 180, and so forth. The network computing device 152 may optionally be equipped with input/output devices 158 for direct user interaction, and may be equipped with a network interface 160 that facilitates communications on the network 140. One skilled in the art will appreciate that the networked computing device 152 may have more or fewer components than those depicted in illustrative
The networked content servers 150 may illustratively be web servers configured to respond to requests for content via the communication network 140. In some aspects, the network content servers 150 provide dynamic content to the server-based browser 164 for transmission to a client browser 114. Further, the modules or components illustrated in
With reference now to
At (2), a server-based browser application 164 receives the content request from the client 102. At (3), the server-based browser application 165 generates an independent request to a corresponding networked content server 150. The independent request is based, at least in part on the content request from the client computing device 102, but is generated and transmitted from the server-based browser application 164.
Turning now to
At (3), the server-based browser application 164, such as via a graphics engine component, generates vector-based processing instructions corresponding to the processed requested resource. As previously described, illustratively the server-based browser application 164 includes a graphics engine that utilizes a library of graphics components, such as lines, circles, squares, etc., to distill graphic objects into simple components. At (4), the server-based browser application, via the graphics engine, then generates a set of instructions for utilizing the simple components of the graphics library to create the graphic objects. The set of instructions can be organized into a vector of processing instructions. For purposes of the present application the generation of the vector of instructions can be considered the encoding of the graphic content. At (5), the server-based browser application transmits the encoded rendering instructions to the client computing device 102 in response to the content request. Illustratively, the server-based browser application 164 would not need to transmit the underlying resource or the processed content along with the encoded rendering instructions. As such, the amount of data transmitted by the server-based browser application 164 to the client computing device 102 would be reduced.
With continued reference to
Turning now to
At (2), the server-based browser application 164, such as via a graphics engine component, generates vector-based processing instructions corresponding to the processed updated requested resource. As previously described, illustratively the server-based browser application 164 includes a graphics engine that utilizes a library of graphics components to distill graphic objects into simple components. At (3), the server-based browser application, via the graphics engine, then generates a set of instructions for utilizing the simple components of the graphics library to create the graphic objects. The set of instructions can be organized into a vector of processing instructions.
At (4), the server-based browser application 164 compares the generated vector-based processing instructions for the updated content with vector-based processing instructions previously transmitted to the client computing device 102. In one embodiment, the server-based browser application 164 compares the generated vector-based processing instructions with the most recently transmitted vector-based processing instructions. In other embodiments, the server-based browser application 164 may utilize one or more reference set of vector-based processing instructions that may serve as the comparison source even if subsequent vector-based processing instructions have been transmitted or additional differences have been previously identified.
Illustratively, the server-based browser application 164 utilizes the comparison between the vector-based processing instructions to identify differences in the vector-based processing instructions. At (5), the server-based browser application 164 encodes the identified vector-based processing instructions. In one embodiment, the server-based browser application 164 encodes the differences in manner that can be utilized by the client computing device 102 to update previously received vector-based processing instructions (including intervening updates) to update the vector-based processing instructions.
With continued reference to
Turning now to
At block 302, the server-based browser application 164 obtains a request for a network resource. As previously described, illustratively, the server-based browser application 164 obtains the content request from the client-based browser application 114. As described above, the content request can be in the form of a URL (or set of URLs) that can be resolved to identify one or more networked content providers 105. At block 304, the server-based browser application 164 processes the content request to transmit an independent request for content to the one or more networked content providers 150. In Some embodiments, the server-based browser application 164 may also supplement the received content request with additional information or may alternatively generate a content request that does not include the same information provided by the client-based browser application 114.
At block 306, the network-based browser application 164 receives the requested content from the networked content server 150. As previously discussed, the requested content can be in the form of a markup language, such as HTML, that can also include references to embedded content. Accordingly, at block 308, the server-based browser application 164 processes the returned content, which can include transmitted additional requests to one or more network content servers 150 for the embedded resources. Illustratively, the server-based browser application 164 processes the requested resources to be able to at least partially render content on a display screen.
At block 310, the server-based browser application 164, such as via a graphics engine component, generates vector-based processing instructions corresponding to the processed requested resource. As previously described, illustratively the server-based browser application 164 includes a graphics engine that utilizes a library of graphics components, such as lines, circles, squares, etc., to distill graphic objects into simple components. Illustratively, in the first instance of routine 300, the server-based browser application 164 may not have reference set of vector-based instructions in which to make a comparison. Accordingly, in this application, routine 300 may omit any comparison steps (blocks 312 and 314) and the full set of vector-based instructions will be encoded and transmitted as described below with regard to block 316.
In the alternative, routine 300 may be implemented in which there is a previously transmitted vector-based instructions or a reference set of vector-based instructions in which to make a comparison. In such embodiments, at block 312, the server-based browser application 164 compares the generated vector-based processing instructions for the updated content with vector-based processing instructions previously transmitted to the client computing device 102. In one embodiment, the server-based browser application 164 compares the generated vector-based processing instructions with the most recently transmitted vector-based processing instructions. In other embodiments, the server-based browser application 164 may utilize one or more reference set of vector-based processing instructions that may serve as the comparison source even if subsequent vector-based processing instructions have been transmitted or additional differences have been previously identified. Illustratively, the differences between the vector-based instructions can be characterized as temporal and spatial differences in accordance with how the vector-based rendering instructions are generated by the graphics engine.
At block 314, the server-based browser application 164 encodes the identified vector-based processing instructions. In one embodiment, the server-based browser application 164 encodes the differences in a manner that can be utilized by the client computing device 102 to update previously received vector-based processing instructions (including intervening updates) to update the vector-based processing instructions. At block 316, the server-based browser application transmits the encoded rendering instructions to the client computing device 102 in response to the content request. Illustratively, the server-based browser application 164 would not need to transmit the underlying resource or the processed content along with the encoded rendering instructions. As such, the amount of data transmitted by the server-based browser application 164 to the client computing device 102 would be reduced.
At decision block 318, a test is conducted to determine whether there are additional vector based rendering instructions. Illustratively, routine 300 may be implemented continuously in embodiments in which the dynamic content is being continuously modified or semi-continuously being modified, such as streaming application. In such embodiments, the server-based browser application 164 may be continuously generating vector-based processing instructions. Accordingly, the routine 300 returns to block 312. Alternatively, if no further vector-based processing instructions are available or if the time between receipt of additional vector-based processing instructions exceeds a threshold, routine 300 terminates at block 320.
Turning now to
At block 402, the client-based browser application 114 obtains encoded instructions. Illustratively, the encoded instructions are responsive to a content request transmitted by the client-based browser application 114 to the network-based browser application 164 in the manner described above. At block 404, the client-based browser application 114, via a compatible graphics engine, would decode the vector of instructions to identify a set of instructions used to generate the content.
At block 406, the client-based browser application 114 determines which vector-based instructions to execute locally to present the content, such as via an accessible display screen. Illustratively, in the first iteration of routine 400, the client-based browser application 114 will utilize the full set of vector-based rendering instructions to render the content for display. In subsequent iterations of routine 400 and as described above, the encoded rendering instructions include only the differential (spatial and temporal) from a reference set of vector instructions, such as a previously transmitted full or partial set of vector-based rendering instructions. In these embodiments, the client-based browser application utilizes the decoded spatial and temporal differences to update the vector-based rendering instructions.
At block 408, the client-based browser application 114 causes execution of the identified vector-based instructions to render the content for presentation. Illustratively, the client-based browser application 114 can utilize a graphics engine and associated libraries to execute the vector based instructions.
At decision block 408, a test is conducted to determine whether additional encoded instructions have been received.
Depending on the embodiment, certain acts, events, or functions of any of the methods described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithm). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
The various illustrative logical blocks, modules and method elements described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
The various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor can be a microprocessor, but in the alternative, the processor can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The elements of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM or any other form of computer-readable storage medium known in the art. A storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.
Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” “involving” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some or all of the elements in the list.
Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y or at least one of Z to each be present.
Unless otherwise explicitly stated, articles such as “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B, and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.
While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain embodiments described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Number | Name | Date | Kind |
---|---|---|---|
4468751 | Plunkett, Jr. | Aug 1984 | A |
5828370 | Moeller | Oct 1998 | A |
6061798 | Coley et al. | May 2000 | A |
6460060 | Maddalozzo, Jr. et al. | Oct 2002 | B1 |
6657647 | Bright | Dec 2003 | B1 |
7191467 | Dujari et al. | Mar 2007 | B1 |
7231606 | Miller et al. | Jun 2007 | B2 |
7512932 | Davidov et al. | Mar 2009 | B2 |
7617458 | Wassom, Jr. et al. | Nov 2009 | B1 |
7627814 | Soldan et al. | Dec 2009 | B1 |
8285063 | Akenine-Möller et al. | Oct 2012 | B2 |
8453049 | Grieve et al. | May 2013 | B1 |
8510237 | Cascaval | Aug 2013 | B2 |
8555157 | Fu | Oct 2013 | B1 |
8677097 | Nemazie et al. | Mar 2014 | B1 |
8762878 | Weber et al. | Jun 2014 | B1 |
8799412 | Trahan et al. | Aug 2014 | B2 |
8893294 | Steele, III et al. | Nov 2014 | B1 |
9167054 | Trahan et al. | Oct 2015 | B2 |
9201850 | Buddhiraja et al. | Dec 2015 | B1 |
9288521 | Reynolds | Mar 2016 | B2 |
9292367 | Mickens | Mar 2016 | B2 |
9348936 | B'far et al. | May 2016 | B2 |
9383932 | Das Sharma | Jul 2016 | B2 |
9509783 | Hayden | Nov 2016 | B1 |
9749202 | Jain et al. | Aug 2017 | B1 |
9811321 | Karppanen | Nov 2017 | B1 |
9881096 | Warr et al. | Jan 2018 | B1 |
9888074 | Roy et al. | Feb 2018 | B1 |
10127210 | Karppanen | Nov 2018 | B1 |
10241983 | Derby et al. | Mar 2019 | B1 |
10296580 | Pulla et al. | May 2019 | B1 |
10341345 | Johansson et al. | Jul 2019 | B1 |
10348797 | Burgin et al. | Jul 2019 | B1 |
10372780 | Lepeska et al. | Aug 2019 | B1 |
20010042045 | Howard et al. | Nov 2001 | A1 |
20010043800 | Gotoh et al. | Nov 2001 | A1 |
20020009078 | Wilson et al. | Jan 2002 | A1 |
20020013833 | Wyatt et al. | Jan 2002 | A1 |
20020133627 | Maes | Sep 2002 | A1 |
20020147788 | Nguyen | Oct 2002 | A1 |
20030014478 | Noble | Jan 2003 | A1 |
20030055610 | Webber | Mar 2003 | A1 |
20040015476 | Twaddle | Jan 2004 | A1 |
20040230903 | Elza et al. | Nov 2004 | A1 |
20050108627 | Mireku | May 2005 | A1 |
20050149718 | Berlin et al. | Jul 2005 | A1 |
20050198365 | Wei | Sep 2005 | A1 |
20060005114 | Williamson et al. | Jan 2006 | A1 |
20060010150 | Shaath et al. | Jan 2006 | A1 |
20060136552 | Krane et al. | Jun 2006 | A1 |
20060168101 | Mikhailov et al. | Jul 2006 | A1 |
20060282795 | Clark et al. | Dec 2006 | A1 |
20070005622 | Fernandes et al. | Jan 2007 | A1 |
20070127440 | Narayanaswami et al. | Jun 2007 | A1 |
20070192329 | Croft et al. | Aug 2007 | A1 |
20080005686 | Singh | Jan 2008 | A1 |
20080139191 | Melnyk | Jun 2008 | A1 |
20080313206 | Kordun et al. | Dec 2008 | A1 |
20090046935 | Akenine-Möller et al. | Feb 2009 | A1 |
20090138937 | Erlingsson et al. | May 2009 | A1 |
20090168760 | Katis et al. | Jul 2009 | A1 |
20090202159 | Ström | Aug 2009 | A1 |
20090210631 | Bosworth et al. | Aug 2009 | A1 |
20090287559 | Chen et al. | Nov 2009 | A1 |
20090319776 | Burch et al. | Dec 2009 | A1 |
20100005053 | Estes | Jan 2010 | A1 |
20100070928 | Goodger et al. | Mar 2010 | A1 |
20100077444 | Forristal | Mar 2010 | A1 |
20100082747 | Yue et al. | Apr 2010 | A1 |
20100161587 | Sullivan | Jun 2010 | A1 |
20100180225 | Chiba et al. | Jul 2010 | A1 |
20100312858 | Mickens et al. | Dec 2010 | A1 |
20100313065 | Feeley et al. | Dec 2010 | A1 |
20100313189 | Beretta et al. | Dec 2010 | A1 |
20110015917 | Wang et al. | Jan 2011 | A1 |
20110082996 | Wester et al. | Apr 2011 | A1 |
20110145360 | Sheshagiri et al. | Jun 2011 | A1 |
20110176790 | Morris | Jul 2011 | A1 |
20110191677 | Morris | Aug 2011 | A1 |
20110225495 | Casalaina et al. | Sep 2011 | A1 |
20110252312 | Lemonik | Oct 2011 | A1 |
20110258532 | Ceze et al. | Oct 2011 | A1 |
20120066380 | Gao et al. | Mar 2012 | A1 |
20120066586 | Shemesh | Mar 2012 | A1 |
20120131485 | Svendsen et al. | May 2012 | A1 |
20120173966 | Powell et al. | Jul 2012 | A1 |
20120239598 | Cascaval et al. | Sep 2012 | A1 |
20120260157 | Zhu et al. | Oct 2012 | A1 |
20120330984 | Fablet | Dec 2012 | A1 |
20120331228 | Shatz | Dec 2012 | A1 |
20120331406 | Baird et al. | Dec 2012 | A1 |
20130007100 | Trahan et al. | Jan 2013 | A1 |
20130031459 | Khorashadi et al. | Jan 2013 | A1 |
20130058414 | Tsuru | Mar 2013 | A1 |
20130061293 | Mao | Mar 2013 | A1 |
20130067086 | Hershko et al. | Mar 2013 | A1 |
20130185650 | Gutowitz et al. | Jul 2013 | A1 |
20130205244 | Decker et al. | Aug 2013 | A1 |
20130246906 | Hamon | Sep 2013 | A1 |
20140026096 | Zhang et al. | Jan 2014 | A1 |
20140033019 | Zhang | Jan 2014 | A1 |
20140040139 | Brudnick et al. | Feb 2014 | A1 |
20140052702 | Fierro et al. | Feb 2014 | A1 |
20140053064 | Weber et al. | Feb 2014 | A1 |
20140109078 | Lang et al. | Apr 2014 | A1 |
20140126309 | Kelly et al. | May 2014 | A1 |
20140143651 | Klotzer et al. | May 2014 | A1 |
20140164960 | Kuo | Jun 2014 | A1 |
20140201809 | Choyi et al. | Jul 2014 | A1 |
20140215336 | Gärdenfors et al. | Jul 2014 | A1 |
20140281918 | Wei | Sep 2014 | A1 |
20140310608 | Snyder et al. | Oct 2014 | A1 |
20150026566 | Hui | Jan 2015 | A1 |
20150052596 | Ayanam | Feb 2015 | A1 |
20150089352 | Conboy et al. | Mar 2015 | A1 |
20150135061 | Palanichamy et al. | May 2015 | A1 |
20150161087 | Khoo | Jun 2015 | A1 |
20150205462 | Jitkoff et al. | Jul 2015 | A1 |
20150205761 | Shah | Jul 2015 | A1 |
20150269065 | Bourd et al. | Sep 2015 | A1 |
20150271188 | Call | Sep 2015 | A1 |
20150279463 | Berke | Oct 2015 | A1 |
20160057220 | Gibbs et al. | Feb 2016 | A1 |
20160142914 | He et al. | May 2016 | A1 |
20160188279 | Rajamani et al. | Jun 2016 | A1 |
20160205088 | Sreesha et al. | Jul 2016 | A1 |
20160299764 | Chakra et al. | Oct 2016 | A1 |
20160313896 | Liang et al. | Oct 2016 | A1 |
20170302976 | Puttagunta et al. | Oct 2017 | A1 |
20170329554 | Voigt et al. | Nov 2017 | A1 |
20180004856 | Levi et al. | Jan 2018 | A1 |
20190079906 | Karppanen | Mar 2019 | A1 |
Entry |
---|
Allen, M., HydrateJS by nanodeath, Dec. 14, 2013, http://nanodeath.gihub.io/HydrateJS/. |
Gross, R., and A. Wightman, MarioNet Split Web Browser, p. 1, Jan. 1999, https://en.wikipedia.org/wiki/MarioNet_split_web_browser. |
Hickson, I., Ed., Web Storage, W3C Working Draft, Oct. 29, 2009, pp. 11-18, http://www.w3.org/TR/2009/WD-webstorage-20091029/. |
Jquery API Documentation, Feb. 10, 2010, Version 1.2, p. 162, http://api.jquery.com/serialize/. |
Wellons, C., Precise JavaScript Serialization With ResurrectJS, Mar. 28, 2013, http://nullprogram.com/blog/2013/03/28/. |
Garsiel, T., and P. Irish, How Browsers Work: Behind the Scenes of Modern Web Browsers, http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/, published Aug. 5, 2011, pp. 1-62, retrieved Jun. 25, 2015. |
Hayden, A.L., Customized Browser Images, U.S. Appl. No. 13/359,290, filed Jan. 26, 2012. |
Jain, A.S., and D.L.R. Batni, Remote Session Preview Management, U.S. Appl. No. 14/180,245, filed Feb. 13, 2014. |