JPH086771A - Program update managing system and update managing method in program update system - Google Patents

Abstract

PURPOSE:To provide a program update managing system capable of updating one program from plural terminals simultaneously and an update managing method in a program update system. CONSTITUTION:The programs for which a readout request is issued from the terminals 10, 20 are read out from a program library 50, and they are stored in a temporary storage part 41 transiently. After that, when the update requests of the program are issued from the terminals 10, 20, an update history acquiring means 32 compares the program for which the update request is issued with the program before update stored transiently, and acquires the update history of the program. It is judged whether or not the update part of an acquired update history is stored in an update history storage part 43 as the update history, and it is judged that the update of the program is valid when no update history is stored, and also, a program update means 33 rewrites the update part of the program stored transiently.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program update management system and an update management method in the program update system, and more particularly to a program update management system and a program update system capable of updating a program stored in a program library from a plurality of terminals. Update management method in.

[0002]

2. Description of the Related Art Conventionally, this kind of update management system has been used to compare the version numbers of programs and prevent erroneous updates of programs. For example, JP-A-3-21
Japanese Patent No. 6733 discloses a source update management system in which an update history file is stored in association with a program name, and the update history file is referenced when updating the program to update the program at an appropriate time. More specifically,
This system is composed of an update history file, an update target program, an update management program, and a program editor. Then, the version number, reason for update, update items, etc. are saved by associating the program name with the update history file, and this is referred to when updating the program to start the program editor when appropriate and update and By saving the contents and referring to them, erroneous updates are prevented.

[0003]

In such a conventional source update management system, since it is not taken into consideration the case where a plurality of terminals simultaneously make an update request, it is said that a plurality of terminals cannot simultaneously modify a program. There was a flaw. Further, since the update information is manually input into the editor, there is a drawback that the processing for it is troublesome and an error is likely to occur.

It is an object of the present invention to solve the above-mentioned drawbacks and provide a program update management system capable of simultaneously updating one program from a plurality of terminals and an update management method in the program update system. It is another object of the present invention to provide a program update management system and an update management method in the program update system, which can easily and surely store update information used for updating a program.

[0005]

In order to achieve the above object, the present invention is a program update management system in which a program stored in a program library can be updated from a plurality of terminals. Program temporary storage means for reading a program from the program library and temporarily storing the program, and a program requested to be updated by the terminal and a program before update stored in the program temporary storage means are compared to update the program. An update history acquisition unit that acquires a history, an update history storage unit that stores the update history acquired by the update history acquisition unit only when the update of the program is determined to be appropriate, and an update history acquisition unit that acquires the update history Determine whether the update location of the update history exists in the update history storage means While it considered appropriate update of the program in the absence, and the configuration and program update means for rewriting the program update stored in the temporary storage means.

According to another aspect, in a program update management system in which a program stored in a program library can be updated from a plurality of terminals, a temporary storage section for temporarily storing the program and an update history of the program. And a storage device having an update history storage unit for storing the program, a program requested to be read by the terminal from the program library, stored in the temporary storage unit, and passed from the temporary storage unit to the terminal. The temporary storage means, the update history acquisition means for acquiring the update history of the program by comparing the program requested to be updated by the terminal with the program before the update stored in the temporary storage portion, and the update of the program is appropriate. Only when it is determined that the update history acquired by the update history acquisition means The update history is stored in the update history storage unit, and it is determined whether or not the update location of the update history acquired by the update history acquisition unit is present in the update history storage unit. And an update management device having a program update means for rewriting the update location of the program stored in the temporary storage unit.

According to another update management method in the program update system for achieving the above object, a read request is issued from the terminal in the update management method in the program update system in which the program stored in the program library can be updated from a plurality of terminals. The program that has been updated from the program library and temporarily stores it, and the program that has been requested to update from the terminal and the temporarily stored program before update are compared to obtain the update history of the program. And a step of storing the acquired update history only when it is determined that the update of the program is appropriate, and a determination is made as to whether or not the update location of the acquired update history is stored as an update history and stored. If it is judged that the update of the program is appropriate when there is not A has a configuration and a step of rewriting the program update that the temporarily stored.

