Patent Grant
9330188
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 computing device, such as a personal computing device, can utilize a software browser application, typically referred to as a “browser,” to request a Web page from a server computing device via the Internet. In such embodiments, the requesting 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, or original content, may be associated with a number of additional resources, such as images or videos, that are to be displayed with the Web page. In one specific embodiment, the additional resources of the Web page are identified by a number of embedded resource identifiers, such as uniform resource locators (“URLs”). In turn, software on the client computing devices, such as a browser, typically processes embedded resource identifiers to generate requests for the content. Accordingly, in order to satisfy a content request, one or more content providers will generally provide client computing devices data associated with the Web page as well as the data associated with the embedded resources.
Once the client computing device obtains the Web page and associated additional resources, the content may be processed in a number of stages by the software browser application or other client computing device interface. For example, and with reference to the above illustration, the software browser application may parse the Web page to process various HTML layout information and references to associated resources, may identify and process Cascading Style Sheets (“CSS”) information, may process and instantiate various Javascript code associated with the Web page, may construct a native object model to represent one or more components of the Web page, and may calculate various layout and display properties of the processed content for presentation to a user.
In some scenarios, computing device users can share accessed individual network resources (e.g., Web sites) with other users by transmitting one or more network identifiers, such as URLs, corresponding to the access network resources. More specifically, users wishing to share more than one accessed network resources are limited to transmitting a set of network identifiers. However, a recipient of a set of network resources that have to be accessed separately cannot directly recreate a browsing session.
The foregoing aspects and many of the attendant advantages of this invention 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, the present disclosure is directed to the generation and management of a remote application session and browse content between client computing devices and content providers in conjunction with a network computing provider. Specifically, aspects of the disclosure will be described with regard to the generation and management of shared session information between the client computing device and the network computing provider. Illustratively, the shared session information corresponds to a specification of a set of network resources accessed by the client computing device and the preservation of browse session information associated with the previous access of the set of network resources.
In one aspect, a session may be defined on a time basis such that all network resources access by a browser application over a defined time period may be considered to be part of the same session. In another aspect, a session may be defined in terms of activities, such as the opening or closing of a browser software application, such that all network resources accessed between a starting activity and ending activity may be considered to be part of the same session. In still a further aspect, a session may be defined in terms of user selectable criteria, such as the manual selection of a collection of accessed network resources to form a session. Additionally, one skilled in the relevant art will appreciate that additional or alternative definitions of a session may also be incorporated and that two or more definitions of a session may be incorporated. Illustratively, the shared session information is utilized by one or more client computing devices to access and recreate a browse session corresponding to the set of network resources.
Other aspects of the present disclosure will be described with regard to the generation and management of shared session information between client computing devices and a shared session manager component. In this embodiment, multiple client computing devices can publish or subscribe to the shared session manager component for purposes of access shared session information. For example, one or more individuals/organizations may publish shared session information for purposes of allowing one or more client computing devices to access the shared session information.
Although aspects of the embodiments described in the disclosure will focus, for the purpose of illustration, on the management of shared session information between a client computing device and either a network computing component or a shared session manager component, one skilled in the art will appreciate that the techniques disclosed herein may be applied to any number of software processes or applications, and may be applied to preserving content of any number of different document and data types. 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.
With reference to an illustrative example, a user may cause a client computing device to load a software browser application (henceforth referred to as a “browser”) for accessing content provided by one or more content providers. In one embodiment, the browser may have a content display area or pane for displaying the accessed network content in addition to one or more local interface components, such as toolbars, menus, buttons, or other user interface controls. Local interface components may be managed and controlled by the software browser application or any other process executing or implemented locally at the client computing device. Illustratively, managing user interface controls locally may allow for a responsive user interface, as interactions by the user are processed locally 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 by establishing a browse session with a network computing provider across a private or public network. The browse session request may include information identifying one or more sources for the requested 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 network computing provider, including the selected URL. The browse session request may further include identification information, such as information identifying the user, browser, or client computing device.
Responsive to the browse session request received from the client computing device, the network computing provider may instantiate or cause to have instantiated one or more computing components associated with the network computing provider that will host a browser software application. For example, the network computing provider can instantiate, or cause to have instantiated, an instance of a virtual machine that includes a software browser application capable of requesting resources from a communication network. Using the instantiated network computing components, the network computing provider may request the identified network resource(s) from one or more content providers, a content delivery network, or a local or associated storage component or data store. For example, the browser software application on the instantiated network computing component can process a primary network resource and then generate additional content requests for content identified in one or more embedded resource identifiers (e.g. pictures, video files, etc.). Illustratively, in the case of other non-browser applications, network resources, or content, may include any file type or format known in the art and supported by the specific software application. The “requested content” corresponds to content that will be provided to the client computing device as responsive to the current browse session request.
In an illustrative embodiment, the network computing provider or client computing device may process the identification information included in the browse session request to initialize shared session information that will capture and maintain information related to a browse session related to the access of a set of network resources. Illustratively, the shared session information may be maintained by a network computing provider hosting the one or more computing components, a shared session manager component that functions as a service provider or a combination thereof.
Having obtained the requested content (e.g., the requested network resource and embedded resources), the network computing provider may identify a client remote session browse configuration specifying a remote session communication protocol for use in transmitting the requested content, user interaction data, intermediate processing results, and other information between the browser being executed on the client computing device and the browser being executed at the instantiated network computing component on the computing and storage provider. Additionally, the information exchanged between the browser on the instantiated network computing component and the browser on the client computing device can be generally referred to as “browser session information.” The shared session information is updated with each network resource accessed by the client computing device and the browser session information associated with such access.
In addition to specifying a remote session communication protocol for transmitting information between the client computing device and the instantiated network computing component, in one embodiment, the identified client remote session browse configuration may specify that one or more processing actions to be performed on the requested content are to be performed at the network computing provider rather than, or in addition to, at the client computing device. A Web page, for example, may be parsed and processed to process various HTML layout information and references to associated resources or embedded content, such as CSS style sheets and Javascript, as well as embedded content objects such as images, video, audio, etc. Each object or piece of code may be parsed and processed before a representative object model corresponding to the web page may be constructed and processed further for layout and display. The client remote session browse configuration may identify which of these actions are to be performed at a network computing component and which are to be performed at the client computing device.
At a subsequent point in time, one or more client computing devices may access the shared session information. For example, a user may publish shared session information corresponding to a celebrity browser session. In another example, a user may be forwarded a shared session identifier that provides access to shared session information or may utilize shared session information as an archive of a previous browser session. Illustratively, accessing the shared session information can result in a client computing device accessing a currently established browser session being hosted on a network computing provider, creating new browsing sessions on a network computing provider or individually accessing the network resources directly from the content provider or accessing an archival copy of the network resources as they were accessed a specified time (such as when the shared session information was created, modified or updated).
The networked computing environment 100 can also include a content provider 104 in communication with the one or more client computing devices 102 or other service providers (e.g., CDN service provider 106, network computing provider 107, etc.) via the communication network 108. The content provider 104 illustrated in
With continued reference to
In an illustrative embodiment, the DNS component 118, 124, 130 and resource cache component 120, 126, 132 are considered to be logically grouped, regardless of whether the components, or portions of the components, are physically separate. Additionally, although the CDN POPs 116, 122, 128 are illustrated in
With further continued reference to
In an illustrative embodiment, NCCs 136, 144, 150 and the storage components 140, 146, 152 are considered to be logically grouped, regardless of whether the components, or portions of the components, are physically separate. For example, a network computing provider 107 may maintain separate POPs for providing the NCC and the storage components. Additionally, although the NCC POPs 134, 142, 148 are illustrated in
In some embodiments, the networked computing environment 100 can also include one or more shared session manager components 154 for creating and managing shared session information. Illustratively, the shared session manager component 154 can function as a network-based service communicating with client computing devices 102 or network computing providers 107 via application program interfaces (“APIs”). The shared session manager component 154 can be associated with one or more data stores for maintain shared session information. In one embodiment, the shared session manager component can correspond to a stand-alone service for processing browser session information from client computing devices 102. Although only a single shared session manager component 154 has been illustrated in
With reference now to
With reference to
Subsequent to the receipt of the browse session request, the network computing provider 107 may select an associated network computing component (hereinafter “NCC”) point of presence (hereinafter “POP”) such as NCC POP 142 to service the browse session request. The selection of the NCC POP may determine the processing and network resources available to the instantiated virtual machine. The selection of processing and network resources and the provisioning of software at the NCC POP instance may be done, at least in part, in order to optimize communication with content providers 104 and client computing devices 102. Once the network computing provider 107 has selected a particular NCC POP 142, the network computing provider 107 can initiate a new (or continued) browse session request.
With reference to
Subsequent to initializing a new browse session instance, NCC POP 142 may provide a request for a network resource to a content provider 104 based on a network address included in the browse session request. For example, a browse session request may include a URL for a Web page, such as “http://www.example.com/default.htm.” NCC POP 142 may resolve the URL to an IP address through a DNS resolver associated with the network computing provider (not shown), and may request the Web page from the content provider 104 at the resolved IP address. In various embodiments, a network resource may be retrieved from any combination of content providers, content delivery network (hereinafter “CDN”) servers, or data stores associated with the network computing provider 107. For example, the network computing provider may check if a resource is stored in a local cache or in another server or service provider associated with the network computing provider 107. If a network resource is stored in a local or associated location, the NCC POP 142 may retrieve the network resource from the local or associated location rather than from the third party content provider 104 or CDN service provider 106. Illustratively, the NCC POP 142 may provide requests for any number of network resources as included in the browse session request, and may obtain these network resources from any number of different sources, sequentially or in parallel.
As illustrated in
Subsequent to obtaining the requested network resource from the content provider 104 (or other source designated by the content provider), the NCC POP 142 may process the network resource to extract embedded resource identifiers and gather information for determination of a client remote session browse configuration. For example, a network resource such as a Web page may include embedded CSS style information and Javascript as well as embedded resource identifiers to additional resources such as text, images, video, audio, animation, executable code, and other HTML, CSS, and Javascript files. In the process of extracting the embedded resource identifiers, the NCC POP 142 may gather information about the processed network resources for later use in the determination of a client remote session browse configuration as discussed below with reference to
With reference to
For example, the network computing provider may check if an embedded resource is stored in a local cache or in another data store or service provider associated with the network computing provider 107. If an embedded resource is stored in a local or associated location, the NCC POP 142 may retrieve the embedded resource from the local or associated location rather than the third party content provider or CDN. Illustratively, the NCC POP 142 may provide requests for any number of embedded resources referenced by a network resource, and may obtain these embedded resources from any number of different sources, sequentially or in parallel. Subsequent to obtaining the requested resources, the NCC POP 142 may process the resources and requested content to determine a client remote session browse configuration for the processing and communication of content to the client computing device 102. The NCC POP 142 may further identify references in any of the retrieved content and determine any additional resource requests for retrieval and caching at the offline browse storage component.
With reference to
As illustrated in
The selected NCC POP 142 may provide an initial processing result to the client computing device 102 over the network 108. The initial processing result may correspond to requested network content, such as a Web page, along with associated embedded resources processed by the NCC POP 142 in accordance with a selected client remote session browse configuration as described in
Subsequent to receiving an initial processing result, the remote session browse configuration information, and the allocation of processes, the client computing device 102 may perform any remaining processing actions on the initial processing result as required by the selected client remote session browse configuration, and may display the fully processed content in a content display area of a browser. The client computing device 102 may process any local user interactions with local interface components or content elements locally, and may provide user interactions requiring remote processing to the network computing provider 107. The network computing provider 107 may provide updated processing results to the client computing device in response to changes to the content or remote user interaction data from the client computing device.
With reference to
The additional browse session request may be generated by a client computing device 102 in response to a user opening up a new browser window with a new content display area, opening a new content display area in an existing browser window (e.g., opening a new tab in a browser), requesting new network content in an existing content display area (e.g., following a link to a new network resource, or entering a new network address into the browser), or any other user interaction. For example, a user browsing a first Web page corresponding to a first browse session instance may follow a link that opens a new tab or browser window to view a second Web page. In one embodiment, any required steps of obtaining and processing content associated with the second Web page may be performed by the currently instantiated network computing component in which the browser can handle the processing of both resource requests.
In another embodiment, the client computing device 102 request may be processed as a new browse session request to the network computing provider 107, including the network address of the second Web page. In this embodiment, the browser on the client computing device may not specifically request a separate browse session, and a user's interaction with the browser on the client computing device 102 may appear to be part of a same browsing session. As described above with regard to
Illustratively, the additional browse session request may include any number of pieces of data or information including, but not limited to, information associated with a user, information associated with the client computing device 102 (e.g., hardware or software information, a device physical or logical location, etc.), information associated with the network 108, user or browser preferences (e.g., a requested remote session browse protocol, a preference list, a decision tree, or other information), information associated with the network computing provider 107, information associated with one or more pieces of requested network content (e.g., the network address of a network resource), etc. Requested content may include any manner of digital content, including Web pages or other documents, text, images, video, audio, executable scripts or code, or any other type of digital resource.
Subsequent to the receipt of the browse session request, the network computing provider 107 may select an associated network computing component such as NCC POP 142 to service the browse session request. As discussed above with reference to
Illustratively, although the network computing provider 107 is depicted here, for purposes of illustration, as selecting NCC POP 142, the network computing provider 107 may select any extant NCC POP to service the browse session request. For example, a single client computing device 102 may simultaneously or sequentially provide three different browse session requests to the network computing provider 107 corresponding to different network resources. The network computing provider 107 may select different NCC POPs for each browse session request, the same NCC POP for all three browse session requests, or any combination thereof. As discussed above, the decision whether to select a different NCC POP than was utilized for a previous or simultaneous browse session request may be made on the basis of available system resources, randomly, or according to any other factor as discussed above and with regard to
With reference to
One of skill in the relevant art will appreciate that the subsystems shown here are depicted for the purpose of illustration, and are not intended to describe a necessary order or a definitive list of browser subsystems. Various browser software components may implement additional or fewer browser subsystems than are shown here, and may order the subsystems or corresponding processing actions in any number of different ways. Although the processing subsystems 900 depicted here for purposes of illustration are directed at the processing of Web pages or other Web content, one of skill in the relevant art will appreciate that the processing of other file types or network resources may be broken up in a similar manner. For example, one of skill in the relevant art will appreciate that similar schema may be developed for the processing of images, video, audio, database information, 3d design data, or any other file format or type of data known in the art. Similar schema may also be developed for any number of device operating system or software framework processing operations, such as scheduling, memory or file management, system resource management, process or service execution or management, etc. Further, although the HTML protocol and RDP remote session communication protocols are discussed herein for the purposes of example, one of skill in the relevant art will appreciate that a client or offline remote session browse configuration may implement any number of remote communication protocols for any number of specified processing actions, and that a client or offline remote session browse configuration may be formulated to perform any fraction or combination of the actions identified below at any combination of the client computing device 102 and network computing provider 107.
Illustratively, the first processing subsystem involved in the processing and display of network content is the networking subsystem 902. Illustratively, the networking subsystem 902 may be responsible for all communication between the browser and content provider, including local caching of Web content. The networking subsystem is generally limited by the performance of the user's network. A client or offline remote session browse configuration that splits processing actions at the networking subsystem 902 might include a client or offline remote session browse configuration utilizing an HTML remote session communication protocol, where one or more caching or resource retrieval actions were performed at the NCC POP, but parsing and processing of the content was performed at the client computing device.
As network resources such as HTML documents are downloaded from the server they may be passed to an HTML subsystem 904 which parses the document, initiates additional downloads in the networking subsystem, and creates a structural representation of the document. Modern browsers may also contain related subsystems which are used for XHTML, XML and SVG documents. A client or offline remote session browse configuration that splits processing actions at the HTML subsystem 904 might include a client or offline remote session browse configuration utilizing an HTML remote session communication protocol, where an initial HTML page is processed at the NCC POP in order to extract embedded resource identifiers, but additional parsing and processing of the content is performed at the client computing device. In another embodiment, a client or offline remote session browse configuration that splits processing actions at the HTML subsystem 904 might perform initial processing to create the structural representation of the HTML document, and provides a processing result including the structural representation and associated embedded resources.
When CSS is encountered, whether inside an HTML document or an embedded CSS document, it may be passed to a CSS subsystem 906 to parse the style information and create a structural representation that can be referenced later. Illustratively, a remote session browse configuration that splits processing actions at a CSS subsystem 906 may construct a processing result including the CSS structural representation and HTML structural representation, optionally including any associated embedded resources.
HTML documents often contain metadata, for example the information described in a document header or the attributes applied to an element. The collections subsystem 908 may be responsible for storing and accessing this metadata. A client or offline remote session browse configuration that splits processing actions at a collections subsystem 908 may construct a processing result including processed metadata along with any other structural representations discussed above, optionally including any associated embedded resources.
When Javascript is encountered, it may be passed directly to a JavaScript subsystem 910 responsible for executing the script. The JavaScript subsystem 910 has been examined fully over the years, and may be one of the most well known browser subsystems in the art. A client or offline remote session browse configuration that splits processing actions at a Javascript subsystem 910 may construct a processing result including an internal representation of one or more Javascript scripts, including, but not limited to, state data or a representation of the script in a native or intermediate form, as well as any other processed structures or data discussed above, optionally including any associated embedded resources.
Because many JavaScript engines are not directly integrated into the browser, there may be a communication layer including the marshalling subsystem 912 between the browser and the script engine. Passing information through this communication layer may generally be referred to as marshalling. A client or offline remote session browse configuration that splits processing actions at a marshalling subsystem 912 may construct a processing result including marshalling data as well as any other processed structures, scripts, or data discussed above, optionally including any associated embedded resources.
In some embodiments, JavaScript interacts with an underlying network resource such as a Web document through the Document Object Model APIs. These APIs may be provided through a native object model subsystem 914 that knows how to access and manipulate the document and is the primary interaction point between the script engine and the browser. Illustratively, a client or offline remote session browse configuration that splits processing actions at a native object model subsystem 914 may construct a processing result including native object model state data or API calls as well as any other processed structures, scripts, or data discussed above, optionally including any associated embedded resources.
Once the document is constructed, the browser may needs to apply style information before it can be displayed to the user. The formatting subsystem 916 takes the HTML document and applies styles. Illustratively, a client or offline remote session browse configuration that splits processing actions at a formatting subsystem 916 may construct a processing result including an HTML representation with applied styles, as well as any other processed state data, API calls, structures, scripts, or data discussed above, optionally including any associated embedded resources.
In one embodiment, CSS is a block based layout system. After the document is styled, the next step, at a block building subsystem 918, may be to construct rectangular blocks that will be displayed to the user. This process may determine things like the size of the blocks and may be tightly integrated with the next stage, layout. A client or offline remote session browse configuration that splits processing actions at a block building subsystem 918 may construct a processing result including block information, as well as any other processed state data, API calls, structures, scripts, or data discussed above, optionally including any associated embedded resources.
Subsequent to the browser styling the content and constructing the blocks, it may go through the process of laying out the content. The layout subsystem 920 is responsible for this algorithmically complex process. Illustratively, a client or offline remote session browse configuration that splits processing actions at a layout subsystem 920 may process the various state data, API calls, structures, scripts, or data discussed above to construct a processing result including layout information for the client computing device. Illustratively, an NCC POP may make use of various data or settings associated with the client computing device or browser (e.g., as provided in the initial browse session request) in order to generate a suitable layout for the client computing device. For example, a mobile device may provide a screen resolution and a display mode to the NCC POP. The NCC POP may base layout calculations on this screen resolution and display mode in order to generate a processing result corresponding to a content representation suitable for a browser running on the mobile device. Illustratively, in various embodiments, any other subsystem implemented by the NCC POP may make use of data associated with the client computing device or browser in generating a processing result for the client.
The final stage of the process may occur inside the display subsystem 922 where the final content is displayed to the user. This process is often referred to as drawing. A client or offline remote session browse configuration that splits processing actions at the networking subsystem 902 might include a client or offline remote session browse configuration utilizing an RDP remote session communication protocol, where nearly all processing is performed at the NCC POP, and a processing result including bitmap data and low level interface data are passed to the client computing device for display.
At block 1004, the shared session manager component 154 initializes shared session information. Illustratively, the initialization of shared session information can based on default criteria or user specified information, such as naming convention, storage location, access preferences, and the like. In another embodiment, the shared session manager component 154 can access previously existing shared session information. For example, the shared session manager component 154 can access shared session information previously created by the same individual or a different individual. In a further embodiment, the shared session manager component 154 can obtain shared session information as part of the request for the network resource submitted by the client computing device 102. The shared session manager component 154 can use the shared session information to add to the previously existing shared session information or to create new shared session information incorporating the additional information.
At block 1006, the shared session manager component 154 adds one or more network resources associated with the request for network resources to the initialized shared session information. Illustratively, the addition of network resources includes not only the identification of the requested network resource, but also browsing session information related to the browsing path (or other information). Illustratively, the browsing information can include information such as navigation path information, such as the order in which network resources were accessed. The browsing information can also include metadata provided during the browsing session, such as annotations, performance data or measurements, timing information, and the like.
At decision block 1008, a test is conducted to determine whether additional resources are to be added. In one embodiment, the shared manager component will maintain shared session information based on various criteria, such as time based criteria, a number of resources included in the shared session information (in terms of maximums or minimums), user actions (e.g., closing of a browser), and the like. If there are additional network resources, at block 1010, the shared session manager component 154 obtains the additional network resource requests and the routine 100 returns to block 1006 to add the additional requested resources to the shared session information.
Referring again to decision block 1008, once no additional resources exist or will be added to the shared session information, at block 1012, the shared session manager component 154 processes the shared session information. In one aspect, the shared session manager component 154 can apply create shared session identifiers based on various naming conventions. For example, the shared session manager component 154 can create readily discernable shared session identifiers based on the network resources associated with the shared session identifier. In another aspect, the shared session manager component 154 can process the resources identified in the shared session information to manage the network resources or browse session information included in the shared session information. For example, the shared session manager component 154 can filter duplicate entries, remove one or more network resources that have been identified in blacklist, and the like. In another example, the shared session manager component 154 can combine at least portions of two or more shared session information sets.
In still another aspect, the shared session manager component 154 can publish or otherwise transmit created shared session identifiers. For example, the shared session manager component 154 can facilitate the publication of shared session identifiers to social networking Web sites. In a further aspect, the shared session manager component 154 can facilitate the editing and verification of shared session information. An illustrative interface for editing shared session will be described with regard to
In still a further aspect, the shared session manager component 154 can configure how shared session information will be accessed or subsequently processed. Illustratively, in one embodiment, accessing shared session information can result in each client computing device 102 individually accessing the network resource at the time the shared session information is accessing. In another embodiment, accessing shared session information can result in each client computing device 102 accessing an ongoing or existing browser session information (e.g., a collaborative browser session). In still another embodiment, accessing shared session information can result in each client computing device 102 accessing archived versions of the network resource to recreate the network resources as they were accessed at the time the shared session information was generated or updated. At block 1014, the routine 1000 terminates.
Interactions with local interface components may be treated as local user interactions or remote user interactions depending on the processing required by the interaction and the client remote session browse configuration. For example, the selection of a preferences option in a browser menu may be handled entirely as a local user interaction by a browser. The processing required to display the menu, provide visual feedback regarding the selection, display the preferences window, and process the changes made to the browser preferences may be performed locally. As discussed above, processing user interactions locally may provide greater responsiveness at the browser as opposed to sending user interaction data to the NCC POP 142 for processing. As another example, when using a client remote session browse configuration that specifies extensive processing on the NCC POP 142 (e.g., a client remote session browse configuration using a remote session communication protocol such as RDP), the selection of a content refresh button in a browser toolbar may be handled both as a local user interaction and a remote user interaction. The limited processing required to provide interface feedback corresponding to the button selection may be handled at the client computing device 102 in order to provide the appearance of interface responsiveness, while the refresh command, which may require processing of the network content displayed in the content display area of the browser, may be sent as user interaction data to the NCC POP 142 for processing. The NCC POP 142 may then transmit updated processing results corresponding to the refreshed network content back to the client computing device 102 for display.
Illustratively, the browser 1100 may include one or more content display areas 1102 organized in content tabs 1108A-C. Illustratively, a content display area 1102 may display a representation of content corresponding to a processing result provided by an NCC POP 142 as the result of a live browsing session, or may display a representation of content corresponding to an offline content representation. Tabs 1108A-1108C also include controls 1110 A-1110C for allowing a user to designate which currently accessed network resource should be included in shared session information. Illustratively, a browser 1100 may include any number of other controls not shown herein, but associated with the viewing, processing, or maintenance of an offline content representation.
Browser interface 1200 can further include additional controls to facilitate the further processing of the shared session information. As also illustrated in
With continued reference to
Although the accessed shared session information is depicted in
While illustrative embodiments have been disclosed and discussed, one skilled in the relevant art will appreciate that additional or alternative embodiments may be implemented within the spirit and scope of the present invention. For example, the techniques described herein may be utilized, without departing from the scope of the present invention, to allow remote processing management in any number of other software applications and processes, including, but not limited to, image or video editing software, database software, office productivity software, 3d design software, audio and sound processing applications, etc. Additionally, although many embodiments have been indicated as illustrative, one skilled in the relevant art will appreciate that the illustrative embodiments do not need to be combined or implemented together. As such, some illustrative embodiments do not need to be utilized or implemented in accordance with the scope of variations to the present disclosure.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” 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 or steps. Thus, such conditional language is not generally intended to imply that features, elements or steps are in any way required for one or more embodiments, or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein, in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art. It will further be appreciated that the data or components described above may be stored on a computer-readable medium and loaded into memory of the computing device using a drive mechanism associated with a computer readable medium storing the computer executable components such as a CD-ROM, DVD-ROM, or network interface; further, the component or data can be included in a single device or distributed in any manner. Accordingly, general purpose computing devices may be configured to implement the processes, algorithms, and methodology of the present disclosure with the processing or execution of the various data or components described above.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5634064 | Warnock et al. | May 1997 | A |
| 5809250 | Kisor | Sep 1998 | A |
| 5872850 | Klein et al. | Feb 1999 | A |
| 5930752 | Kawaguchi et al. | Jul 1999 | A |
| 5961593 | Gabber et al. | Oct 1999 | A |
| 6049812 | Bertram et al. | Apr 2000 | A |
| 6084582 | Qureshi et al. | Jul 2000 | A |
| 6108637 | Blumenau | Aug 2000 | A |
| 6138156 | Fletcher et al. | Oct 2000 | A |
| 6144991 | England | Nov 2000 | A |
| 6182133 | Horvitz | Jan 2001 | B1 |
| 6195679 | Bauersfeld et al. | Feb 2001 | B1 |
| 6230266 | Perlman et al. | May 2001 | B1 |
| 6282542 | Carneal et al. | Aug 2001 | B1 |
| 6356934 | Delph | Mar 2002 | B1 |
| 6360366 | Heath | Mar 2002 | B1 |
| 6397253 | Quinlan et al. | May 2002 | B1 |
| 6411966 | Kwan et al. | Jun 2002 | B1 |
| 6430624 | Jamtgaard et al. | Aug 2002 | B1 |
| 6438597 | Mosberger et al. | Aug 2002 | B1 |
| 6513061 | Ebata et al. | Jan 2003 | B1 |
| 6549941 | Jaquith et al. | Apr 2003 | B1 |
| 6560620 | Ching | May 2003 | B1 |
| 6560705 | Perlman et al. | May 2003 | B1 |
| 6625624 | Chen et al. | Sep 2003 | B1 |
| 6633316 | Maddalozzo et al. | Oct 2003 | B1 |
| 6691106 | Sathyanarayan | Feb 2004 | B1 |
| 6704024 | Robotham et al. | Mar 2004 | B2 |
| 6704204 | Eskildsen et al. | Mar 2004 | B1 |
| 6725269 | Megiddo | Apr 2004 | B1 |
| 6728763 | Chen | Apr 2004 | B1 |
| 6785864 | Te et al. | Aug 2004 | B1 |
| 6842777 | Tuli | Jan 2005 | B1 |
| 6871213 | Graham et al. | Mar 2005 | B1 |
| 6871236 | Fishman et al. | Mar 2005 | B2 |
| 6931439 | Hanmann et al. | Aug 2005 | B1 |
| 6944665 | Brown et al. | Sep 2005 | B2 |
| 6963850 | Bezos et al. | Nov 2005 | B1 |
| 6976059 | Rogalski et al. | Dec 2005 | B1 |
| 7003442 | Tsuda | Feb 2006 | B1 |
| 7013310 | Messing et al. | Mar 2006 | B2 |
| 7051084 | Hayton et al. | May 2006 | B1 |
| 7054952 | Schwerdtfeger et al. | May 2006 | B1 |
| 7082476 | Cohen et al. | Jul 2006 | B1 |
| 7085736 | Keezer et al. | Aug 2006 | B2 |
| 7085753 | Weiss et al. | Aug 2006 | B2 |
| 7089316 | Andersen et al. | Aug 2006 | B2 |
| 7127473 | Agassi et al. | Oct 2006 | B2 |
| 7133846 | Ginter et al. | Nov 2006 | B1 |
| 7159023 | Tufts | Jan 2007 | B2 |
| 7171478 | Lueckhoff et al. | Jan 2007 | B2 |
| 7191211 | Tuli | Mar 2007 | B2 |
| 7219136 | Danner et al. | May 2007 | B1 |
| 7260841 | Tenereillo | Aug 2007 | B2 |
| 7274775 | Zavaliagk | Sep 2007 | B1 |
| 7353252 | Yang et al. | Apr 2008 | B1 |
| 7373313 | Kahle et al. | May 2008 | B1 |
| 7409719 | Armstrong et al. | Aug 2008 | B2 |
| 7426750 | Cooper et al. | Sep 2008 | B2 |
| 7441045 | Skene et al. | Oct 2008 | B2 |
| 7444337 | Zhou et al. | Oct 2008 | B2 |
| 7448079 | Tremain | Nov 2008 | B2 |
| 7483983 | Bonefas et al. | Jan 2009 | B1 |
| 7484089 | Kogen et al. | Jan 2009 | B1 |
| 7509397 | Totty et al. | Mar 2009 | B1 |
| 7543059 | Johnson et al. | Jun 2009 | B2 |
| 7552172 | Corboy et al. | Jun 2009 | B2 |
| 7565425 | Van Vleet et al. | Jul 2009 | B2 |
| 7599851 | Frengut et al. | Oct 2009 | B2 |
| 7610382 | Siegel | Oct 2009 | B1 |
| 7624047 | Round | Nov 2009 | B1 |
| 7653544 | Bradley et al. | Jan 2010 | B2 |
| 7730352 | Marquard et al. | Jun 2010 | B2 |
| 7792944 | DeSantis et al. | Sep 2010 | B2 |
| 7797421 | Scofield et al. | Sep 2010 | B1 |
| 7831582 | Scofield et al. | Nov 2010 | B1 |
| 7865528 | Neil | Jan 2011 | B2 |
| 7865720 | Little et al. | Jan 2011 | B2 |
| 7890528 | Khoshnevisan | Feb 2011 | B1 |
| 7904531 | Toomey | Mar 2011 | B2 |
| 7925782 | Sivasubramanian et al. | Apr 2011 | B2 |
| 7945637 | Van Vleet et al. | May 2011 | B2 |
| 7966184 | O'Canar et al. | Jun 2011 | B2 |
| 7966395 | Pope et al. | Jun 2011 | B1 |
| 7975000 | Dixon et al. | Jul 2011 | B2 |
| 7991859 | Miller et al. | Aug 2011 | B1 |
| 7996912 | Spalink et al. | Aug 2011 | B2 |
| 8010545 | Stefik et al. | Aug 2011 | B2 |
| 8010679 | Low et al. | Aug 2011 | B2 |
| 8015343 | Garman et al. | Sep 2011 | B2 |
| 8015496 | Rogers | Sep 2011 | B1 |
| 8046435 | Parekh et al. | Oct 2011 | B1 |
| 8051166 | Baumback et al. | Nov 2011 | B1 |
| 8051180 | Mazzaferri et al. | Nov 2011 | B2 |
| 8060463 | Spiegel | Nov 2011 | B1 |
| 8060616 | Richardson et al. | Nov 2011 | B1 |
| 8065417 | Richardson et al. | Nov 2011 | B1 |
| 8073850 | Hubbard et al. | Dec 2011 | B1 |
| 8079087 | Spies et al. | Dec 2011 | B1 |
| 8103742 | Green | Jan 2012 | B1 |
| 8103769 | Weiser et al. | Jan 2012 | B1 |
| 8117314 | Croft et al. | Feb 2012 | B2 |
| 8122098 | Richardson et al. | Feb 2012 | B1 |
| 8171085 | Tevanian, Jr. | May 2012 | B1 |
| 8185621 | Kasha | May 2012 | B2 |
| 8195767 | Albrecht et al. | Jun 2012 | B2 |
| 8204359 | Ljolje | Jun 2012 | B2 |
| 8209623 | Barletta et al. | Jun 2012 | B2 |
| 8224964 | Fredrickson et al. | Jul 2012 | B1 |
| 8249904 | DeSantis et al. | Aug 2012 | B1 |
| 8271887 | Offer et al. | Sep 2012 | B2 |
| 8307396 | Tofighbakhsh | Nov 2012 | B2 |
| 8316124 | Baumback et al. | Nov 2012 | B1 |
| 8336049 | Medovich | Dec 2012 | B2 |
| 8359637 | Yau et al. | Jan 2013 | B2 |
| 8386514 | Cheng et al. | Feb 2013 | B2 |
| 8391218 | Joshi et al. | Mar 2013 | B1 |
| 8392617 | Weber et al. | Mar 2013 | B1 |
| 8392980 | Ahrens et al. | Mar 2013 | B1 |
| 8448245 | Banerjee et al. | May 2013 | B2 |
| 8499088 | Breau et al. | Jul 2013 | B1 |
| 8510443 | Kim | Aug 2013 | B2 |
| 8566137 | Cabrera et al. | Oct 2013 | B1 |
| 8621621 | Burns et al. | Dec 2013 | B1 |
| 8660129 | Brendel et al. | Feb 2014 | B1 |
| 8671022 | Sinn et al. | Mar 2014 | B2 |
| 8683585 | Chen et al. | Mar 2014 | B1 |
| 8706860 | Trahan et al. | Apr 2014 | B2 |
| 8739170 | Gupta et al. | May 2014 | B1 |
| 8826242 | Livshits et al. | Sep 2014 | B2 |
| 20010036182 | Addante | Nov 2001 | A1 |
| 20010039490 | Verbitsky et al. | Nov 2001 | A1 |
| 20010051996 | Cooper et al. | Dec 2001 | A1 |
| 20010052006 | Barker et al. | Dec 2001 | A1 |
| 20020016925 | Pennec et al. | Feb 2002 | A1 |
| 20020026511 | Garcia-Luna-Aceves et al. | Feb 2002 | A1 |
| 20020030703 | Robertson et al. | Mar 2002 | A1 |
| 20020040395 | Davis et al. | Apr 2002 | A1 |
| 20020069369 | Tremain | Jun 2002 | A1 |
| 20020073155 | Anupam et al. | Jun 2002 | A1 |
| 20020103846 | Zisapel et al. | Aug 2002 | A1 |
| 20020107985 | Hwang et al. | Aug 2002 | A1 |
| 20020129119 | Aoki et al. | Sep 2002 | A1 |
| 20020184493 | Rees | Dec 2002 | A1 |
| 20020194302 | Blumberg | Dec 2002 | A1 |
| 20030004882 | Holler et al. | Jan 2003 | A1 |
| 20030005041 | Ullmann et al. | Jan 2003 | A1 |
| 20030009742 | Bass et al. | Jan 2003 | A1 |
| 20030023712 | Zhao et al. | Jan 2003 | A1 |
| 20030033434 | Kavacheri et al. | Feb 2003 | A1 |
| 20030041106 | Tuli | Feb 2003 | A1 |
| 20030046335 | Doyle et al. | Mar 2003 | A1 |
| 20030080995 | Tenenbaum et al. | May 2003 | A1 |
| 20030084121 | De Boor et al. | May 2003 | A1 |
| 20030097592 | Adusumilli | May 2003 | A1 |
| 20030126433 | Hui | Jul 2003 | A1 |
| 20030137531 | Katinsky et al. | Jul 2003 | A1 |
| 20030149646 | Chen et al. | Aug 2003 | A1 |
| 20030187932 | Kennedy | Oct 2003 | A1 |
| 20030208570 | Lapidous | Nov 2003 | A1 |
| 20030229697 | Borella | Dec 2003 | A1 |
| 20030233621 | Paolini et al. | Dec 2003 | A1 |
| 20040006481 | Kiecza et al. | Jan 2004 | A1 |
| 20040010543 | Grobman | Jan 2004 | A1 |
| 20040030887 | Harrisville-Wolff et al. | Feb 2004 | A1 |
| 20040066397 | Walker et al. | Apr 2004 | A1 |
| 20040073713 | Pentikainen et al. | Apr 2004 | A1 |
| 20040083294 | Lewis | Apr 2004 | A1 |
| 20040093376 | De Boor et al. | May 2004 | A1 |
| 20040093493 | Bisbee et al. | May 2004 | A1 |
| 20040098463 | Shen et al. | May 2004 | A1 |
| 20040139208 | Tuli | Jul 2004 | A1 |
| 20040143579 | Nakazawa | Jul 2004 | A1 |
| 20040181613 | Hashimoto et al. | Sep 2004 | A1 |
| 20040205448 | Grefenstette et al. | Oct 2004 | A1 |
| 20040220905 | Chen et al. | Nov 2004 | A1 |
| 20040228335 | Park et al. | Nov 2004 | A1 |
| 20040243622 | Morisawa | Dec 2004 | A1 |
| 20040267723 | Bharat | Dec 2004 | A1 |
| 20050010863 | Zernik | Jan 2005 | A1 |
| 20050027815 | Christodoulou et al. | Feb 2005 | A1 |
| 20050033577 | Bradley et al. | Feb 2005 | A1 |
| 20050060643 | Glass et al. | Mar 2005 | A1 |
| 20050138382 | Hougaard et al. | Jun 2005 | A1 |
| 20050147044 | Teodosiu et al. | Jul 2005 | A1 |
| 20050160014 | Moss et al. | Jul 2005 | A1 |
| 20050183039 | Revis | Aug 2005 | A1 |
| 20050188361 | Cai et al. | Aug 2005 | A1 |
| 20050204276 | Hosea et al. | Sep 2005 | A1 |
| 20050246193 | Roever et al. | Nov 2005 | A1 |
| 20050255829 | Kirkup et al. | Nov 2005 | A1 |
| 20050257400 | Sommerer et al. | Nov 2005 | A1 |
| 20050273463 | Zohar et al. | Dec 2005 | A1 |
| 20060031774 | Gaudette | Feb 2006 | A1 |
| 20060085766 | Dominowska et al. | Apr 2006 | A1 |
| 20060095336 | Heckerman et al. | May 2006 | A1 |
| 20060112167 | Steele et al. | May 2006 | A1 |
| 20060122889 | Burdick et al. | Jun 2006 | A1 |
| 20060123092 | Madams et al. | Jun 2006 | A1 |
| 20060161535 | Holbrook | Jul 2006 | A1 |
| 20060168510 | Bryar et al. | Jul 2006 | A1 |
| 20060184421 | Lipsky et al. | Aug 2006 | A1 |
| 20060212509 | Feigenbaum et al. | Sep 2006 | A1 |
| 20060242192 | Musgrove et al. | Oct 2006 | A1 |
| 20060248195 | Toumura et al. | Nov 2006 | A1 |
| 20060248442 | Rosenstein et al. | Nov 2006 | A1 |
| 20060259462 | Timmons | Nov 2006 | A1 |
| 20060265472 | Seitz et al. | Nov 2006 | A1 |
| 20060277167 | Gross et al. | Dec 2006 | A1 |
| 20060280121 | Matoba | Dec 2006 | A1 |
| 20060294366 | Nadalin et al. | Dec 2006 | A1 |
| 20060294461 | Nadamoto et al. | Dec 2006 | A1 |
| 20070022072 | Kao et al. | Jan 2007 | A1 |
| 20070027672 | Decary et al. | Feb 2007 | A1 |
| 20070073704 | Bowden et al. | Mar 2007 | A1 |
| 20070094241 | M. Blackwell et al. | Apr 2007 | A1 |
| 20070118740 | Deishi | May 2007 | A1 |
| 20070118801 | Harshbarger et al. | May 2007 | A1 |
| 20070118803 | Walker et al. | May 2007 | A1 |
| 20070124693 | Dominowska et al. | May 2007 | A1 |
| 20070139430 | Korn et al. | Jun 2007 | A1 |
| 20070150727 | Miyazawa | Jun 2007 | A1 |
| 20070150737 | Parupudi et al. | Jun 2007 | A1 |
| 20070168535 | Ikonen et al. | Jul 2007 | A1 |
| 20070180503 | Li et al. | Aug 2007 | A1 |
| 20070198364 | Quoe et al. | Aug 2007 | A1 |
| 20070208687 | O'Canar et al. | Sep 2007 | A1 |
| 20070226044 | Hanson | Sep 2007 | A1 |
| 20070240160 | Paterson-Jones et al. | Oct 2007 | A1 |
| 20070245260 | Koppert | Oct 2007 | A1 |
| 20070288589 | Chen et al. | Dec 2007 | A1 |
| 20070288855 | Rohrabaugh et al. | Dec 2007 | A1 |
| 20080016040 | Jones et al. | Jan 2008 | A1 |
| 20080028334 | De Mes | Jan 2008 | A1 |
| 20080059557 | DeSantis et al. | Mar 2008 | A1 |
| 20080086264 | Fisher | Apr 2008 | A1 |
| 20080104502 | Olston | May 2008 | A1 |
| 20080133540 | Hubbard et al. | Jun 2008 | A1 |
| 20080134033 | Burns et al. | Jun 2008 | A1 |
| 20080134058 | Shen et al. | Jun 2008 | A1 |
| 20080148401 | Shen | Jun 2008 | A1 |
| 20080155691 | Fossen et al. | Jun 2008 | A1 |
| 20080172607 | Baer | Jul 2008 | A1 |
| 20080181580 | Sakai et al. | Jul 2008 | A1 |
| 20080183672 | Canon et al. | Jul 2008 | A1 |
| 20080183889 | Andreev et al. | Jul 2008 | A1 |
| 20080184128 | Swenson et al. | Jul 2008 | A1 |
| 20080189770 | Sachtjen | Aug 2008 | A1 |
| 20080209325 | Suito et al. | Aug 2008 | A1 |
| 20080222299 | Boodaei | Sep 2008 | A1 |
| 20080229025 | Plamondon | Sep 2008 | A1 |
| 20080232775 | Ljolje | Sep 2008 | A1 |
| 20080288486 | Kim et al. | Nov 2008 | A1 |
| 20080289047 | Benea et al. | Nov 2008 | A1 |
| 20080301225 | Kamura | Dec 2008 | A1 |
| 20080320225 | Panzer et al. | Dec 2008 | A1 |
| 20090006258 | Ross | Jan 2009 | A1 |
| 20090012969 | Rail et al. | Jan 2009 | A1 |
| 20090013034 | Cheng et al. | Jan 2009 | A1 |
| 20090049443 | Powers et al. | Feb 2009 | A1 |
| 20090063854 | Parkinson | Mar 2009 | A1 |
| 20090063983 | Amidon et al. | Mar 2009 | A1 |
| 20090100345 | Miller | Apr 2009 | A1 |
| 20090103470 | Candelore | Apr 2009 | A1 |
| 20090132640 | Verma et al. | May 2009 | A1 |
| 20090150343 | English et al. | Jun 2009 | A1 |
| 20090164597 | Shuster | Jun 2009 | A1 |
| 20090164924 | Flake et al. | Jun 2009 | A1 |
| 20090187819 | Bonefas et al. | Jul 2009 | A1 |
| 20090198618 | Chan et al. | Aug 2009 | A1 |
| 20090204478 | Kaib et al. | Aug 2009 | A1 |
| 20090204964 | Foley et al. | Aug 2009 | A1 |
| 20090217199 | Hara et al. | Aug 2009 | A1 |
| 20090240717 | Mimatsu | Sep 2009 | A1 |
| 20090241191 | Keromytis et al. | Sep 2009 | A1 |
| 20090248680 | Kalavade | Oct 2009 | A1 |
| 20090254867 | Farouki et al. | Oct 2009 | A1 |
| 20090276488 | Alstad | Nov 2009 | A1 |
| 20090282021 | Bennett | Nov 2009 | A1 |
| 20090287659 | Bennett | Nov 2009 | A1 |
| 20090287698 | Marmaros et al. | Nov 2009 | A1 |
| 20090327517 | Sivasubramanian et al. | Dec 2009 | A1 |
| 20090327914 | Adar et al. | Dec 2009 | A1 |
| 20100005394 | Dubnov | Jan 2010 | A1 |
| 20100017704 | Jaffe et al. | Jan 2010 | A1 |
| 20100017880 | Masood | Jan 2010 | A1 |
| 20100027552 | Hill | Feb 2010 | A1 |
| 20100031028 | Adams et al. | Feb 2010 | A1 |
| 20100036740 | Barashi | Feb 2010 | A1 |
| 20100042724 | Jeon et al. | Feb 2010 | A1 |
| 20100048296 | Adiraju | Feb 2010 | A1 |
| 20100050201 | Kubota et al. | Feb 2010 | A1 |
| 20100057639 | Schwarz et al. | Mar 2010 | A1 |
| 20100070569 | Turakhia | Mar 2010 | A1 |
| 20100070849 | Sadan et al. | Mar 2010 | A1 |
| 20100088404 | Mani et al. | Apr 2010 | A1 |
| 20100115126 | Kanakadandi et al. | May 2010 | A1 |
| 20100125507 | Tarantino, III et al. | May 2010 | A1 |
| 20100131594 | Kashimoto | May 2010 | A1 |
| 20100131646 | Drako | May 2010 | A1 |
| 20100135473 | Dewing et al. | Jun 2010 | A1 |
| 20100138293 | Ramer et al. | Jun 2010 | A1 |
| 20100138534 | Mutnuru et al. | Jun 2010 | A1 |
| 20100144314 | Sherkin et al. | Jun 2010 | A1 |
| 20100145902 | Boyan et al. | Jun 2010 | A1 |
| 20100185864 | Gerdes et al. | Jul 2010 | A1 |
| 20100191544 | Bosworth et al. | Jul 2010 | A1 |
| 20100198742 | Chang et al. | Aug 2010 | A1 |
| 20100218106 | Chen et al. | Aug 2010 | A1 |
| 20100223470 | Lord et al. | Sep 2010 | A1 |
| 20100235473 | Koren et al. | Sep 2010 | A1 |
| 20100278453 | King | Nov 2010 | A1 |
| 20100281112 | Plamondon | Nov 2010 | A1 |
| 20100293190 | Kaiser et al. | Nov 2010 | A1 |
| 20100312750 | Moore et al. | Dec 2010 | A1 |
| 20100312788 | Bailey | Dec 2010 | A1 |
| 20100313149 | Zhang et al. | Dec 2010 | A1 |
| 20100318892 | Teevan et al. | Dec 2010 | A1 |
| 20100325239 | Khedouri et al. | Dec 2010 | A1 |
| 20100325287 | Jagadeeswaran et al. | Dec 2010 | A1 |
| 20100332513 | Azar et al. | Dec 2010 | A1 |
| 20110010762 | Nijdam et al. | Jan 2011 | A1 |
| 20110022957 | Lee | Jan 2011 | A1 |
| 20110029854 | Nashi et al. | Feb 2011 | A1 |
| 20110055203 | Gutt et al. | Mar 2011 | A1 |
| 20110055398 | DeHaan et al. | Mar 2011 | A1 |
| 20110066982 | Paulsami et al. | Mar 2011 | A1 |
| 20110072502 | Song et al. | Mar 2011 | A1 |
| 20110078140 | Dube et al. | Mar 2011 | A1 |
| 20110078705 | Maclinovsky et al. | Mar 2011 | A1 |
| 20110119352 | Perov | May 2011 | A1 |
| 20110119374 | Ruhl et al. | May 2011 | A1 |
| 20110119661 | Agrawal et al. | May 2011 | A1 |
| 20110126296 | Moore | May 2011 | A1 |
| 20110154028 | Kirkup et al. | Jun 2011 | A1 |
| 20110161849 | Stallings et al. | Jun 2011 | A1 |
| 20110167156 | Mani et al. | Jul 2011 | A1 |
| 20110173177 | Junqueira et al. | Jul 2011 | A1 |
| 20110173637 | Brandwine et al. | Jul 2011 | A1 |
| 20110178868 | Garg et al. | Jul 2011 | A1 |
| 20110185025 | Cherukuri et al. | Jul 2011 | A1 |
| 20110191327 | Lee | Aug 2011 | A1 |
| 20110197121 | Kletter | Aug 2011 | A1 |
| 20110202848 | Ismalon | Aug 2011 | A1 |
| 20110208822 | Rathod | Aug 2011 | A1 |
| 20110208840 | Blackman | Aug 2011 | A1 |
| 20110212717 | Rhoads et al. | Sep 2011 | A1 |
| 20110213966 | Fu et al. | Sep 2011 | A1 |
| 20110214082 | Osterhout et al. | Sep 2011 | A1 |
| 20110219448 | Sreedharan et al. | Sep 2011 | A1 |
| 20110231555 | Ebrahimi et al. | Sep 2011 | A1 |
| 20110246873 | Tolle et al. | Oct 2011 | A1 |
| 20110249074 | Cranfill et al. | Oct 2011 | A1 |
| 20110256889 | Polis et al. | Oct 2011 | A1 |
| 20110261828 | Smith | Oct 2011 | A1 |
| 20110264649 | Hsiao et al. | Oct 2011 | A1 |
| 20110282997 | Prince et al. | Nov 2011 | A1 |
| 20110289074 | Leban | Nov 2011 | A1 |
| 20110289157 | Pirnazar | Nov 2011 | A1 |
| 20110296341 | Koppert | Dec 2011 | A1 |
| 20110296503 | Shull et al. | Dec 2011 | A1 |
| 20110302510 | Harrison et al. | Dec 2011 | A1 |
| 20110314154 | Resch et al. | Dec 2011 | A1 |
| 20110320598 | Solin | Dec 2011 | A1 |
| 20110321100 | Tofighbakhsh | Dec 2011 | A1 |
| 20110321139 | Jayaraman et al. | Dec 2011 | A1 |
| 20120005258 | Cok et al. | Jan 2012 | A1 |
| 20120005276 | Guo et al. | Jan 2012 | A1 |
| 20120005600 | Ito | Jan 2012 | A1 |
| 20120022942 | Holloway et al. | Jan 2012 | A1 |
| 20120023487 | Letca et al. | Jan 2012 | A1 |
| 20120030460 | Chang | Feb 2012 | A1 |
| 20120047234 | Terayoko | Feb 2012 | A1 |
| 20120047449 | Buckart et al. | Feb 2012 | A1 |
| 20120054316 | Piazza et al. | Mar 2012 | A1 |
| 20120054869 | Yen et al. | Mar 2012 | A1 |
| 20120066502 | Borneman et al. | Mar 2012 | A1 |
| 20120066586 | Shemesh | Mar 2012 | A1 |
| 20120072821 | Bowling | Mar 2012 | A1 |
| 20120084433 | Bar-Caspi et al. | Apr 2012 | A1 |
| 20120084644 | Robert et al. | Apr 2012 | A1 |
| 20120096269 | McAlister | Apr 2012 | A1 |
| 20120096365 | Wilkinson et al. | Apr 2012 | A1 |
| 20120110017 | Gu et al. | May 2012 | A1 |
| 20120117565 | Staelin et al. | May 2012 | A1 |
| 20120117649 | Holloway et al. | May 2012 | A1 |
| 20120137201 | White et al. | May 2012 | A1 |
| 20120143944 | Reeves et al. | Jun 2012 | A1 |
| 20120144288 | Caruso et al. | Jun 2012 | A1 |
| 20120150844 | Lindahl et al. | Jun 2012 | A1 |
| 20120158694 | Skrenta et al. | Jun 2012 | A1 |
| 20120166526 | Ambardekar | Jun 2012 | A1 |
| 20120166922 | Rolles | Jun 2012 | A1 |
| 20120192220 | Wyatt et al. | Jul 2012 | A1 |
| 20120198020 | Parker et al. | Aug 2012 | A1 |
| 20120198516 | Lim | Aug 2012 | A1 |
| 20120203904 | Niemela et al. | Aug 2012 | A1 |
| 20120206317 | Wong et al. | Aug 2012 | A1 |
| 20120210233 | Davis et al. | Aug 2012 | A1 |
| 20120215833 | Chen et al. | Aug 2012 | A1 |
| 20120215834 | Chen et al. | Aug 2012 | A1 |
| 20120215919 | Labat et al. | Aug 2012 | A1 |
| 20120216035 | Leggette et al. | Aug 2012 | A1 |
| 20120254402 | Panidepu et al. | Oct 2012 | A1 |
| 20120284629 | Peters et al. | Nov 2012 | A1 |
| 20120290348 | Hackett et al. | Nov 2012 | A1 |
| 20120297341 | Glazer et al. | Nov 2012 | A1 |
| 20120317295 | Baird et al. | Dec 2012 | A1 |
| 20120324043 | Burkard et al. | Dec 2012 | A1 |
| 20120331406 | Baird et al. | Dec 2012 | A1 |
| 20130007101 | Trahan et al. | Jan 2013 | A1 |
| 20130007102 | Trahan et al. | Jan 2013 | A1 |
| 20130031461 | Hou et al. | Jan 2013 | A1 |
| 20130046878 | Fryc et al. | Feb 2013 | A1 |
| 20130051686 | Bennett | Feb 2013 | A1 |
| 20130073388 | Heath | Mar 2013 | A1 |
| 20130080611 | Li et al. | Mar 2013 | A1 |
| 20130097380 | Colgrove et al. | Apr 2013 | A1 |
| 20130097494 | St. Jacques et al. | Apr 2013 | A1 |
| 20130103785 | Lyon | Apr 2013 | A1 |
| 20130111579 | Newman et al. | May 2013 | A1 |
| 20130165238 | Batista Jerez | Jun 2013 | A1 |
| 20130185715 | Dunning et al. | Jul 2013 | A1 |
| 20130198641 | Brownlow et al. | Aug 2013 | A1 |
| 20130198823 | Hitchcock et al. | Aug 2013 | A1 |
| 20130202150 | Sinha et al. | Aug 2013 | A1 |
| 20130318354 | Entschew et al. | Nov 2013 | A1 |
| 20140006129 | Heath | Jan 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 2013003631 | Jan 2013 | WO |
| WO 2013049025 | Apr 2013 | WO |
| Entry |
|---|
| Bango, Rey, “How JS & Ajax work in Opera Mini 4”, Nov. 2, 2007, XP055050107, Retrieved from the Internet. |
| Brinkmann, M., “Record and Share your browser history with Hooeey,” ghacks.net, Feb. 26, 2008, 6 pages, printed on Jan. 25, 2013. |
| Considine, A., “The Footprints of Web Feet,” The New York Times, Mar. 4, 2011, 3 pages, printed on Jan. 25, 2013. |
| EyeBrowse: Record, Visualize and Share your Browser History, Information Aesthetics, Sep. 18, 2009, 2 pages, printed on Jan. 25, 2013. |
| Feuerstein, Adam, “Flyswat Takes Aim,” San Francisco Business Times, printed from http://www.bizjournals.com/sanfrancisco/stories/1999/10/25/story2.html?t=printable, Oct. 22, 1999, 2 pages. |
| Gabber, et al., “How to Make Personalized Web Browsing Simple, Secure, and Anonymous,” Financial Cryptography, 16 pages (1997). |
| Gingerich, Jason, “Keycorp Making Site Into Portal,” KRTBN Knight-Ridder Tribune Business News (South Bend Tribune, Indiana), Oct. 25, 1999, 2 pages. |
| Hopper, D. Ian, “Desktops Now Have Power to Comparison-Shop,” Oct. 18, 1999, printed from http://www.cnn.com/TECH/computing/9910/18/r.u.sure/index.html, 3 pages. |
| Van Kleek, M., Introducing “Eyebrowse”—Track and share your web browsing in real time, Haystack Blog, Aug. 28, 2009, 3 pages, printed on Jan. 25, 2013. |
| Web page titled “RSS Ticker: Add-ons for Firefox,” https://addons.mozilla.org/en-US/firefox/addon/rss-ticker/, 3 printed pages, printed on Feb. 7, 2013. |
| Web page titled “What Internet Users Do on a Typical Day, Trend Data (Adults), Pew Internet & American Life Project,” printed from http://pewinternet.org/Static-Pages/Trend-Data-(Adults)/Online-Activities-Daily.aspx on Nov. 29, 2012, 4 pages. |
| Chen, H., et al., “Bringing Order to the Web: Automatically Categorizing Search Results,” Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 1-6, 2000, pp. 145-152. |
| Close ‘n’ Forget Firefox add on, Evilfantasy's blog, http://evilfantasy.wordpress.com/2009/03/24/close-%E2%80%98n%E2%80%99-forget-firefox-add-on/, retrieved Mar. 24, 2009, 1 page. |
| Rao, H.C.-H., et al., “A Proxy-Based Personal Web Archiving Service,” Operating Systems Review, 35(1):61-72, 2001. |
| Teevan, J., et al., “Changing How People View Changes on the Web,” 2009, Proceedings of the 22nd Annual ACM Symposium on User Interface Software and Technology, New York, 2009, pp. 237-246. |
| Baumann, A., et al., Enhancing STEM Classes Using Weave: A Collaborative Web-Based Visualization Environment, Integrated Stem Education Conference, Apr. 2, 2011, Ewing, New Jersey, pp. 2A-1-2A-4. |
| De Carvalho, L.G., et al., Synchronizing Web Browsing Data With Browserver, Proceedings of the IEEE Symposium on Computers and Communications, Jun. 22-25, 2010, Riccione, Italy, pp. 738-743. |
| Acharya, et al., Balancing Push and Pull for Data Broadcast, Proceedings of ACM SIGMOD Conference, May 1997, pp. 1-12, Tucson, AZ. |
| Acharya, et al., Prefetching from a Broadcast Disk, Proceedings of the International Conference on Data Engineering, Feb. 1996, New Orleans, LA. |
| Amazon Gives Virtual Private Clouds Internet Access, available at http://web2.sys-con.com/node/1759023/, Mar. 2011. |
| Bestavros, et al., Server-initiated Document Dissemination for the WWW, IEEE Data Engineering Bulletin, Sep. 1996, vol. 19, Issue 3, pp. 3-11, Boston, MA. |
| Brooks, et al., Application-Specific Proxy Servers as HTTP Stream Transducers, Dec. 1995, pp. 1-7. |
| Chinen, et al., An Interactive Prefetching Proxy Server for Improvement of WWW Latency, Jun. 1997, pp. 1-10. |
| Curewitz, et al., Practical Prefetching via Data Compression, SIGMOD Conference, 1993, pp. 10, San Diego, CA. |
| Dias, et al., A Smart Internet Caching System, 1996, pp. 1-12, Moratuwa, Sri Lanka. |
| Franklin, et al., Dissemination-Based Information Systems, IEEE Data Engineering Bulletin, Sep. 1996, vol. 19, Issue 3, pp. 1-9. |
| Gingerich, Jason, Keycorp Making Site Into Portal: Keycorp, South Bend Tribune, Ind., Apr. 9, 2009, 2 pages. |
| Gulbrandsen, et al., “A DNS RR for specifying the location of services (DNS SRV)”, RFC 2782, 12 pages, Feb. 2000. |
| Inoue, et al., An Adaptive WWW Cache Mechanism in the AI3 Network, 1997, pp. 1-9. |
| Kumar, V., et al, “Metadata Visualization for Digital Libraries: Interactive Timeline Editing and Review,” Proceedings of the Third ACM Conference on Digital Libraries, ACM, 1998, pp. 126-133. |
| Lubonski, et al., An Adaptation Architecture to Improve User-Perceived QoS of Multimedia Services for Enterprise Remote Desktop Protocols. NG12005, pp. 149-156. |
| Malik, et al., “Virtual Cloud: Rent Out the Rented Resources”, 6th International Conference on Internet Technology and Secured Transactions, Dec. 2011. |
| Mockapetris, “Domain Names—Implementation and Specification”, RFC 1035, 55 pages, Nov. 1987. |
| Monroy, Carlos, et al, “Interactive Timeline Viewer (ItLv): A Tool to Visualize Variants Among Documents,” Visual Interfaces to Digital Libraries, Springer Berlin Heidelberg, 2002, pp. 1-11. |
| Opera Mini, http://en.wikipedia.org/wiki/Opera—mini, last modified on Mar. 7, 2013 at 10:31. |
| Padmanabhan, et al., Using Predictive Prefetching to Improve World Wide Web Latency, Computer Communication Review, 1996, vol. 26, pp. 22-36. |
| Shrikumar, et al., Thinternet: Life at the End of a Tether, 1994, vol. 222-09. |
| Sullivan, D., “Google Search History Expands, Becomes Web History”, http://searchengineland.com/google-search-history-expands-becomes-web-history-11016, Apr. 19, 2007, 12 pages. |
| Wang, et al., Prefetching in World Wide Web, Department of Computer Science, University College London, Nov. 18-22, 1996, London, UK. |
