Browser-independent and automatic apparatus and method for receiving, installing and launching applications from a browser on a client computer

• US 6,546,554 B1
• Filed: 01/21/2000
• Issued: 04/08/2003
• Est. Priority Date: 01/21/2000
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Violet, Scott R., Muller, Hans E., Schmidt, Rene W.
• Primary Examiner(s): Dam, Tuan Q.
• Assistant Examiner(s): DAS, CHAMELI
• Application Number:
  US09/489,583
• Time in Patent Office: 1,173 Days
• Field of Search: 717/171, 717/172, 717/173, 717/174, 717/177, 717/178, 717/175, 717/176, 717/121, 717/148, 709/203, 709/201, 707/513, 345/744, 345/748, 345/749, 345/760, 345/738, 345/854
• US Class Current: 717/176
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons

Abstract

A browser-independent and automatic apparatus and method for receiving, installing, and launching applications from a browser is described. According to one embodiment, a helper application is registered with a browser for a specified file type. When the browser encounters a link to a metafile of the specified file type, the file is downloaded to the requesting system and the helper application is invoked to process the downloaded file. In the context of a Java™ implementation, the downloaded metafile comprises a short launch file specification for a Java™ application, and specifies a classpath as a set of Universal Resource Identifiers (“URIs”), a Java™ Runtime Environment (“JRE”) version, security considerations, and other relevant information concerning the Java™ application to be executed. According to aspects of the present invention, automatic installation of Java™ archive files (“JAR files”) and class files based on the URIs from which they are downloaded is implemented, automatic updates and versioning are supported without any central administration, and automatic installation of multiple JREs is facilitated. Embodiments of the present invention may also be used to facilitate other applications, such as launching Java™ applications directly from a browser without having to execute them within the browser, and to tie web contents to the appropriate corresponding viewer application.

Claims

1. A browser-independent method for receiving, installing and launching an application from a browser on a client computer, comprising:

registering a helper application with a browser on said client computer for a specified file type, wherein said helper application is invoked when said browser encounters a link to a metafile of said specified file type;

receiving a copy of said metafile at said client computer and invoking said helper application using a copy of said metafile as an input parameter when said browser encounters a link to said metafile;

parsing a copy of said metafile to determine the components necessary to install and launch said application;

receiving a copy of any of said components not already installed on said client computer at said client computer;

installing said application on said client computer; and

launching said application independently of said browser.

2. The method according to claim 1, wherein said application is a java application and said metafile comprises a short launch file specification for said java application.

3. The method according to claim 2, wherein said metafile specifies a classpath as a set of Universal Resource Identifiers (“

URIs”

), a Java Runtime Environment (“

JRE”

) version, and security information concerning said java application.

4. The method according to claim 3, further comprising automatic installation of java archive files and class files based on the Universal Resource Identifiers (“

URIs”

) from which said java archive files and class files are received.

5. The method according to claim 3, wherein said application can be automatically updated to a newer version.

6. The method according to claim 3, further comprising automatic installation of a JRE if said JRE is specified by said metafile and said JRE is not installed on said client computer.

7. A browser-independent method for receiving, installing and launching an application from a browser on a client computer, comprising:

installing a browser capable of registering helper applications for specified mime-types or file types on said client computer;

installing one or more runtime environments for said application on said client computer;

installing a helper application capable of parsing a metafile describing the components necessary to install and execute said application on said client computer;

activating a link to said metafile;

receiving a copy of said metafile at said client computer and invoking said helper application using a copy of said metafile as an input parameter;

parsing a copy of said metafile to determine the components necessary to install and launch said application;

receiving a copy of any of said components not already installed on said client computer at said client computer;

installing said application on said client computer; and

launching said application independently of said browser.

8. The method according to claim 7, wherein said application is a java application and said metafile comprises a short launch file specification for said java application.

9. The method according to claim 7, wherein said metafile specifies a classpath as a set of Universal Resource Identifiers (“

URIs”

), a Java Runtime Environment (“

JRE”

) version, and security information concerning said java application.

