Software application delivery and launching system

• US 10,114,660 B2
• Filed: 02/22/2011
• Issued: 10/30/2018
• Est. Priority Date: 02/22/2011
• Status: Active Grant

• Current Assignee: Julian Michael Urbach
• Original Assignee: Julian Michael Urbach
• Inventors: Urbach, Julian Michael
• Primary Examiner(s): Rahman, Sm
• Application Number:
  US13/031,747
• Publication Number:
  US 20120215831A1
• Time in Patent Office: 2,807 Days
• Field of Search: 709223, 709203, 719321
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons
• CPC Class Codes: G06F 9/44573 Execute-in-place [XIP]
• CPC Class Codes: G06F 9/44584 Portable applications, i.e. making applications self-contained, e.g. U3 standard
• CPC Class Codes: G06F 9/44594 Unloading
• CPC Class Codes: G06F 9/4484 Executing subprograms

Abstract

One embodiment allocates a first virtual memory; receives executable code of a first piece of software; writes the executable code of the first piece of software directly into the first virtual memory; marks the first virtual memory as executable; executes the executable code of the first piece of software directly from the first virtual memory; and downloads and executes executable code of a second piece of software as facilitated by the executable code of the first piece of software.

Claims

1. A method, comprising:

allocating, by a first computing device, a first virtual memory;

receiving, by the first computing device, executable code of a first software from a disparate second computing system via a communication network;

writing, by the first computing device, the executable code of the first software directly into the first virtual memory;

marking, by the first computing device, the first virtual memory as executable;

executing, by the first computing device, the executable code of the first software directly from the first virtual memory;

determining, by the first computing device via the execution of the first software, a specific version of a second software to be downloaded by identifying an operating system of the first computing device and identifying the specific version of the second software most compatible with the operating system;

allocating, by the first computing device via the execution of the first software, a second virtual memory for loading and executing the second software, the second virtual memory being distinct from the first virtual memory;

downloading, by the first computing device, executable code of the specific version of the second software for directly writing into the second virtual memory as facilitated by the downloaded executable code of the first software, the second software is disparate from the first software;

executing, by the first computing device, the executable code of the second software; and

de-allocating, by the first computing device, the first virtual memory distinct from the second virtual memory after the execution of the executable code of the first software is completed so that memory locations of the first virtual memory are released.

2. The method recited in claim 1, further comprising loading, by the first computing device, one or more shared libraries needed by the executable code of the first software.

3. The method recited in claim 1, wherein downloading and executing the executable code of the second software as facilitated by the executable code of the first software further comprises:

receiving, by the first computing device, the executable code of the second software;

extracting, by the first computing device, the executable code of the second software from a data stream;

writing, by the first computing device, the executable code of the second software directly into the second virtual memory;

marking, by the first computing device, the second virtual memory as executable; and

executing, by the first computing device, the executable code of the second software directly from the second virtual memory.

4. The method recited in claim 3, further comprising:

validating, by the first computing device, the executable code of the second software;

loading, by the first computing device, one or more first shared libraries needed by the executable code of the second software existing on the first computing device; and

downloading, by the first computing device, one or more second shared libraries needed by the executable code of the second software from a second computing device.

5. The method recited in claim 3, further comprising de-allocating, by the first computing device, the second virtual memory after the execution of the executable code of the second software is completed so that there is no trace of the executable code of the second software on the first computing device.

6. The method recited in claim 3, wherein:

the executable code of the second software is received from a third computing device.

7. The method recited in claim 3, wherein the executable code of the second software is embedded in the data stream.

8. A first system, comprising:

a memory comprising instructions executable by one or more processors; and

one or more processors coupled to the memory and operable to execute the instructions, the memory comprising instructions for;

allocating a first virtual memory;

receiving executable code of a first software from a disparate second computing system via a communication network;

writing the executable code of the first software directly into the first virtual memory;

marking the first virtual memory as executable;

executing the executable code of the first software directly from the first virtual memory;

determining via the execution of the first software, a specific version of a second software to be downloaded by identifying an operating system of the first system and identifying the specific version of the second software most compatible with the operating system;

allocating, via the execution of the first software, a second virtual memory for loading and executing the second software, the second virtual memory being distinct from the first virtual memory;

downloading executable code of the specific version of the second software for directly writing into the second virtual memory as facilitated by the downloaded executable code of the first software, the second software is disparate from the first software;

executing the executable code of the second software; and

de-allocating the first virtual memory distinct from the second virtual memory after the execution of the executable code of the first software is completed so that memory locations of the first virtual memory are released.

