METHOD AND SYSTEM FOR EXTENDING CLIENT-SERVER SOFTWARE TO ADDITIONAL CLIENT PLATFORMS

• US 20020013808A1
• Filed: 09/30/1998
• Published: 01/31/2002
• Est. Priority Date: 09/30/1998
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: HOCHBERG, AVISHAI HAIM, CASE, DOUGLAS ROBERT
• Granted Patent: US 6,847,987 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

A method and system for servicing a request using a server is disclosed. The server is capable of communicating with a client. The client provides a plurality of functions. The method and system include providing a thin client for providing the request. The thin client is compatible with at least one client platform. The method and system also include providing a listening program. The listening program is for listening for the request from the thin client and invoking the client. A portion of the plurality of functions may be provided on the at least one client platform. In another aspect, the thin client is further compatible with a plurality of client platforms. The request may be from one of the plurality of client platforms.

Claims

1. A system for servicing a request using a server, the server being capable of communicating with a client, the client providing a plurality of functions, the system comprising

a thin client for providing the request, the thin client being compatible with at least one client platform;

and

a listening program for listening for the request from the thin client, and invoking the client;

wherein a portion of the plurality of functions may be provided on the at least one client platform.

2. The system of claim 1 wherein the client utilizes a first format and the thin client utilizes a second format;

and

wherein the listening program further converts between the first format and the second format.

3. The system of claim 1 wherein the thin client is further compatible with a plurality of client platforms;

and

wherein the request may be from one of the plurality of client platforms.

4. The system of claim 1 wherein the client further includes at least one application program interface (API);

and

wherein the listening program invokes the client through the at least one API.

5. The system of claim 1 wherein the at least one client platform are capable of including at least one file;

and wherein the plurality of functions further include a migrate or a recall of the at least one file.

6. The system of claim 1 wherein the at least one client platform are capable of including at least one file;

and wherein plurality of functions include a backup or a restore of the at least one file.

7. The system of claim 6 wherein the at least one file includes data;

and

wherein the thin client further ensures that the data exists in the second format and provides the data to the listening program.

8. The system of claim 1 wherein the at least one client platform are capable of including at least one file;

and wherein the plurality of functions further include archiving the at least one file.

9. The system of claim 8 wherein the plurality of functions further include retrieving the at least one file.

10. The system of claim 1 wherein the client and the server both reside on a server machine.

11. The system of claim 1 wherein the thin client is executed by a browser.

12. The system of claim 3 wherein the thin client is implemented in JAVA.

13. The system of claim 1 wherein the thin client is implemented in C.

14. A method for servicing a request using a server, the server being capable of communicating with a client, the client providing a plurality of functions, the method comprising the steps of:

providing a thin client, the thin client for providing the request, the thin client being compatible with at least one client platform; and

providing a listening program, the listening program for listening for a communication from the thin client, and invoking the client;

wherein a portion of the plurality of functions may be provided on the at least one client platform.

15. The method of claim 14 wherein the client utilizes a first format and the thin client utilizes a second format;

and

wherein the listening program further converts between the first format and the second format.

16. The method of claim 14 wherein the thin client is further compatible with a plurality of client platforms;

and

wherein the portion of the plurality of functions may be provided on the plurality of client platforms.

17. The method of claim 14 wherein the client further includes at least one application program interface (API);

and

wherein the listening program invokes the client through the at least one API.

18. The method of claim 14 wherein the at least one client platform includes at least one file;

and wherein the plurality of functions further include a migrate or a recall of the at least one file.

19. The method of claim 14 wherein the at least one client platform includes at least one file;

and wherein the plurality of functions further include a backup or a restore of the at least one file.

20. The method of claim 19 wherein the at least one file includes data;

and

wherein the thin client further ensures that the data exists in the second format and provides the data to the listening program.

21. The method of claim 14 wherein the at least one client platform are capable of including at least one file;

and wherein the plurality of functions further include archiving the at least one file.

22. The method of claim 21 wherein the plurality of functions further include retrieving the at least one file.

23. The method of claim 16 wherein the thin client providing step further includes the step of:

providing the thin client implemented in JAVA.

24. The method of claim 14 wherein the thin client providing step further includes the step of:

providing the thin client implemented in C or C++.

28. The computer-readable medium of claim 24 wherein the thin client is further compatible with a plurality of client platforms;

and

wherein the request may be from one of the plurality of client platforms.

29. The computer-readable medium of claim 28 wherein the client further includes at least one application program interface (API);

and wherein the instruction for invoking the client further includes instructions for;

using the listening program to invoke the client through the at least one API.

25. A method for servicing a request for a function performed by a server, the server capable of communicating with a client, the client providing a plurality of functions and utilizing a first format, the method comprising the steps of:

(a) utilizing a thin client compatible with a plurality of client platforms to provide the request, the thin client using a second format;

(b) listening for the request on a listening program coupled with the thin client;

(c) converting from the first format to the second format;

(d) invoking the client by the listening program; and

(e) communicating between the client and the server to service the request;

wherein a portion of the plurality of functions may be provided on the plurality of client platforms.

26. The method of claim 25 wherein the client further includes at least one application program interface (API) and wherein the client invoking step (d) further includes the step of:

(d1) using the listening program to invoke the client through the at least one API.

27. A computer-readable medium having a program for servicing a request using a server, the server being capable of communicating with a client, the client providing a plurality of functions, the program containing instructions for:

providing a thin client compatible with at least one client platform; and

providing a listening program for listening for a communication from the thin client, and invoking the client;

wherein a portion of the plurality of functions may be provided on the at least one client platform.

30. A computer-readable medium containing a program for servicing a request for a function performed by a server, the server being capable of communicating with a client, the client providing a plurality of functions, the program including instructions for:

listening for the request from a thin client, the thin client being compatible with a plurality of client platforms;

invoking the client to allow the client and server to communicate to service the request; and

providing the thin client with a response from the service of the request.

31. A computer-readable medium containing a program for servicing a request for a function performed by a server, the server being capable of communicating with a client, the client providing a plurality of functions, the program including instructions for:

providing the request to a listening program, the request capable of being from a plurality of client platforms, the client communicating with the server to service the request, the listening program capable of invoking the client; and

receiving a reply from the listening program, the reply being in response to the service of the request;

wherein a portion of the plurality of functions may be provided on the plurality of client platforms.