Hosting an application in one of a plurality of execution environments

• US 7,475,408 B2
• Filed: 11/18/2003
• Issued: 01/06/2009
• Est. Priority Date: 02/27/2003
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Watt, Murray E., Alcazar, Mark A.
• Primary Examiner(s): An; Meng-Ai
• Assistant Examiner(s): Seye; Abdou K
• Application Number:
  US10/715,707
• Publication Number:
  US 20040172443A1
• Time in Patent Office: 1,876 Days
• Field of Search: 719/330, 709/200
• US Class Current: 719/330
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Described is a mechanism for executing a hosted application in either a browser-execution environment or as a standalone application. The invention provides a mechanism that enables hosting code in either of plural hosting environments. Briefly stated, code is created that executes in a common execution environment. That execution environment can be either owned by a browser or not. When the code is launched, a host sniffer component determines from an indicator within the code which hosting environment is appropriate. Based on that indicator, the code is launched in the appropriate hosting environment. The appropriate hosting environment may be either browser hosted or standalone.

Claims

1. A client device a computer-readable storage medium storing computer-executable components, the client device comprising:

a first hosting environment;

a second hosting environment;

a code host mechanism resident within the client device; and

a body of code received by the client device to be hosted in either the first or the second hosting environment,

wherein the body of code is essentially the same for the first hosting environment and the second hosting environment,

wherein the code host mechanism evaluates the body of code to determine the presence of a particular function call within the body of code, wherein the function, when compiled, results in a byte signature within an executable code, the byte signature being indicative of the function call,

wherein;

in the event that the body of code includes the particular function call, the code host mechanism operates to cause the body of code to be hosted in the first hosting environment;

in the event that the body of code does not include the particular function call, then the code host mechanism operates to cause the body of code to be hosted in second hosting environment.

2. The client device of claim 1, wherein the body of code comprises an executable file.

3. The client device of claim 1, wherein the first hosting environment comprises a browser hosting environment.

4. The client device of claim 3, wherein the second hosting environment comprises a standalone hosting environment.

5. The client device of claim 1, wherein the first hosting environment comprises a standalone hosting environment.

6. The client device of claim 1, wherein the function comprises a public static function that, when called, results in the body of code being hosted in the first hosting environment.

7. The client device of claim 6, wherein the public static function is called from within a public class included in the body of code.

8. A computer-readable storage medium storing computer-executable components for hosting an executable file in a client device, the computer-executable components comprising:

a default hosting environment in the client device;

an alternate hosting environment in the client device;

an executable file for hosting within the client device, comprising;

a first portion including computer-executable instructions operative for performing operations; and

a second portion including a function call which, when invoked, is operative to cause the executable file to be executed in the alternative hosting environment, wherein the function, when compiled, results in a byte signature within the executable code, the byte signature being indicative of the function call ;

and

a handler component, executing in either the default hosting environment or the alternate hosting environment, to facilitate the launch of the executable file in either the default hosting environment or the alternate hosting environment, wherein;

in the event that the executable file invokes the function, the executable file is launched in the alternative hosting environment;

in the event that the executable file does not invoke the function, the executable file is launched in the default hosting environment.

9. The computer-readable storage medium recited in claim 8, wherein the alternative hosting environment comprises a browser hosted environment and the default hosting environment comprises a standalone hosting environment.

10. The computer-readable storage medium recited in claim 8, wherein the alternative hosting environment comprises a browser hosted environment.

11. The computer-readable storage medium recited in claim 8, wherein the alternative hosting environment comprises a standalone hosting environment.

12. A computer-executable method of hosting an executable file in a hosting environment, the method comprising:

providing a default hosting environment for the executable file;

providing an alternative hosting environment for the executable file;

providing a shell environment that is operative to launch the executable file in the default hosting environment common to other executable files;

providing a function that, if called by the executable file, is operative to cause the executable file to be launched in the alternative hosting environment, wherein the function, when compiled, results in a byte signature within the executable file, the byte signature being indicative of the function call; and

invoking a handler component within the shell environment, wherein the handler component determines if the executable file is configured to call the function, wherein in the event the handler component determines that the executable file is configured to call the function, the handler component facilitates the launch of the executable file, wherein;

in the event that the executable file calls the function, the executable file is launched in the alternative hosting environment;

in the event that the executable file does not call the function, the executable file is launched in the default hosting environment,

wherein a determination of whether to launch the executable file in either the default hosting environment or the alternative hosting environment is based substantially exclusively on the executable file being configured to call the function.

13. The computer-executable method recited in claim 12, wherein the default hosting environment comprises a standalone hosting environment.

14. The computer-executable method recited in claim 13, wherein the alternative hosting environment comprises a browser hosted environment.

15. The computer-executable method recited in claim 12, wherein the default hosting environment comprises a browser hosted environment.

16. The computer-executable method recited in claim 15, wherein the alternative hosting environment comprises a standalone hosting environment.

17. The computer-executable method recited in claim 12, wherein the function comprises a public static function.

18. The computer-executable method recited in claim 12, wherein the executable file is configured for execution in either the default hosting environment or the alternative hosting environment.