Startup of container applications

• US 8,539,073 B1
• Filed: 12/29/2006
• Issued: 09/17/2013
• Est. Priority Date: 12/29/2006
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Dayan, Tal
• Primary Examiner(s): BEHARRY, NOEL R
• Application Number:
  US11/648,324
• Time in Patent Office: 2,454 Days
• Field of Search: 709/225
• US Class Current: 709/225
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A container application is a native application that allows a web based application to access a computer'"'"'s system resources and windowing system. Web based applications are downloaded from application servers and run inside container applications. If a container application is associated with a window, then the web based application can alter or control many, or all, aspects of the container application'"'"'s content area and meta user interfaces (UIs). A container startup module stored in a non-volatile memory can launch container application instances that automatically download and run web based applications. As such, an entire web based user environment can be easily launched.

Claims

1. A method comprising:

providing a web based application over at least one network to a container application running on a computer comprising at least one system resource;

wherein a non-volatile memory on the computer stores data comprising a container startup module, wherein the container startup module specifies the web based application such that the container application automatically downloads the web based application upon startup of the container application;

wherein the container startup module is used to launch the container application, and the container application, when launched, maintains a content area and a meta user interface (UI) area separate from the content area; and

wherein the web based application being provided can run inside the container application to access the at least one system resource, and the web-based application can alter or control an appearance of the content area and a functionality of the meta UI area maintained by the container application when run on the computer, wherein selection of the meta UI area causes the functionality of the meta UI area to function.

2. The method of claim 1 wherein at least one container security datum is used to authenticate the container application.

3. The method of claim 1 wherein the non-volatile memory is a pluggable non-volatile memory.

4. The method of claim 1 wherein at least one permission datum is used to limit access from the web based application to the at least one system resource.

5. The method of claim 1 wherein the non-volatile memory is a pluggable non-volatile memory and wherein the computer automatically uses the container startup module to launch the container application when the pluggable non-volatile memory is mounted.

6. The method of claim 1, the web based application additionally alters or controls the appearance of the meta UI area.

7. The method of claim 1, the web based application is a non-native application.

8. A method comprising:

providing, on a first computer, a web based application to a container application running on a second computer comprising at least one system resource;

wherein a non-volatile memory stores data comprising a container startup module and the container application, wherein the container startup module specifies the web based application such that the container application automatically downloads the web based application upon startup of the container application;

wherein the second computer uses the container startup module to launch the container application; and

wherein the web based application uses the container application to access the at least one system resource on the second computer

wherein the container startup module is used to launch the container application, and the container application, when launched, maintains a content area and a meta user interface (UI) area separate from the content area; and

wherein the web based application being provided can run inside the container application to access the at least one system resource, and the web based application can alter or control an appearance of the content area and a functionality of the meta UI area maintained by the container application when run on the second computer, wherein selection of the meta UI area causes the functionality of the meta UI area to function.

9. The method of claim 8 wherein at least one container security datum is used to authenticate the container application.

10. The method of claim 8 wherein the non-volatile memory is a pluggable non-volatile memory.

11. The method of claim 8 wherein at least one permission datum is used to determine which of the at least one system resource the web based application is allowed to access.

12. The method of claim 8 wherein the non-volatile memory is a pluggable non-volatile memory and wherein the computer automatically uses the container startup module to launch the container application when the pluggable non-volatile memory is mounted.

13. The method of claim 8:

wherein at least one container security datum is used to authenticate the container application;

wherein at least one permission datum is used to determine which of the at least one system resource the web based application is allowed to access;

wherein the non-volatile memory is a pluggable non-volatile memory;

wherein the computer automatically uses the container startup module to launch the container application; and

wherein the container startup module specifies the web based application such that the container application automatically downloads the web based application.

14. A system for instantiating a container application, comprising:

a container application that maintains a content area and a meta user interface (UI) area separate from the content area comprising at least one system resource, wherein the container application comprises;

a container startup module configured to launch the container application on a computer, wherein the container startup module specifies a web based application to download automatically upon startup of the container application,

wherein the web based application being served can ran inside the container application to access the at least one system resource, and the web-based application can alter or control an appearance of the content area and a functionality of the meta UI area maintained by the container application, wherein selection of the meta UI area causes the functionality of the meta UI area to function.

15. The system of claim 14, wherein the web based application is specified on a pluggable non-volatile memory.