Process for simulating a server architecture from a client architecture

• US 5,822,563 A
• Filed: 12/30/1994
• Issued: 10/13/1998
• Est. Priority Date: 12/31/1993
• Status: Expired due to Fees

• Current Assignee: Bull Sas (Atos SE)
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Sitbon, Gerard, Freund, Hubert, Aydin, Alev, Bassier, Jean-Fran.cedilla.ois
• Primary Examiner(s): LOUIS JACQUES, JACQUES H
• Application Number:
  US08/366,909
• Time in Patent Office: 1,383 Days
• Field of Search: 395/500, 395/600, 395/650, 395/200.01, 395/200.03, 395/200.9, 395/200.16, 395/403, 395/404, 395/440, 395/200.18, 395/200.15, 395/474, 395/700 , 395/821, 395/894, 395/726, 395/157, 395/603, 395/684, 395/200.33, 395/200.67, 395/672, 395/200.49, 370/85.13, 370/60, 370/94.1, 340/825.34, 364/578, 380/4, 379/59, 379/60, 379/90, 379/111, 379/112, 379/114, 379/115, 379/67, 379/88, 379/89, 379/93.29
• US Class Current: 719/330
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching

Abstract

The invention relates to a process for simulating, in a network, a server architecture from a client architecture in a first machine (PS) for the execution of remote procedure calls (RPC sent by at least one machine with client architecture (CL). In this this process, the first machine (PS) initially sends an RPC call to a third machine with server architecture (RE) which is used as a relay machine between the first (PS) and the second (CL) machines, and this RPC call opens a communication context for the sequence of exchanges while the first machine (PS) blocks itself on standby for a return of the RPC call. When the second machine (CL) sends an RPC call which represents a predetermined function to be executed by the first machine (PS), this call is transmitted to the relay machine (RE) which, after recognizing the function, retransmits it to the first machine (PS) through a return of the blocked RPC call. The first machine (PS) then requests the input parameters of the function to be executed, which are known to the relay machine (RE), then executes the function upon their reception by furnishing the result as an output parameter to the second machine (CL) via the relay machine (RE).

Claims

1. A process for simulating, in a network, a server architecture from a client architecture in a first machine for the execution of remote procedure calls (RPC) sent by at least one second machine with client architecture, wherein the first machine initially sends an RPC call to a relay machine with server architecture which is used between the first and the second machines, said RPC call opening a communication context for a sequence of exchanges while said first machine blocks itself on said call on standby for its return, then when the second machine sends an RPC call which represents a predetermined function to be executed by the first machine, transmitting said RPC call to the relay machine, which after recognizing the function to be executed retransmits it to the first machine through a return of the blocked RPC call, the first machine then requesting the input parameters of the function to be executed which are present in the relay machine, then executing said function after receiving said input parameters, and finally furnishing the result as an output parameter to the second machine via the relay machine.

2. The simulation process according to claim 1, in which the machines are of the DCE type.

3. The simulation process according to claim 2, in which the remote procedure calls are of the standard DCE/RPC type.

4. The simulation process according to claim 2, in which any type of remote procedure call (RPC) is used for the communications between machines.

5. The simulation process according to claim 1, in which the remote procedure calls are of the standard DCE/RPC type.

6. The simulation process according to claim 1, in which any type of remote procedure call (RPC) is used for the communications between machines.

7. A process for simulating, in a network, a server architecture in a first machine for the execution of remote procedure calls (RPC) sent by at least one second machine with client architecture, comprising sending an RPC call from the first machine to a first execution unit of a third machine, defined as a relay machine, with server architecture which is used between the first and second machines, said RPC call opening a communication context for a sequence of exchanges while said first machine blocks itself on said call on standby for its return, searching by the second machine in a directory of a naming service for the address of the function to be executed, then, when the second machine sends an RPC call which represents a predetermined function to be executed by the first machine to a second execution unit in the relay machine, said second execution unit puts itself on standby for a wake-up signal and blocks the second machine to said RPC call (2) after having sent a wake-up signal to the first execution unit on standby, transmitting said call to the relay machine which, after recognizing the function to be executed, re-transmits said call to the first machine through a return of the blocked RPC call, then sending a RPC call from the first machine to the first execution unit in the relay machine via an interprocess to request input parameters of the function to be executed which are present in the second execution unit of the relay machine, then executing said function to be executed after receiving said input parameters, and finally furnishing the result as an output parameter to the second machine via the execution unit in the relay machine.

8. The simulation process according to claim 7, in which the machines are of the DCE type.

9. The simulation process according to claim 8, in which the remote procedure calls are of the standard DCE/RPC type.

10. The simulation process according to claim 8, in which any type of remote procedure call (RPC) is used for the communications between machines.

11. The simulation process according to claim 7, in which the remote procedure calls are of the standard DCE/RPC type.

12. The simulation process according to claim 11, in which any type of remote procedure call (RPC) is used for the communications between machines.