JP2000353093A - Distribution method for stub and skeleton - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide development environment which automates from generation to transfer of a stub and a skeleton by enabling the stub or the skeleton to be transferred to a client or a server and putting stub and skeleton generation and transfer in one command. SOLUTION: It is made possible to automatically transfer a stub to a client and a skeleton to a server when a user generates the stub and the skeleton from a server program by adding a function for transferring to the server and the client to a program 102 for generating the stub and the skeleton and, furthermore, equipping transfer data 110 which describe a client name of a transferred party of the stub and a name of the server of a transferred party of the skeleton. This method consists of a stub/skeleton generation part 102, a transferred party interpretation part 103 and a stub/skeleton transfer part 104. Moreover, a transfer data change part is possessed.

Description

DETAILED DESCRIPTION OF THE INVENTION

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for generating and transferring stubs and skeletons, which are objects for communication between a server and a client.

2. Description of the Related Art Conventionally, a mechanism for calling a method of an object on a different machine requires a server object and its skeleton on the server side, and a stub of the server object on the client side. The stub and skeleton are generated by a generation command and transferred. It was transferred to each server machine and client machine by the command.

In the above prior art, when a server program is changed, the server program is compiled to generate a server object, a stub, and a skeleton, and then the stub is transferred to the client and the server object and the skeleton are transferred to the server. The user had to do the work. This requires knowing the name of the client or server to which the stub or skeleton is to be transferred. If the client name or server name is changed due to a network configuration change, this change is notified to the user. Otherwise, if the server program needs to be changed, there is a problem that stubs and skeletons cannot be transferred correctly. The purpose of the present invention is to set the transfer destination of the stub and skeleton by the system administrator,
By storing the setting items as data on the development machine, it is possible to transfer stubs and skeletons to clients and servers, and by combining stub and skeleton generation and transfer into one command, transfer from stub and skeleton generation to transfer The purpose of the present invention is to provide a stub and skeleton distribution method that performs automation up to the point.

