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 a communication network. For example, a user at a personal computing device can utilize a software browser application, typically referred to as a software browser application, to request a network resource (e.g., 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 request for content is typically initiated by the selection or input of a network resource identifier, such as a Uniform Resource Locator (“URL”), corresponding to a specific Web site. For example, a user can enter a specific URL, utilize a stored history previously accessed URLs or use an input device to select from a listing of a set of URLs. Responsive to the request for content, the client computing device obtains content associated with the requested Web page and renders the requested content on the client computing device. Once the content has been rendered, a user can access the rendered content via user input devices, such as touch screens, pens, mice, keyboards, and the like.
The foregoing aspects and many of the attendant advantages will become more readily appreciated by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
Generally described, aspects of the present disclosure relate to the management of content and information corresponding to the access of content. Specifically, aspects of the present disclosure relate to the selective management of resources obtained by a software browser application and rendered to a user. The software browser application obtains resources from a network resource, such as a Web page. In one embodiment, the software browser application presents, among other controls or icons, a graphical icon that is representative of a command to initiate a network based service on selected resources, such as a network-based storage service. Responsive to a selection of the graphical icon, the software browser application can transmit the appropriate network-based service request for the selected resources.
As used herein, reference to “client computing device” will not necessarily be limited to any particular type of device or to the illustrative examples of devices described herein. Still further, reference to “software browser application” will not necessarily be limited as to any type of software application and does not prevent the incorporation of aspects of the present disclosure into other types of software applications or operating system functionality. Although aspects of the present disclosure will be described with regard to an illustrative network environments and component interactions, flow diagrams, graphical icons and screen interfaces, one skilled in the relevant art will appreciate that the disclosed embodiments are illustrative in nature and should not be construed as limiting.
With reference now to
In an illustrative embodiment, the client computing devices 102 include necessary hardware and software components for establishing communications over a communication network 116, such as a wide area network or local area network. For example, the client computing devices 102 may be equipped with networking equipment and software browser applications that facilitate communications via the Internet or an intranet.
Illustratively, the client computing devices 102 may have varied local computing resources such as central processing units and architectures, memory, mass storage, graphics processing units, communication network availability and bandwidth, etc. Generally, however, each computing device 102 may include one or more processing units, such as one or more CPUs. The computing device 102 may also include system memory, which may correspond to any combination of volatile and/or non-volatile storage mechanisms. The system memory may store information that provides an operating system component, various program modules, program data, or other components. The computing device 102 performs functions by using the processing unit(s) to execute instructions provided by the system memory. The computing device may also include one or more input devices (keyboard, mouse device, specialized selection keys, touch screen interface, stylus, etc.) and one or more output devices (displays, printers, audio output mechanisms, etc.). The computing device 102 may also include one or more types of removable storage and one or more types of non-removable storage. Still further, the computing device 102 can include communication components for facilitating communication via wired and wireless communication networks, such as the wireless communication network 116.
As illustrated in
The content delivery environment 100 can also include one or more content providers 110 in communication with the one or more client computing devices 102 or other service providers via the communication network 116. The content provider 110 illustrated in
With continued reference to
With reference now to
With reference to
Upon accessing the network resource and receiving any associated content from the content provider 110, the client computing device 102, such as through the software browser application 104, processes the requested resources and renders the received resources as appropriate (3). Although not illustrated in
With reference to
With reference now to
With continued reference to
One skilled in the relevant art will appreciate that NCCs utilize physical computing device resources and software to provide multiple instances of a virtual machine or to dynamically cause the creation of instances of a virtual machine. As applied to the present disclosure, the virtual machine instances execute a software browser application that is in communication with the software browser application 104 on the client computing device 102. In this embodiment, the software browser application executed on the virtual machine instance works in conjunction with the software browser application 104 on the client computing device 102 to process content. The NCCs may further include additional software or hardware components that facilitate communications including, but not limited to, load balancing or load sharing software or hardware components for selecting instances of a virtual machine supporting a requested application or providing information to a DNS nameserver to facilitate request routing.
With reference now to
With reference to
As illustrated in
With reference to
With reference to
As further illustrated in
Turning now to
At block 302, the software browser application 104 obtains one or more resources based on a resource request initiated by (or on behalf of) a user. As previously discussed, in one embodiment, a client computing device 102 initiates a request for content by identification of a desired network service 118, such as via identification of a specific URL. In one example, the software browser application 104 receives an input of a specific URL to access, such via a keyboard associated with the client computing device 102. In another example, a user can manipulate a graphical user interface to select an object, such as a selection of an embedded hyperlink or selection of an entry in a “Favorites” listing. The manipulation of the graphical user interface results in the software browser application 104 receiving or recalling the information (e.g., the URL or network address) used to access the desired network service 118. Still further, upon accessing the network service and receiving any associated content from the content provider 110, the client computing device 102, such as through the software browser application 104, processes the requested resources and renders the received resources as appropriate. The processing of the resources by the software browser application 104 can include multiple iterative resource requests corresponding to an original resource (such as a Web page) and a number of embedded resources. One skilled in the relevant art will appreciate that rendering of the resource can result in the generation of one or more display objects on a display associated with the client computing device 102. The display objects may correspond to the resource or be representative of the resource.
At block 304, the software browser application 104 can classify the displayed objects in order to facilitate the selection of multiple objects by user input. In one example, the classification of the objects can correspond to an identification of common Meta-data or other information that will be used to group display objects and the underlying resources. For example, the software browser application 104 can group display objects that are provided by the same content provider 110 or that have a common network address. In another example, the software browser application 104 can sort objects based attributes of the resource, such as size of the file, dimensions of an image file, length of audio or video file, keywords, associated resolution, author, pricing plan, and the like. In another example, the software browser application 104 can classify objects based on historical information, such as previous interactions by the specific user or groups of users. In this example, a software browser application 104 may group a set of images based on historical information indicating that a majority of users grouped the set of images. One skilled in the relevant art will appreciate that additional or alternative groupings may also be implemented.
At block 306, the software browser application 104 obtains user input or indications of user input, such as via information provided to the input interface component 106. In one embodiment, the user input can correspond to a selection of a graphical icon or control provided by, or otherwise associated with, the software browser application 104. Example graphical icons and controls that are associated with a software browser application 104 will be described with regard to
At decision block 308, a test is conducted to determine whether the received input corresponds to a selection of multiple display objects corresponding to a set of resources. The determination of whether multiple display objects at decision block 308 can be based on various types of user input and interfaces and the grouping information generated by the software browser application 104. Examples of the selection of multiple objects will be described with regard to
If only a single object is selected at decision block 308 or once the set of multiple objects are selected at block 310, at block 312, the software browser application 104 determines processing actions for the set of selected objects. In an illustrative embodiment, the processing actions correspond to the type of processing or network based services that are available for the selected display objects. For example, the software browser application 104 may determine that the set of selected display objects may be stored on a network based storage service or posted to a social network. In another example, the software browser application 104 may determine that the set of selected network based services may be copied to a distribution service for transmitting to other client computing devices 102. In a further example, the software browser application 104 may utilize information services or other configuration information to determine that one or more network based services are unavailable. In this example, the software browser application 104 may determine that restrictions have been placed on one or more of the objects that prohibits distribution or network based storage.
At block 314, the software browser application 104 determines network based service parameters based on a selection of one or more of the available actions or network based services. In one embodiment, the network based service parameters can correspond to the identification of the resources to be processed. In one example, the software browser application 104 can utilize copies of the resources for purposes of initiating the service request. In another embodiment, the software browser application 104 can obtain identifiers or other pointers that do not require the transmission of the resources to the network based services. In another embodiment, the network based service parameters can include user or account identifiers, user configurations, authentication information or other configuration information that will be used to process the service request. For example, the software browser application 104 can recall or otherwise obtain naming convention configuration information for facilitating network based storage. In another example, the software browser application 104 can obtain third party information, such as location information to include in the network based service request. In still a further example, the software browser application 104 can collect additional information to be associated with the resources, such as text to accompany image files posted on a network service.
At block 316, the software browser application 104 transmits the network based service requests with any appropriate service parameter information. As illustrated in
d are block diagrams illustrative of various screen interfaces generated by a software browser application 104 for presenting, among other controls, one or more graphical icons or controls corresponding to a request for network based services. With reference to
With continued reference to
With reference to
As illustrated in
With reference to
With reference to
For purposes of an illustrative embodiment, the screen display 450 can be divided into a number of subareas 452, 454, 456, and 458 for displaying objects or for obtaining input corresponding to network service request commands. For example, subarea 452 may be configured to display a first set of display objects 460 while subarea 454 may be configured to display a second set of display objects 462. In one embodiment, the screen display 450 can include a display object 464 that can be manipulated (as illustrated at 466) to elicit a network based service request. In another embodiment, the placement of a display object in subarea 458 may elicit the same or a different network based request. Still further, a length of time in which an object is selected may also be utilized in the selection of display objects or the determination of whether a network based service request has been selected.
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 disclosure. 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. Moreover, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey utilization of the conjunction “or” in enumerating a list of elements does not limit the selection of only a single element and can include the combination of two or more elements.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/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 and/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 and/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 and/or execution of the various data and/or components described above. Alternatively, some or all of the methods described herein may alternatively be embodied in specialized computer hardware. In addition, the components referred to herein may be implemented in hardware, software, firmware or a combination thereof.
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 |
5872850 | Klein et al. | Feb 1999 | A |
5961593 | Gabber et al. | Oct 1999 | A |
6049812 | Bertram et al. | Apr 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 |
6430624 | Jamtgaard et al. | Aug 2002 | B1 |
6549941 | Jaquith et al. | Apr 2003 | B1 |
6560620 | Ching | May 2003 | B1 |
6625624 | Chen et al. | Sep 2003 | B1 |
6654784 | Wei | Nov 2003 | B1 |
6704024 | Robotham et al. | Mar 2004 | B2 |
6728763 | Chen | Apr 2004 | B1 |
6785864 | Te et al. | Aug 2004 | 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 |
7003442 | Tsuda | Feb 2006 | B1 |
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 |
7089316 | Andersen et al. | Aug 2006 | B2 |
7159023 | Tufts | Jan 2007 | B2 |
7171478 | Lueckhoff et al. | Jan 2007 | B2 |
7191211 | Tuli | Mar 2007 | B2 |
7353252 | Yang et al. | Apr 2008 | B1 |
7373313 | Kahle et al. | May 2008 | B1 |
7428540 | Coates et al. | Sep 2008 | B1 |
7483983 | Bonefas et al. | Jan 2009 | B1 |
7509397 | Totty et al. | Mar 2009 | B1 |
7543059 | Johnson et al. | Jun 2009 | B2 |
7610382 | Siegel | Oct 2009 | B1 |
7624047 | Round | Nov 2009 | B1 |
7734732 | Soelberg | Jun 2010 | B2 |
7792944 | DeSantis et al. | Sep 2010 | B2 |
7831582 | Scofield et al. | Nov 2010 | B1 |
7975000 | Dixon et al. | Jul 2011 | B2 |
7996912 | Spalink et al. | Aug 2011 | B2 |
8010545 | Stefik et al. | Aug 2011 | B2 |
8015496 | Rogers | Sep 2011 | B1 |
8060463 | Spiegel | Nov 2011 | B1 |
8073850 | Hubbard et al. | Dec 2011 | B1 |
8103742 | Green | Jan 2012 | B1 |
8185621 | Kasha | May 2012 | B2 |
8195767 | Albrecht et al. | Jun 2012 | B2 |
8224964 | Fredrickson et al. | Jun 2012 | B1 |
8249904 | DeSantis et al. | Aug 2012 | B1 |
8271836 | Hawkins | Sep 2012 | B2 |
8271887 | Offer et al. | Sep 2012 | B2 |
8316124 | Baumback et al. | Nov 2012 | B1 |
8336049 | Medovich | Dec 2012 | B2 |
8577963 | Trahan et al. | Nov 2013 | B2 |
8706860 | Trahan et al. | Apr 2014 | B2 |
8799412 | Trahan et al. | Aug 2014 | B2 |
8914514 | Jenkins et al. | Dec 2014 | B1 |
20010039490 | Verbitsky et al. | Nov 2001 | A1 |
20010052006 | Barker et al. | Dec 2001 | A1 |
20020015042 | Robotham et al. | Feb 2002 | A1 |
20020026511 | Garcia-Luna-Aceves et al. | Feb 2002 | A1 |
20020030703 | Robertson et al. | Mar 2002 | A1 |
20020073155 | Anupam et al. | Jun 2002 | A1 |
20020103846 | Zisapel et al. | Aug 2002 | A1 |
20020194302 | Blumberg | Dec 2002 | A1 |
20030023712 | Zhao et al. | Jan 2003 | A1 |
20030041106 | Tuli | Feb 2003 | A1 |
20040010543 | Grobman | Jan 2004 | A1 |
20040066397 | Walker et al. | Apr 2004 | A1 |
20040083294 | Lewis | Apr 2004 | A1 |
20040139208 | Tuli | Jul 2004 | A1 |
20040181613 | Hashimoto et al. | Sep 2004 | A1 |
20040205448 | Grefenstette et al. | Oct 2004 | A1 |
20040220905 | Chen et al. | Nov 2004 | A1 |
20040243622 | Morisawa | Dec 2004 | A1 |
20050010863 | Zernik | Jan 2005 | A1 |
20050060643 | Glass et al. | Mar 2005 | A1 |
20050138382 | Hougaard et al. | Jun 2005 | A1 |
20050183039 | Revis | Aug 2005 | A1 |
20050246193 | Roever et al. | Nov 2005 | A1 |
20050278698 | Verco | Dec 2005 | A1 |
20060015574 | Seed et al. | Jan 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 |
20060168510 | Bryar et al. | Jul 2006 | A1 |
20060173819 | Watson | Aug 2006 | A1 |
20060184421 | Lipsky et al. | Aug 2006 | A1 |
20060248195 | Toumura et al. | Nov 2006 | A1 |
20060248442 | Rosenstein et al. | Nov 2006 | A1 |
20060248453 | Bennett et al. | Nov 2006 | A1 |
20060277167 | Gross et al. | Dec 2006 | A1 |
20060288112 | Soelberg | Dec 2006 | A1 |
20060294461 | Nadamoto et al. | Dec 2006 | A1 |
20070022072 | Kao et al. | Jan 2007 | A1 |
20070027672 | Decary et al. | Feb 2007 | A1 |
20070061700 | Kothari et al. | Mar 2007 | A1 |
20070089174 | Bader | Apr 2007 | A1 |
20070094241 | Blackwell et al. | Apr 2007 | A1 |
20070118803 | Walker et al. | May 2007 | A1 |
20070124693 | Dominowska et al. | May 2007 | A1 |
20070139430 | Korn et al. | Jun 2007 | A1 |
20070168535 | Ikonen et al. | Jul 2007 | A1 |
20070240160 | Paterson-Jones et al. | Oct 2007 | A1 |
20070288589 | Chen et al. | Dec 2007 | A1 |
20070288855 | Rohrabaugh et al. | Dec 2007 | A1 |
20080028334 | De Mes | Jan 2008 | A1 |
20080034019 | Cisler et al. | Feb 2008 | A1 |
20080104502 | Olston | May 2008 | A1 |
20080183672 | Canon et al. | Jul 2008 | A1 |
20080184128 | Swenson et al. | Jul 2008 | A1 |
20080301180 | Klassen | Dec 2008 | A1 |
20080320225 | Panzer et al. | Dec 2008 | A1 |
20090012969 | Rail et al. | Jan 2009 | A1 |
20090094339 | Allen et al. | Apr 2009 | A1 |
20090104934 | Jeong | Apr 2009 | A1 |
20090132640 | Verma et al. | May 2009 | A1 |
20090158141 | Bauchot et al. | Jun 2009 | A1 |
20090164924 | Flake et al. | Jun 2009 | A1 |
20090187819 | Bonefas et al. | Jul 2009 | A1 |
20090204478 | Kaib et al. | Aug 2009 | A1 |
20090217199 | Hara et al. | Aug 2009 | A1 |
20090237728 | Yamamoto | Sep 2009 | A1 |
20090248622 | Zhang | Oct 2009 | A1 |
20090248680 | Kalavade | Oct 2009 | A1 |
20090254867 | Farouki et al. | Oct 2009 | A1 |
20090282021 | 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 |
20100036740 | Barashi | Feb 2010 | A1 |
20100057639 | Schwarz et al. | Mar 2010 | A1 |
20100088647 | Jing | Apr 2010 | A1 |
20100125507 | Tarantino, III et al. | May 2010 | A1 |
20100131594 | Kashimoto | May 2010 | A1 |
20100138293 | Ramer et al. | Jun 2010 | A1 |
20100218106 | Chen et al. | Aug 2010 | A1 |
20100293190 | Kaiser et al. | Nov 2010 | A1 |
20100312750 | Moore et al. | Dec 2010 | A1 |
20100312788 | Bailey | Dec 2010 | A1 |
20100318892 | Teevan et al. | Dec 2010 | A1 |
20100332513 | Azar et al. | Dec 2010 | A1 |
20110022957 | Lee | Jan 2011 | A1 |
20110029854 | Nashi et al. | Feb 2011 | A1 |
20110055203 | Gutt et al. | Mar 2011 | A1 |
20110078140 | Dube et al. | Mar 2011 | A1 |
20110078705 | Maclinovsky et al. | Mar 2011 | A1 |
20110087690 | Cairns | Apr 2011 | A1 |
20110119352 | Perov | May 2011 | A1 |
20110119661 | Agrawal et al. | May 2011 | A1 |
20110161849 | Stallings et al. | Jun 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 |
20110208822 | Rathod | Aug 2011 | A1 |
20110246873 | Tolle et al. | Oct 2011 | A1 |
20110289074 | Leban | Nov 2011 | A1 |
20110296341 | Koppert | Dec 2011 | A1 |
20110302510 | Harrison et al. | Dec 2011 | A1 |
20120022942 | Holloway et al. | Jan 2012 | A1 |
20120054316 | Piazza et al. | Mar 2012 | A1 |
20120072821 | Bowling | Mar 2012 | A1 |
20120084433 | Bar-Caspi et al. | Apr 2012 | A1 |
20120084644 | Robert et al. | Apr 2012 | A1 |
20120096365 | Wilkinson et al. | Apr 2012 | A1 |
20120110017 | Gu et al. | May 2012 | A1 |
20120137201 | White et al. | May 2012 | A1 |
20120143944 | Reeves et al. | Jun 2012 | A1 |
20120150844 | Lindahl et al. | Jun 2012 | A1 |
20120166922 | Rolles | Jun 2012 | A1 |
20120198516 | Lim | Aug 2012 | A1 |
20120215834 | Chen et al. | Aug 2012 | A1 |
20120215919 | Labat et al. | Aug 2012 | A1 |
20120284629 | Peters et al. | Nov 2012 | A1 |
20120317295 | Baird 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 |
20130066848 | Tuttle | Mar 2013 | A1 |
20130080611 | Li et al. | Mar 2013 | A1 |
20140067923 | Trahan et al. | Mar 2014 | A1 |
Number | Date | Country |
---|---|---|
2004-193979 | Jul 2004 | JP |
WO 0167233 | Sep 2001 | WO |
WO 2013003631 | Jan 2013 | WO |
Entry |
---|
NPL1—Title: Interposed Request Routing for Scalable Network Storage; OSDI Proceedings 2000; Dept. Computerscience; Duke University; by Anderson et al. |
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. |
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. |
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. |
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. |
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. |
Lubonski, M., et al., An Adaptation Architecture to Improve User-Perceived QoS of Multimedia Services for Enterprise Remote Desktop Protocols. NG12005, pp. 149-156, 2005. |
International Search Report and Written Opinion in PCT/US2012/044711 dated Jan. 25, 2013. |
International Preliminary Report on Patentability for PCT/US2012/044711 dated Jan. 7, 2014. |
International Search Report and Written Opinion in PCT/US2012/044716 dated Sep. 25, 2012. |
International Preliminary Report on Patentability for PCT/US2012/044716 dated Jan. 7, 2014. |