Client intermediation of server applications

• US 6,138,148 A
• Filed: 06/18/1998
• Issued: 10/24/2000
• Est. Priority Date: 06/18/1998
• Status: Expired due to Term

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Lipkin, Efrem
• Primary Examiner(s): Maung, Zarni
• Assistant Examiner(s): Farahi, Farzaneh
• Application Number:
  US09/099,489
• Time in Patent Office: 859 Days
• Field of Search: 395/200, 705/40, 709/201, 709/206, 709/209
• US Class Current: 709/206
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• 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/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

One embodiment of the present invention provides a method and an apparatus for providing a client-side intermediary that communicates with an application on a second server computer system. The method operates by receiving a composite message at a client computer system from a first server computer system, and examining type information from the composite message. This type information specifies how the composite message is formatted, and can be used to select an application that is capable of processing the composite message. The method uses the type information to look up a network address of the application residing on the second server computer system. This address is used to forward the composite message to the application on the second server computer system. The above embodiment can be implemented within a browser on the client computer system, or within a separate application on the client computer system. A return communication can be facilitated by receiving a return composite message at the client computer system from the second server computer system, and examining type information from the return composite message. This type information is used to look up an address of a source application on the network, and this address is used to forward the return composite message to the source application.

Claims

1. A method for providing a client-side intermediary that redirects communications directed to an application on a client computer system to a remote application on a second server computer system, comprising:

receiving, at the client computer system, a composite message from a first server computer system directed to the application on the client computer system;

examining type information from the composite message, the type information specifying how the composite message is formatted and thereby implicitly specifying applications that are capable of processing the composite message;

using the type information to lookup the address of the remote application one the second server computer system that is capable processing the composite message;

wherein the lookup is performed using at least one table that translates the type information into an address of the remote application on the second server computer system;

using the address to engage an access mechanism through which the remote application on the second server computer system can be accessed; and

forwarding the composite message and subsequent composite messages of the same type to the remote application on the second server computer system using the access mechanism so that the remote application appears to exist on the client computer system in spite of the fact that the remote application actually exists on the second server computer system.

2. The method of claim 1, further comprising:

receiving, at the client computer system, a return composite message from the second server computer system;

examining return type information from the return composite message the return type information specifying how the return composite message is formatted and thereby implicitly specifying applications that are capable of processing the return composite message;

using the return type information to engage a source access mechanism through which a source application on the first server computer system can be accessed; and

forwarding the return composite message to the source application on the first server computer system using the source access mechanism.

3. The method of claim 1, wherein:

receiving the composite message includes receiving the composite message at a browser on the client computer system; and

using the type information to look up the access mechanism includes using MIME-type information to look up an entry in a helper application table in the browser, the entry in the helper application table including the address of the application on the second server computer system.

4. The method of claim 1, wherein:

receiving the composite message includes receiving the composite message at a client-side application on the client computer system; and

wherein

forwarding the composite message to the remote application to the second server computer system includes forwarding the composite message from the client-side application to the remote application on the second server computer system.

5. The method of claim 1, wherein the type information includes Multipurpose Internet Mail Extensions (MIME) type information.

6. The method of claim 1, wherein the type information is specified by a filename extension for a file associated with the composite message.

7. The method of claim 1, wherein forwarding the composite message to the remote application on the second server computer system, includes repackaging the composite message.

8. The method of claim 1, wherein the address includes a Universal Resource Locator (URL), and wherein engaging the access mechanism includes referencing the remote application on the second server computer system through the URL.

9. The method of claim 1, wherein the remote application implements an electronic wallet.

10. A method for providing a client-side intermediary that redirects communications directed to an application on a client computer system to a remote application on a second server computer system, comprising:

receiving, at the client computer system, a composite message from a first server computer system directed to the application on the client computer system;

examining type information from the composite message, the type information specifying how the composite message is formatted according to the Multipurpose Internet Mail Extensions (MIME) standard and thereby implicitly specifying applications that are capable of processing the composite message;

using the type information to lookup the a Universal Resource Locator (URL) for the remote application one the second server computer system that is capable processing the composite message;

wherein the lookup is performed using at least one table that translates the type information into an URL for the remote application on the second server computer system;

using the URL to engage an access mechanism through which the remote application on the second server computer system can be accessed; and

forwarding the composite message to the remote application on the second server computer system using the access mechanism;

wherein the remote application on the second server computer system implements an electronic wallet.

11. A computer readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for providing a client-side intermediary that redirects communications directed to an application on a client computer system to a remote application on a second server computer system, method comprising:

receiving, at the client computer system, a composite message from a first server computer system directed to the application on the client computer system;

examining type information from the composite message, the type information specifying how the composite message is formatted and thereby implicitly specifying applications that are capable of processing the composite message;

using the type information to lookup the address of the remote application one the second server computer system that is capable processing the composite message;

wherein the lookup is performed using at least one table that translates the type information into an address of the remote application on the second server computer system;

using the address to engage an access mechanism through which the remote application on the second server computer system can be accessed; and

forwarding the composite message and subsequent composite messages of the same type to the remote application on the second server computer system using the access mechanism so that the remote application appears to exist on the client computer system in spite of the fact that the remote application actually exists on the second server computer system.

12. An apparatus that provides a client-side intermediary that redirects communications directed to an application on a client computer system to a remote application on a second server computer system, comprising:

a receiving mechanism that receives a composite message from a first server computer system directed to the application on the client computer system;