9. The system recited in claim 8, wherein the instructions further comprise instructions for loading one or more shared libraries needed by the executable code of the first software.

10. The system recited in claim 8, wherein the instructions for downloading and executing the executable code of the second software as facilitated by the executable code of the first software further comprises instructions for:

receiving the executable code of the second software;

extracting the executable code of the second software from the data stream;

writing the executable code of the second software directly into the second virtual memory;

marking the second virtual memory as executable; and

executing the executable code of the second software directly from the second virtual memory.

11. The system recited in claim 10, wherein the one or more processors are further operable when executing the instructions to:

validating the executable code of the second software;

loading one or more first shared libraries needed by the executable code of the second software existing on the first computing device; and

downloading one or more second shared libraries needed by the executable code of the second software from a second computing device.

12. The system recited in claim 10, the memory further comprising instructions for de-allocating the second virtual memory after the execution of the executable code of the second software is completed so that there is no trace of the executable code of the second software on the first computing device.

13. The system recited in claim 10, wherein:

the executable code of the second software is received from a third computing device.

14. The system recited in claim 10, wherein the executable code of the second software is received from the disparate second computing system.

15. The system recited in claim 10, wherein the executable code of the second software is embedded in a data stream.

16. One or more computer-readable storage media embodying software operable when executed by a first computer system to:

allocating a first virtual memory;

receiving executable code of a first software from a disparate second computing system via a communication network;

writing the executable code of the first software directly into the first virtual memory;

marking the first virtual memory as executable;

executing the executable code of the first software directly from the first virtual memory;

determining via the execution of the first software, a specific version of a second software to be downloaded by identifying an operating system of the first computer system and identifying the specific version of the second software most compatible with the operating system;

allocating, via the execution of the first software, a second virtual memory for loading and executing the second software, the second virtual memory being distinct from the first virtual memory;

downloading executable code of the specific version of the second software for directly writing into the second virtual memory as facilitated by the executable code of the first piece of software the second software is disparate from the first software;

executing the executable code of the second software; and

de-allocating the first virtual memory distinct from the second virtual memory after the execution of the executable code of the first software is completed so that memory locations of the first virtual memory are released.

17. The media recited in claim 16, further comprising instructions for:

loading one or more shared libraries needed by the executable code of the first software.

18. The media recited in claim 16, wherein the instructions for downloading and executing the executable code of the second software further comprise instructions for:

receiving the executable code of the second software;

extracting the executable code of the second software from the data stream;

writing the executable code of the second software directly into the second virtual memory;

marking the second virtual memory as executable; and

executing the executable code of the second software directly from the second virtual memory.

19. The media recited in claim 18, wherein the software is further operable when executed by the first computer system to:

validating the executable code of the second software;

loading one or more first shared libraries needed by the executable code of the second software existing on the first computing device; and

downloading one or more second shared libraries needed by the executable code of the second software from a second computing device.

20. The media recited in claim 18, further comprising instructions for de-allocating the second virtual memory after the execution of the executable code of the second software is completed so that there is no trace of the executable code of the second software on the first computing device.

21. The media recited in claim 18, wherein:

the executable code of the second software is received from a third computing device.

22. The media recited in claim 18, wherein the executable code of the second software is received from a second computing device.

23. A method, comprising:

receiving, by a first computing device, a request for an executable code of a first software from a client device, the executable code of the first software is configured to generate a request for the second software upon execution from a virtual memory of the client device;

transmitting, by the first computing device, the executable code of the first software to the client device in response to the request; and

configuring, by the first computing device, the client device to determine via the execution of the first software, a specific version of a second software to be downloaded by identifying an operating system of the client device and identifying the specific version of the second software most compatible with the operating system and to transmit a request for the specific second software via the executable code of the first software, the first software and the second software are configured to be respectively written and executed from a first and second virtual memories allocated on the client device and the second software is disparate from the first software;

providing, by the first computing device, a script configured to access a memory de-allocation function that de-allocates the first virtual memory of the client device allocated to the first software after the execution of the executable code of the first software is completed so that memory locations of the virtual memory on the client device are released.

24. The method of claim 23, further comprising:

receiving, by the first computing device, the request for the second software;

transmitting, by the first computing device, the executable code of the second software to the client device.

25. The method of claim 23, wherein configuring the client device to request for a second software further comprises:

configuring, by the first computing device, the client device to transmit a request for the second software to a third computing device that is disparate from the first computing device.