Bridge for a client-server environment

• US 5,862,328 A
• Filed: 09/06/1996
• Issued: 01/19/1999
• Est. Priority Date: 09/15/1995
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Colyer, Adrian Mark
• Primary Examiner(s): Trammell, James P.
• Assistant Examiner(s): Smithers, Matthew
• Application Number:
  US08/709,087
• Time in Patent Office: 865 Days
• Field of Search: 395/703, 395/700, 395/200, 395/200.09, 395/680, 395/200.51, 395/200.33, 395/3
• US Class Current: 709/203
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

A software bridge is introduced between a client and a server in a client-server distributed computing environment. The bridge presents the interface of a server to a client and the interface of a client to a server. The bridge is used for monitoring or logging of requests and associated data flowing between the client and the server, useful for example in problem determination. The bridge is also used for workload balancing between servers. It can further be used to reduce network connectivity between clients and servers. All of these advantages can be achieved without any modifications to existing client or server code.

Claims

1. A bridge for use between a client and a server in a distributed object-oriented computer system, the bridge having an interface to the client that corresponds to the interface of a server and an interface to the server that corresponds to the interface of a client the bridge being transparently inserted between the client and the server so that the client and the server respectively communicate through the bridge as though directly interfacing with the server and the client respectively.

2. A bridge as claimed in claim 1 wherein:

said client and said server operate asynchronously;

said bridge is derived from a client and a server by inheritance;

said bridge overrides methods inherited from said server to record the name of the client making the request and to forward the request to said server; and

said bridge overrides methods inherited from said client to forward reply parameters to said client.

3. A bridge as claimed in claim 1 wherein:

said client and said server operate synchronously;

said bridge is derived from a server by inheritance; and

said bridge overrides methods inherited from said server to invoke said method on said server and to return reply parameters to said client.

4. A bridge as claimed in claim 1 further comprising means to monitor and log requests between the client and the server and data associated with such requests.

5. A bridge as claimed in claim 1 further comprising means for performing workload balancing between servers.

6. A bridge as claimed in claim 5 wherein said means for performing workload balancing measures response times and directs client requests to servers in response to said measured response time.

7. A bridge as claimed in claim 1 wherein:

said distributed object-oriented computer system comprises m clients and n servers (where n and m are integers greater than or equal to

     2), each of said m clients being able to request services from each of said m servers;

said bridge is connected to said m clients and said n servers; and

said bridge thereby reducing the number of connections between said m clients and said n servers from n*m to n+m.

8. A bridge as claimed in any one of claim 1 to claim 7 wherein said distributed object-oriented computer system is a CORBA compliant system.

9. A bridge as claimed in claim 8 wherein said distributed object-oriented computer system uses DSOM class libraries.

10. A distributed object-oriented computer system comprising one or more servers, one or more clients and a bridge as claimed in any one of claim 1 to claim 7.

11. A method of operating a distributed client-server computer system comprising the steps of:

defining an interface, for a bridge, such that the interface to a client corresponds to the interface of a server and the interface to a server corresponds to the interface of a client; and

transparently inserting said bridge between said client and said server;

wherein the client and the server respectively communicate through the bridge as though directly interfacing with the server and the client respectively.

12. A method as claimed in claim 11 wherein said client and said server operate asynchronously, and said step of defining an interface comprises:

deriving said interface to a client from a server by inheritance;

overriding methods inherited from said server to record the name of the client making the request and to forward the request to said server;

deriving said interface to a server from a client by inheritance; and

overriding methods inherited from said client to forward reply parameters to said client.

13. A method as claimed in claim 12 wherein said client and said server operate synchronously and said step of defining an interface comprises:

deriving said interface to a client from a server by inheritance; and

overriding methods inherited from said server to invoke said method on said server and to return reply parameters to said client.

14. A computer program product in a computer readable memory for operating a distributed client-server computer system, the computer program product comprising:

means for defining an interface, for a bridge, such that the interface to a client corresponds to the interface of a server and the interface to a server corresponds to the interface of a client; and

means for transparently inserting said bridge between said client and said server;

wherein the client and the server respectively communicate through the bridge as though directly interfacing with the server and client respectively.

15. A computer program product as claimed in claim 14 wherein said client and said server operate asynchronously, and said means for defining an interface comprises:

means for deriving said interface to a client from a server class by inheritance;

means for overriding methods inherited from said server class to record the name of the client making the request and to forward the request to said server;

means for deriving said interface to a server from a client class by inheritance; and

means for overriding methods inherited from said client class to forward reply parameters to said client.

16. A computer program product as claimed in claim 15 wherein said client and said server operate synchronously, and said means for defining an interface comprises:

means for deriving said interface to a client from a server class by inheritance; and

means for overriding methods inherited from said server class to invoke said method on said server and to return reply parameters to said client.