10. The method according to claim 9, further comprising automatic installation of java archive files and class files based on the Universal Resource Identifiers (“

URIs”

) from which said java archive files and class files are received.

11. The method according to claim 9, wherein said application can be automatically updated to a newer version.

12. The method according to claim 9, further comprising automatic installation of a JRE if said JRE is specified by said metafile and said JRE is not installed on said client computer.

13. A browser-independent method for receiving and installing a runtime environment from a browser on a client computer, comprising:

registering a helper application with a browser on said client computer for a specified file type, wherein said helper application is invoked when said browser encounters a link to a metafile of said specified file type;

receiving a copy of said metafile at said client computer and invoking said helper application using a copy of said metafile as an input parameter when said browser encounters a link to said metafile;

parsing a copy of said metafile to determine whether said runtime environment is necessary to launch said application; and

receiving and installing said runtime environment at said client computer if said runtime environment is determined to be necessary to launch said application and said runtime environment is not already installed on said client computer.

14. The method according to claim 13, wherein said runtime environment is a Java Runtime Environment (“

JRE”

).

15. The method according to claim 13, wherein said runtime environment can be automatically updated to a newer version.

16. The method according to claim 13, wherein said runtime environment is received at said client computer from a trusted source.

17. The method according to claim 13, wherein said runtime environment is received at said client computer from a trusted source using trustworthy means.

18. A browser-independent method for transmitting an application to a client computer, comprising:

configuring a HTTP server to transmit a specified mime-type when a metafile describing the components necessary to install and launch said application is transmitted by said HTTP server to said client computer; and

transmitting said metafile having said mime-type to said client computer in response to a HTTP request received from said client computer; and

transmitting some or all of said components to said client computer in response to one or more requests received from said client computer.

19. The method according to claim 18, wherein said application is a java application and said metafile comprises a short launch file specification for said java application.

20. The method according to claim 18, wherein said metafile specifies a classpath as a set of Universal Resource Identifiers (“

URIs”

), a Java Runtime Environment (“

JRE”

) version, and security information concerning said java application.

21. A browser-independent apparatus for receiving, installing and launching an application from a browser on a client computer, comprising:

means for registering a helper application with a browser on said client computer for a specified file type, wherein said helper application is invoked when said browser encounters a link to a metafile of said specified file type;

means for receiving a copy of said metafile at said client computer and invoking said helper application using a copy of said metafile as an input parameter when said browser encounters a link to said metafile;

means for parsing a copy of said metafile to determine the components necessary to install and launch said application;

means for receiving a copy of any of said components not already installed on said client computer at said client computer;

means for installing said application on said client computer; and

means for launching said application independently of said browser.

22. The apparatus according to claim 21, wherein said application is a java application and said metafile comprises a short launch file specification for said java application.

23. The apparatus according to claim 22, wherein said metafile specifies a classpath as a set of Universal Resource Identifiers (“

URIs”

), a Java Runtime Environment (“

JRE”

) version, and security information concerning said java application.

24. The apparatus according to claim 23, further comprising automatic installation of java archive files and class files based on the Universal Resource Identifiers (“

URIs”

) from which said java archive files and class files are received.

25. The apparatus according to claim 23, wherein said application can be automatically updated to a newer version.

26. The apparatus according to claim 23, further comprising means for automatic installation of a JRE if said JRE is specified by said metafile and said JRE is not installed on said client computer.

27. A browser-independent apparatus for receiving, installing and launching an application from a browser on a client computer, comprising:

means for installing a browser capable of registering helper applications for specified mime-types or file types on said client computer;

means for installing one or more runtime environments for said application on said client computer;

means for installing a helper application capable of parsing a metafile describing the components necessary to install and execute said application on said client computer;

means for activating a link to said metafile;

means for receiving a copy of said metafile at said client computer and invoking said helper application using a copy of said metafile as an input parameter;