According to the present invention, there is provided a program for generating a stub and a skeleton, which is provided with a function of transferring the stub and the skeleton to a server and a client. By providing transfer data that describes the server name that is the transfer destination of the server on the development machine, when the user generates a stub and skeleton from the server program, it is possible to automatically transfer the stub to the client and the skeleton to the server Things. The present invention includes a stub / skeleton generating unit, a destination interpreting unit, and a stub / skeleton transferring unit. Further, it has a transfer data update unit.

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a block diagram showing the system of the present invention. Server program development environment 10
0, a development machine 105, a system administrator environment 200, a system administrator machine 204, a server machine 300, a client machine 400, and a network 500.
In the system administrator environment 200, the system configuration (change of the server name, addition of a new server object, etc.) is changed by the system change unit 201. When the system is changed and the server name is changed, the server name (1) 602 shown in FIG. 2 is changed to the server name. When the name of the client is changed, the client name (1) 604 is changed to the client name.
If the directory where the skeleton is stored is changed, the server-side storage directory name (1) 6
Change 03. If the directory in which the stub is stored is changed, the client-side storage destination directory name (1) 605 is changed. This process is performed by the transfer data updating unit 202. When the change of the transfer data 205 is completed, the system administrator transfers the transfer data 205 to the transfer data 110 of the development machine 105 by the transfer data transfer unit 203. In the server program development environment 100, the server program 106 is changed by the developer in the server program changing unit 101, and the server program 106 is compiled and the server object 107 is changed.
Is generated. The command unit 111 reads the server object 107, stubs and the skeleton creation unit 102,
Transfer destination interpretation unit 103, stub / skeleton transfer unit 104
Execute Each processing content of the command unit 111 is as follows. The stub / skeleton generating unit 102 generates a stub 108 and a skeleton 109 from the changed server object 107. The transfer interpretation unit 103 reads the transfer data 110 and sets the object name (1) 601 to the server object 107 and the server object 107.
And the skeleton 109 to be transferred to the server machine 300 and the stub 108 to be transferred to the client machine 400 are determined.
Transfer destination server machine 300 from server name (1) 602 of transfer data 110 and server-side storage directory name (1)
603 is determined and the client name of the transfer data 110 is determined.
(1) The transfer destination client machine 400 and the client side storage destination directory name (1) 605 are determined from 604. Server machine 3 in stub / skeleton transfer unit 104
00, the skeleton 109 is transferred to the skeleton 302 of the server-side storage directory (1) 603, and the server machine 3
The server object 107 is transferred to the server object 301 of the server-side storage destination directory (1) 603 of 00. Further, the stub 108 is transferred to the stub 402 of the client-side storage destination directory (1) 605 of the client machine 400. Next, FIG. 2 will be described. FIG. 2 describes the format of transfer data stored in the magnetic disks of the development machine 105 and the system administrator machine 204. The object name (1) 601 indicates the server object 107 to be transferred. The stub 108 and the skeleton 109 to be transferred are determined from the object name (1) 601. A server name (1) 602 indicates the transfer destination server machine 300, and determines a skeleton transfer destination server name. The server-side storage destination directory name (1) 603 indicates the storage directory of the skeleton on the server name (1) 602. client name
(1) 604 indicates a transfer destination client name (1) 400 for determining a transfer destination client name of the stub. Client-side storage directory name (1) 605
Indicates a stub storage directory on the client name (1) 604. The above parameter group and one object correspond one-to-one, and a plurality of transfer destinations can be specified for a plurality of objects. An EOF 606 is described at the end of all data. Next, FIG. 3 will be described. FIG. 3 shows an example in which the method of the server object 701 is called from the client object 704. Client object 704 is server object 70
When the first method is called, first, the stub 703 of the server object is called. The server object stub 703 transmits a method call of the server object 701 from the client object 704 to the communication infrastructure 7.
It has a function to convert to a type that can be used in 08. The stub 703 of the server object converts the method call of the server object 701 from the client object 704 into a type usable in the communication board 708 and sends it to the communication board 708. Skeleton 702 of server object
Has a function of converting a type usable in the communication infrastructure 708 into a type for calling a method of the server object 701. The skeleton 702 of the server object is obtained from the type received from the communication infrastructure 708 from the server object 701.
Is converted to the method call type, and the method of the server object 701 is called. Server object 701
When the execution of the method is completed, the return value of the resulting method is returned through the path of the server object skeleton 702, the communication infrastructure 708, the stub 703 of the server object, and the client object 704.

According to the present invention, the generation and transfer of stubs and skeletons can be integrated into one tool, and the generation and transfer of stubs and skeletons can be automated collectively by creating data describing the destination machine. There is.
By doing so, the developer of the application using the stub and skeleton can concentrate on the application program development without being conscious of the transfer destination of the stub and skeleton.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a system configuration of the present invention.

FIG. 2 is a diagram showing a format of transfer data;

FIG. 3 is a diagram for explaining a server method call from a client.

[Explanation of symbols]

100: User program development environment, 101: Server program change unit, 102: Stub and skeleton generation unit
103: transfer destination resolution unit, 104: stub, skeleton transfer unit, 105: development machine, 106: server program, 107: server object, 108: stub, 1
09: skeleton, 110: transfer data, 111: command section, 200: system administrator environment, 201: system change section, 202: transfer data update section, 203: transfer data transfer section, 204: system administrator machine, 205:
Transfer data, 300: server machine, 301: server object, 302: skeleton, 400: client machine, 401: client object, 402
… Stub, 500… network, 701… server object, 702… server object stub, 703
.., Server object skeleton, 704, client object, 705, server object method call, 706, server machine, 707, client machine, 708, communication infrastructure.

Claims (3)

[Claims] In a system in which a method of a server object is called from a client object in a network environment, a stub and a skeleton that provide a communication function are generated from the server object, and the stub and the skeleton are collectively transferred. A stub and skeleton distribution method characterized by the following. 2. The stub and skeleton distribution method according to claim 1, wherein the stub and skeleton are transferred by referring to transfer data in which a transfer destination is described in advance. 3. The stub and skeleton distribution method according to claim 2, wherein the transfer destination of the transfer data describing the stub and skeleton transfer destination is changed when the system configuration is changed.