[0008]

In the present invention, the program requested to be read by the terminal is read from the program library and temporarily stored. After that, when a program update request is issued from the terminal, the program requesting the update is compared with the temporarily stored program before update, and the update history of the program is acquired. Then, it is determined whether or not the acquired update location of the update history is stored as the update history, and if not stored, the update of the program is determined to be valid, and the temporarily stored update location of the program is rewritten. Further, the update history acquired only when the update of the program is judged to be appropriate is stored.

[0009]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 1 is a block diagram showing the configuration of a program update management system that is an embodiment to which the present invention is applied. 1, in the program update management system, a plurality of terminals 10 and 20, an update management device 30 that manages a program to be updated, a storage device 40 that temporarily stores information such as a program to be updated, and a plurality of devices. And a program library 50 for storing the programs of the above.

Each of the terminals 10 and 20 can update the program stored in the program library 50. Thereby, for example, the same program can be distributed and developed. Here, the case where the number of terminals 10 and 20 is two is shown, but the number of terminals may be three or more.

The update management device 30 operates under program control, and includes temporary storage means 31 for temporarily storing the update target program requested by the terminals 10 and 20 in the storage device 40, and the storage device 40. The update history acquisition means 32 for acquiring the update history and the program update means 33 for updating the program stored in the storage device 40 are provided.

The storage device 40 includes a temporary storage unit 41 for temporarily storing the program requested to be read by the terminals 10 and 20, and an update history storage unit for storing the update history of the program stored in the temporary storage unit 41. And 42.

Next, the operation of the program update management system of this embodiment configured as described above will be described with reference to the flowcharts of FIGS. When the terminal 1 or 2 requests the update management device 30 to read the program of the program library 50, the temporary storage unit 31 refers to the temporary storage unit 41 (step 2).
01), it is checked whether or not it has been referred to, that is, whether or not there is a requested program in the temporary storage unit 41 (step 202).

When it can be referred to, that is, the temporary storage unit 41
If there is the requested program, the temporary storage means 31 delivers the program stored in the temporary storage unit 41 to the terminal 10 or the terminal 20. That is, the terminal 10 or the terminal 20 reads the program from the temporary storage unit 41 (step 203).

On the other hand, if it cannot be referred to, that is, if there is no requested program in the temporary storage unit 41, the temporary storage unit 31 copies the requested program from the program library 50 to the temporary storage unit 41 (step 2).
04), the program copied to the temporary storage unit 41 is delivered to the terminal 10 or the terminal 20. That is, the terminal 10 or the terminal 20 reads the program from the temporary storage unit 41 as described above (step 203).

When the terminal 10 or 20 that has read the program requests the update management apparatus 30 to update the program (step 205), the update management apparatus 30 operates as follows. First, the update history acquisition unit 32 refers to the update history of the update history storage unit 42 (step 206) and determines whether or not the reference was successful (step 207).

The update history acquisition means 32 includes an update history storage unit 4
When the update history of 2 can be referred to, the program update means 3
3 acquires the update history, that is, the update location between the program requested to be updated and the program in the temporary storage unit 41 (step 208), and determines the validity of the update (step 2).
09). The validity of the update means whether or not the acquired update location exists in the update history storage unit 42. That is, when the update location does not exist in the update history storage unit 42, the update location is a location that has not been updated by another terminal, so it is appropriate for the terminal to update this location. On the other hand, when the update location exists in the update history storage unit 42, the update location is already updated by another terminal, so it is not appropriate for the terminal to update this location.

When the update is judged to be valid (step 210), the acquired update history is stored in the update history storage unit 4
2 is additionally stored, and only the updated portion of the program stored in the temporary storage unit 41 is rewritten (step 211). Thereby, for example, even when the terminal 20 tries to update the portion updated by the terminal 10, the content updated by the terminal 20 first is protected. Further, for example, when the terminal 20 attempts to update a part different from the part updated by the terminal 10, the part can be rewritten. Therefore, a plurality of terminals can update the same program such as correction. Furthermore, since the latest program is written in the temporary storage unit 41 from the update history acquisition means 32, step 203
The latest program can be delivered to the terminal at.