means for parsing a copy of said metafile to determine the components necessary to install and launch said application;

means for receiving a copy of any of said components not already installed on said client computer at said client computer;

means for installing said application on said client computer; and

means for launching said application independently of said browser.

28. The apparatus according to claim 27, wherein said application is a java application and said metafile comprises a short launch file specification for said java application.

29. The apparatus according to claim 27, wherein said metafile specifies a classpath as a set of Universal Resource Identifiers (“

URIs”

), a Java Runtime Environment (“

JRE”

) version, and security information concerning said java application.

30. The apparatus according to claim 29, further comprising automatic installation of java archive files and class files based on the Universal Resource Identifiers (“

URIs”

) from which said java archive files and class files are received.

31. The apparatus according to claim 29, wherein said application can be automatically updated to a newer version.

32. The apparatus according to claim 29, further comprising means for automatic installation of a JRE if said JRE is specified by said metafile and said JRE is not installed on said client computer.

33. A browser-independent apparatus for receiving and installing a runtime environment from a browser on a client computer, comprising:

means for registering a helper application with a browser on said client computer for a specified file type, wherein said helper application is invoked when said browser encounters a link to a metafile of said specified file type;

means for receiving a copy of said metafile at said client computer and invoking said helper application using a copy of said metafile as an input parameter when said browser encounters a link to said metafile;

means for parsing a copy of said metafile to determine whether said runtime environment is necessary to launch said application; and

means for receiving and installing said runtime environment at said client computer if said runtime environment is determined to be necessary to launch said application and said runtime environment is not already installed on said client computer.

34. The apparatus according to claim 33, wherein said runtime environment is a Java Runtime Environment (“

JRE”

).

35. The apparatus according to claim 33, wherein said runtime environment can be automatically updated to a newer version.

36. The apparatus according to claim 33, wherein said runtime environment is received at said client computer from a trusted source.

37. The apparatus according to claim 33, wherein said runtime environment is received at said client computer from a trusted source using trustworthy means.

38. A browser-independent apparatus for transmitting an application to a client computer, comprising:

means for configuring a HTTP server to transmit a specified mime-type when a metafile describing the components necessary to install and launch said application is transmitted by said HTTP server to said client computer; and

means for transmitting said metafile having said mime-type to said client computer in response to a HTTP request received from said client computer; and

means for transmitting some or all of said components to said client computer in response to one or more requests received from said client computer.

39. The apparatus according to claim 38, wherein said application is a java application and said metafile comprises a short launch file specification for said java application.

40. The apparatus according to claim 38, wherein said metafile specifies a classpath as a set of Universal Resource Identifiers (“

URIs”

), a Java Runtime Environment (“

JRE”

) version, and security information concerning said java application.

41. A browser-independent apparatus for receiving, installing and launching an application from a browser on a client computer, comprising:

a runtime environment for said application; and

a helper application that is invoked by a browser when said browser encounters a link to a metafile describing the components necessary to install and launch said application, wherein said helper application comprises logic for parsing a copy of said metafile to determine the components necessary to install and launch said application, logic for obtaining a copy of any of said components not already installed on said client computer, logic for installing said application on said client computer, and logic for launching said application independently of said browser.

42. The apparatus according to claim 41, wherein said application is a java application, said runtime environment is a Java Runtime Environment (“

JRE”

), and said metafile comprises a short launch file specification for said java application.

43. The apparatus according to claim 42, wherein said metafile specifies a classpath as a set of Universal Resource Identifiers (“

URIs”

), a Java Runtime Environment (“

JRE”

) version, and security information concerning said java application.

44. The apparatus according to claim 43, wherein said helper application further comprises logic for automatic installation of java archive files and class files based on the Universal Resource Identifiers (“

URIs”

) from which said java archive files and class files are obtained.

45. The apparatus according to claim 43, wherein said helper application further comprises logic for automatically updating said application to a newer version.