a reading mechanism, in communication with the receiving mechanism, that reads type information from the composite message, the type information specifying how the composite message is formatted and thereby implicitly specifying applications that are capable of processing the composite message;

an access mechanism, in communication with the reading mechanism, that uses the type information to trigger an access to the remote application on the second server computer system;

wherein the access mechanism is configured to use the type information to lookup the address of the remote application one the second server computer system that is capable processing the composite message;

wherein the lookup is performed using at least one table that translates the type information into an address of the remote application on the second server computer system; and

a forwarding mechanism, in communication with the receiving mechanism, that forwards the composite message and subsequent composite messages of the same type to the remote application on the second server computer system using the access mechanism so that the remote application appears to exist on the client computer system in spite of the fact that the remote application actually exists on the second server computer system.

13. The apparatus of claim 12, wherein:

the receiving mechanism is configured to receive a return composite message from the second server computer system;

the reading mechanism is configured to read return type information from the return composite message the return type information specifying how the return composite message is formatted and thereby implicitly specifying applications that are capable of processing the return composite message;

the access mechanism is configured to use the return type information to trigger an access to a source application on the first server computer system; and

the forwarding mechanism is configured to forward the composite message to the source application on the first server computer system using the access mechanism.

14. The apparatus of claim 12, further comprising a browser on the client computer system, the browser including the receiving mechanism, the reading mechanism, the access mechanism and the forwarding mechanism.

15. The apparatus of claim 12, further comprising a client-side application on the client computer system, the client-side application including the receiving mechanism, the reading mechanism, the access mechanism and the forwarding mechanism.

16. The apparatus of claim 12, wherein the type information includes Multipurpose Internet Mail Extensions (MIME) type information.

17. The apparatus of claim 12, wherein the type information is specified by a filename extension of a file associated with the composite message.

18. The apparatus of claim 12, wherein the forwarding mechanism is configured to repackage the composite message.

19. The apparatus of claim 12, wherein the address includes a Universal Resource Locator (URL), and wherein the access mechanism references the remote application on the second server computer system through the URL.

20. The apparatus of claim 12, wherein the remote application implements an electronic wallet.

21. A computer system that provides a client-side intermediary that redirects communications directed to an application on a client computer system to a remote application on a second server computer system, comprising:

a client computer system;

a first server computer system;

a network coupled to the first server computer system, the second server computer system and the client computer system;

a receiving mechanism that receives a composite message from a first server computer system directed to the application on the client computer system;

a reading mechanism, in communication with the receiving mechanism, that reads type information from the composite message, the type information specifying how the composite message is formatted and thereby implicitly specifying applications that are capable of processing the composite message;

an access mechanism, in communication with the reading mechanism, that uses the type information to trigger an access to the remote application on the second server computer system;

wherein the access mechanism is configured to use the type information to lookup the address of the remote application one the second server computer system that is capable processing the composite message;

wherein the lookup is performed using at least one table that translates the type information into an address of the remote application on the second server computer system; and

a forwarding mechanism, in communication with the receiving mechanism, that forwards the composite message and subsequent composite messages of the same type to the remote application on the second server computer system using the access mechanism so that the remote application appears to exist on the client computer system in spite of the fact that the remote application actually exists on the second server computer system.

22. An apparatus that provides a client-side intermediary that redirects communications directed to an application on a client computer system to a remote application on a second server computer system, comprising:

a receiving means, for receiving a composite message from a first server computer system directed to the application on the client computer system;

a reading means, in communication with the receiving means, for reading type information from the composite message, the type information specifying how the composite message is formatted and thereby implicitly specifying applications that are capable of processing the composite message;

an access means, in communication with the reading means, that uses the type information to trigger an access to the remote application on the second server computer system;

wherein the access means uses the type information to lookup the address of the remote application one the second server computer system that is capable processing the composite message;

wherein the lookup is performed using at least one table that translates the type information into an address of the remote application on the second server computer system; and

a forwarding means, in communication with the receiving means, for forwarding the composite message and subsequent composite messages of the same type to the remote application on the second server computer system using the access means so that the remote application appears to exist on the client computer system in spite of the fact that the remote application actually exists on the second server computer system.

23. A method for providing a client-side intermediary that redirects communications directed to an application on a client computer system to a remote application on a second server computer system, comprising:

receiving commands from a user at a client computer system;

allowing the user to interact with a first server computer system through the client computing system;

in response to interactions by the user, receiving a communication directed to the client computer system from the first server computer system;

examining the communication to determine what type of information is contained in the communications and thereby implicitly specifying applications that are capable of processing the composite message;

using the type information to lookup the address of the remote application one the second server computer system that is capable processing the composite message;

wherein the lookup is performed using at least one table that translates the type information into an address of the remote application on the second server computer system;

using the address to engage an access mechanism through which the remote application on the second server computer system can be accessed; and

if the type of information in the communication can be processed by the remote application on a second server computer system, forwarding the communication to the remote application on the second server computer system so that the remote application appears to exist on the client computer system in spite of the fact that the remote application actually exists on the second server computer system.

24. The method of claim 23, wherein the remote application on the second server computer system implements an electronic wallet.

25. The method of claim 23, wherein forwarding the composite message to the remote application on the second server computer system includes repackaging the composite message.

26. The method of claim 25, wherein repackaging the composite message makes the composite message appear to originate from the client computing system.

27. The method of claim 25, wherein repackaging the composite message makes the composite message appear to originate from a third server computing system.