Thereafter, it is judged whether or not there are 0 terminals which are referring to the program requested to be updated (step 21).
2). If there are no terminals that are referring to the program requested to be updated, there is no more terminal on the system to update the program, and the program updating means 33 stores the program in the temporary storage unit 41 into the program library 50. Then, the program in the temporary storage unit 41 is erased (step 213), and the process ends.

Even when the update history acquisition means 32 cannot refer to the update history in the update history storage section 42 in step 207, the program update means 33 transfers the program in the temporary storage section 41 to the program library 50 and temporarily stores it. The program in the storage unit 41 is erased (step 2
13), the process ends. If it is determined in step 210 that the update is not appropriate, the process ends without updating.

Although the present invention has been described with reference to the preferred embodiments, the present invention is not necessarily limited to the above embodiments.

[0022]

As described above, according to the program update management system and the update management method in the program update system of the present invention, when there is a program update request from the terminal, the program update history is acquired and acquired. Since it is configured to judge whether the update location of the update history is already stored as the update history and update the program only when it is not stored, it is possible to update the part updated by one terminal with another terminal. Even if you do, the contents updated earlier by other terminals are protected. Further, when another terminal attempts to update a part updated by a certain terminal, that part can be rewritten. Therefore,
The same program can be updated on multiple terminals at the same time.

Further, since the update history acquired when the update of the program is judged to be appropriate is stored, it is possible to easily and surely save the update information used for updating the program. .

Further, since the latest program is written in the temporary storage unit based on the acquired update history, the latest program can be delivered to the terminal.

[Brief description of drawings]

FIG. 1 is a block diagram showing a configuration of a program update management system showing an embodiment of the present invention.

FIG. 2 is a flowchart illustrating the operation of the program update management system of FIG.

3 is a flowchart illustrating an operation of the program update management system of FIG.

[Explanation of symbols]

 10 terminal 20 terminal 30 update management device 31 temporary storage means 32 update history acquisition means 33 program update means 40 storage device 41 temporary storage section 42 update history storage section 50 program library

Claims (3)

[Claims] 1. A program update management system capable of updating a program stored in a program library from a plurality of terminals, wherein a program temporarily requested to be read from the terminal is temporarily stored by being read from the program library. The storage means compares the program requested to be updated by the terminal with the program before update stored in the program temporary storage means, and acquires the update history of the program, and the update of the program is appropriate. Only when it is determined that the update history storage means for storing the update history acquired by the update history acquisition means, whether the update location of the update history acquired by the update history acquisition means exists in the update history storage means Is judged,
A program update management system comprising: a program update unit that determines that the update of the program is appropriate when it does not exist, and rewrites the update location of the program stored in the temporary storage unit. 2. A program update management system capable of updating a program stored in a program library from a plurality of terminals, and a temporary storage section for temporarily storing the program and an update history for storing the update history of the program. A storage device having a storage unit; and a temporary storage unit that reads out a program requested to be read from the terminal from the program library, stores the program in the temporary storage unit, and transfers the program from the temporary storage unit to the terminal. Update history acquisition means for acquiring the update history of the program by comparing the program requested to be updated by the terminal with the program before update stored in the temporary storage unit, and when the update of the program is judged to be appropriate Only the update history acquired by the update history acquisition means is stored in the update history storage unit. It is determined whether or not the update location of the update history acquired by the update history acquisition means exists in the update history storage unit, and if it does not exist, the update of the program is determined to be valid and stored in the temporary storage unit. And an update management device having a program updating means for rewriting the updated part of the stored program. 3. An update management method in a program update system capable of updating a program stored in a program library from a plurality of terminals, wherein a program requested to be read from the terminal is read from the program library and temporarily read. A step of storing, a step of comparing the program requested to be updated by the terminal with the temporarily stored program before update, and obtaining an update history of the program; and when the update of the program is judged to be appropriate. Only the step of storing the acquired update history, determining whether or not the update location of the acquired update history is stored as an update history, and if not stored, determine that the update of the program is valid, Step of rewriting the updated part of the temporarily stored program Update management method in the program update system characterized by comprising.