46. The apparatus according to claim 43, wherein said helper application further comprises logic for automatically installing a JRE if said JRE is specified by said metafile and said JRE is not installed on said client computer.

47. A browser-independent apparatus for receiving and installing a runtime environment from a browser on a client computer, comprising:

a helper application that is invoked by a browser when said browser encounters a link to a metafile describing the components necessary to install and launch an application dependent on said runtime environment, wherein said helper application comprises logic for parsing a copy of said metafile to determine which version of said runtime environment is specified, logic for determining whether said version of said runtime environment is installed on said client computer, logic for obtaining a copy of said version of said runtime environment if said version of said runtime environment is not already installed on said client computer, and logic for installing said version of said runtime environment on said client computer independently of said browser.

48. The apparatus according to claim 47, wherein said runtime environment is a Java Runtime Environment (“

JRE”

).

49. The apparatus according to claim 47, wherein said helper application further comprises logic for automatically updating said runtime environment to a newer version.

50. The apparatus according to claim 47, wherein said helper application further comprises logic for obtaining said runtime environment from a trusted source using trustworthy means.

51. A browser-independent apparatus for transmitting an application to a client computer, comprising:

a HTTP server configured to transmit a specified mime-type when a metafile describing the components necessary to install and launch said application is transmitted by said HTTP server to said client computer; and

a metafile having said mime-type, wherein said metafile is transmitted by said HTTP server to said client computer in response to a HTTP request received from said client computer.

52. The apparatus according to claim 51, wherein said application is a java application and said metafile comprises a short launch file specification for said java application.

53. The apparatus according to claim 52, wherein said metafile specifies a classpath as a set of Universal Resource Identifiers (“

URIs”

), a Java Runtime Environment (“

JRE”

) version, and security information concerning said java application.

54. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a browser-independent method for receiving, installing and launching an application from a browser on a client computer, the method comprising:

registering a helper application with a browser on said client computer for a specified file type, wherein said helper application is invoked when said browser encounters a link to a metafile of said specified file type;

receiving a copy of said metafile at said client computer and invoking said helper application using a copy of said metafile as an input parameter when said browser encounters a link to said metafile;

parsing a copy of said metafile to determine the components necessary to install and launch said application;

receiving a copy of any of said components not already installed on said client computer at said client computer;

installing said application on said client computer; and

launching said application independently of said browser.

55. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a browser-independent method for receiving, installing and launching an application from a browser on a client computer, the method comprising:

installing a browser capable of registering helper applications for specified mime-types or file types on said client computer;

installing one or more runtime environments for said application on said client computer;

installing a helper application capable of parsing a metafile describing the components necessary to install and execute said application on said client computer;

activating a link to said metafile;

receiving a copy of said metafile at said client computer and invoking said helper application using a copy of said metafile as an input parameter;

parsing a copy of said metafile to determine the components necessary to install and launch said application;

receiving a copy of any of said components not already installed on said client computer at said client computer;

installing said application on said client computer; and

launching said application independently of said browser.

56. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a browser-independent method for receiving and installing a runtime environment from a browser on a client computer, the method comprising:

registering a helper application with a browser on said client computer for a specified file type, wherein said helper application is invoked when said browser encounters a link to a metafile of said specified file type;

receiving a copy of said metafile at said client computer and invoking said helper application using a copy of said metafile as an input parameter when said browser encounters a link to said metafile;

parsing a copy of said metafile to determine whether said runtime environment is necessary to launch said application; and

receiving and installing said runtime environment at said client computer if said runtime environment is determined to be necessary to launch said application and said runtime environment is not already installed on said client computer.

57. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform a browser-independent method for transmitting an application to a client computer, the method comprising:

configuring a HTTP server to transmit a specified mime-type when a metafile describing the components necessary to install and launch said application is transmitted by said HTTP server to said client computer; and

transmitting said metafile having said mime-type to said client computer in response to a HTTP request received from said client computer; and

transmitting some or all of said components to said client computer in response to one or more requests received from said client computer.