JP2000181863A - Client server system performing exclusion control - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a client sever system in which each client can efficiently perform edition working. SOLUTION: This client server system is provided with one server 1 and plural clients 3a, 3b,.... The storing part 5 of the server 1 is provided with a master file 9 in which data to be an edition object is written a graphic lock list 11 with which an object edited by any of the clients 3a, 3b,.... An operating part 7 has an edition log analyzing part 13 which analyzes the contents of an edition log file in which the log of edition processing performed by each client 3a, 3b,....

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a client-server system in which data managed by a server is edited by a plurality of clients, and more particularly to exclusive control and synchronization (unification) of edited data among a plurality of clients. About technology.

[0002]

2. Description of the Related Art It is assumed that a plurality of clients manually edit map data managed by a server (for example, a client A draws a road A and a client B draws a road B). The server must guarantee the consistency and uniformity of the editing process performed by a plurality of clients at the same time. For example, map data as shown in FIG. 1A is simultaneously provided from a server to a client P and a client Q, and the client P edits the road 100 as shown in FIG. As shown in FIG.
When the editing process of 0 is performed, in order to reflect the intention of each of the clients P and Q, the server displays the final result in FIG.
As shown in (D), it is necessary to notify the final result to each of the clients P and Q (synchronization, that is, unification of edited data). Also, the result of the editing performed by the client P and the result of the editing performed by the client Q are consistent,
In other words, there is no contradiction (for example, clients P, Q
However, it is necessary to ensure that the same road 100 is not edited in the same different form) (consistency of edited data).

[0003] Therefore, the server usually performs exclusive control such that all data is divided into a plurality of data groups and managed, and only one client is allocated to one data group. That is, the server locks the data group to be edited by the client P so that the client Q cannot edit the data group, releases the lock after the editing process of the client P ends, and sets the data group to be edited by the client Q. Make it possible.

[0004]

How to set the volume of the data group, which is one unit of the above-mentioned exclusive control, is a serious problem that affects the efficiency and ease of use of editing work. For example, in the case of a map editing application, all map images are meshed in advance at fixed longitude and latitude intervals,
Data groups of all figures, characters, and the like existing in one of the meshes can be used as one unit of exclusive control. However, in this case, when a client starts editing a figure that passes through a large number of meshes, such as a long-distance railway track, other clients cannot touch the numerous meshes until the editing is completed.
In effect, there is a problem that the work does not proceed. To solve this problem, the unit of the exclusive control may be an individual figure such as an individual road or building on the map (that is, it may be a minimum data that is not suitable for being divided and edited). However, if the unit of the exclusive control is reduced in such a manner, it becomes necessary to search the graphic data from the map data managed as a database. If the database is large, there is a problem that this search requires a lot of time, and the work efficiency becomes poor.

In the conventional client-server system, the client notifies the server of the contents of the editing process to be executed each time the client attempts to execute each editing process. The server determines whether or not to permit the notified editing process. If so, the server updates the database according to the content, and returns the update result to the client. The client receiving the update result reflects the update result on its own application. In addition, the server notifies each of the clients other than the client that has notified the above-described editing processing of the update result. Each of the clients receiving the update result reflects the update result on its own application. In short, the client only exchanges various notifications with the server, and substantially all editing processing is performed under the initiative of the server.

Therefore, when the number of clients increases, the amount of processing required of the server becomes enormous, and the load on the server becomes extremely large. In addition, since various requests and notifications are reciprocated between the client and the server before the result of the editing process is reflected on the application of each client, it takes a long time for the process, and the editing result is not reflected on other applications. There is a problem that it takes more time until the information is reflected on the client.

Accordingly, it is an object of the present invention to provide a client server system in which each client can perform an editing operation efficiently.

Another object of the present invention is to provide a client server system that reflects the work result of each client to another client at a higher speed.

[0009]

According to a first aspect of the present invention, there is provided a client-server system, wherein the server comprises: a lock list in which objects locked by any client being edited are registered; A notification unit that refers to the lock list and notifies each of the clients whether or not the object that the client wants to edit is locked. As a result, the client that has received the notification makes only the unlocked object editable.

[0010] In the client-server system according to the second aspect of the present invention, first, the server hands the object to the client, and the client freely edits the object received from the server. Then, a difference log indicating the contents of the change of the object due to the editing is generated and transmitted to the server. Then, the server reflects the content of the transmitted difference log in data managed by itself. As a result, the data can be synchronized between the server and the client.

In a preferred embodiment, the server transmits the transmitted difference log to a client other than the client that has transmitted the difference log, and the client that has received the difference log transmitted from the server has: Reflect the contents of the difference log to itself. As a result, data can be synchronized throughout the entire client-server system.

[0012]

FIG. 2 shows an overall configuration diagram of an editing system according to an embodiment of the present invention.

[0013] The client server system of the present invention comprises:
It includes one server computer 1 (hereinafter, referred to as a server) and a plurality of client computers 3a, 3b,... (Hereinafter, referred to as clients). The following description will be made on the assumption that these clients 3a, 3b,... Edit map data managed by the server 1.

The server 1 has a management unit 4, a storage unit 5, and a calculation unit 7 as functions of a server map editing application. The management unit 4 manages the relationship between each unit in the server 1 and manages the relationship between the server 1 and each of the clients 3a, 3b. For example, the management unit 4 gives various commands to each unit in the server 1, and sends and receives various notifications and data between the server 1 and each of the clients 3a, 3b,. For specific functions,
This will be described in the following description as necessary).

The storage unit 5 of the server 1 has a master file 9 in which map data (for example, map data for all over Japan) edited by the clients 3a, 3b,... Is stored. The management unit 4 is an area (for example, a range surrounded by specific latitude and longitude) requested by each of the clients 3a, 3b,.
Search for the map data in the master file 9
.. Or update the contents of the master file 9 based on the editing process performed by each of the clients 3a, 3b.

This client server system can perform exclusive control on the minimum unit of data that can be edited by the user. The data of the minimum unit is data that is not suitable for editing separately, for example, in the present embodiment for performing map editing, individual geographical objects such as roads, railroad tracks, and buildings on a map (hereinafter, object ). In a document creation application, one character data or one word data or one sentence data may be used. In a spreadsheet application, one cell data or one row data or one column data may be used. (In these cases, one character data, word data, or sentence data, or one cell data, row data, or column data is an object). Therefore, for example, if the client 3a
When the editing process is being performed on A, other clients (that is, clients other than the client 3a) cannot perform any editing process on the building A. The editing process can be freely performed as long as the editing process is not performed.

The storage unit 5 of the server 1 also has a graphic lock list 11 in which the graphic numbers of objects currently being edited by any of the clients 3a, 3b,... Are registered. Objects registered in the graphic lock list are objects that are currently locked and cannot be newly edited by other clients. Each figure on the map image in the master file 9 is assigned a unique figure number, and only the figure number of the locked object is registered in the figure lock list 11. Is not registered in the lock list 11. Management unit 1
When the client 3a, 3b... Inquires about whether or not a certain object can be locked, the client refers to the graphic lock list 11 to determine whether or not the inquired object is locked. The result is transmitted to the clients 3a, 3b,. When the client 3a, 3b,... Notifies the user of the addition or deletion of the locked object, the management unit 4 writes the figure number of the notified object in the figure lock list 11 or the like. , Delete it.

The operation unit 7 of the server 1 is provided with each client 3
Edit log analysis that analyzes the contents of the edit log file in which the difference log of the edit processing (data indicating the difference between the object before editing and the object after editing) sent from a, 3b,. It has a part 13. The management unit 4
The edit log file is received from the clients 3a, 3b,. Then, the edit log analysis unit 13 analyzes the contents of the edit log file, and the management unit 4 updates the data contents of the master file 9 based on the analyzed contents of the edit log file. Further, the management unit 4 has a function of distributing an edit log file received from one client (for example, the client 3a) to another client (that is, a client other than the client 3a) as it is. Then, each client to which the edit log file has been distributed analyzes the contents of the edit log file and reflects it on itself, so that the map data can be synchronized (unified) throughout the entire client server system.

Each of the clients 3a, 3b,... Has storage units 15a, 15b,..., Operation units 17a, 17b, and user interface units 18a, 18b.

Each of the clients 3a, 3b,... Receives a file of map data of a desired area from the server 1, and the storage unit 5 stores the file in a local file 19a, 1b.
9b... Or an edit log file to be described later.

The operation unit 17 of the clients 3a, 3b,...
have editing units 20a, 20b, and editing log creating units 21a, 21b,.

The editing units 20a, 20b... Write, move, deform, or delete roads and buildings on a map image in accordance with a user's instruction.
Various editing processes are performed on the data of the local files 19a, 19b.

The edit log creation units 21a, 21b... Create edit log files indicating the difference logs of the edit processing performed by the edit units 20a, 20b, and temporarily store the storage units 15a, 15b.
.. And transmitted to the server 1 as appropriate. Also, the edit log creation units 21a, 21b,... Analyze the contents of the edit log files distributed from the server 1, and reflect the analyzed contents in the local files 19a, 19b,. As a result, the map data can be synchronized (unified) throughout the entire client-server system.

The user interface units 18a, 18b ...
Is an interface to, for example, a keyboard, a mouse, a display, etc., displays a map editing screen on the display, and responds to a user's mouse operation or keyboard operation on this screen, and outputs a corresponding instruction to the editing unit 20.
a, 20b ...

FIG. 3 shows the flow of the editing process.

First, when the map editing application of the client 3a is started, the map editing application of the client 3a (hereinafter, simply referred to as the client 3a) logs in to the server 1, and the user attempts to edit the server 1 Request a map data file for the area where it is located (S1). The server 1 retrieves the requested file from the master file 9 (S2) and sends it to the client 3a (S3). The client 3a receives the file from the server 1, saves the received file as a local file 9a, and opens the local file 9a (S4). Then, the client 3a displays the map of the local file 9a on the map editing screen on the display (S5), so that the user can perform editing work.

Next, the user performs a predetermined operation on the map editing screen, and designates a desired object on the map as an object to be edited (S6). For example, it is conceivable that the user designates an object to be edited by operating the mouse, placing the cursor on a desired object on the display, and clicking the object.

When an object to be edited is designated, the client 3a sends the figure number of the designated object to the server 1 and inquires whether the object can be locked (S7). Management unit 4 of server 1
Determines whether or not the queried object can be locked with reference to the graphic lock list 11 (S
8). That is, the management unit 4 refers to the graphic lock list 11, and if the object inquired by the client 3a is on the graphic lock list 11, another client (a client other than the client 3a) is editing the object. The client 3a determines that the object cannot be edited because there is, and transmits the graphic number of the object and the fact that the object cannot be locked (that is, cannot be edited) to the client 3a as lock information (S10). Further, the management unit 4 determines that the client 3a can edit if the object inquired from the client 3a is not on the graphic lock list 11 because no other user is editing the object. The graphic number of the object is written in the graphic lock list 11 (S9), and the graphic number of the object and the fact that the object is lockable (that is, editable) is transmitted to the client 3a as lock information (S10). In the operation of confirming whether or not the lock is possible, the graphic lock list 11 that lists only the graphic numbers of the locked objects is used.
, It is possible to judge whether the lock is possible in an extremely short time as compared with a conventional method of searching for a data for which the lock is to be checked from a huge database.

The client 3a acquires the lock information from the server 1 (S11), and sets the lockable object to the editable mode (S12). For example, the client 3a indicates to the user that the lockable object can be edited by, for example, highlighting the lockable object on the display, and does not highlight the object that cannot be locked, and outputs a message such as “editable”. May be notified to the user by, for example, displaying on a display.

If the specified object can be edited, the user performs various editing operations on the object (S13). As this editing work, for example, it is conceivable to change, add, or delete the size, shape, color, and the like of buildings and roads on the map.

Next, the client 3a determines whether or not all editing work on the object being edited by the user has been completed (S14). For example, if the user is editing a certain building on the map, and the user specifies another object other than the building or performs an operation of ending the map editing application, the client 3 a It is determined that all editing work on the building has been completed. If editing is not finished,
Returning to S13, the user continues the editing work.

After the editing operation is completed, if the user wants to edit another object, the process returns to step S6 and specifies a new object. At the same time, the edit log creating unit 21a creates a log of the edit processing for one object that has just ended as an edit log file (S15). The log stored in the edit log file is a difference log indicating only the changes due to the edit processing, and is not a post-edit image log indicating the edited object itself. Then, the client 3a transmits the created edit log file to the server 1 (S1
6).

The management section 4 of the server 1 receives the transmitted edit log file (S17), and edits the edit log analysis section 13
Pass to. The edit log analysis unit 13 analyzes the contents of the edit log file (S18). The management unit 4 updates the contents of the master file 9 based on the analyzed contents (that is, updates the contents of the master file 9)
Updates the corresponding object to its edited state) (S1
9). Thereby, synchronization (unification) between the client 3a and the server 1 can be achieved. The management unit 4 also synchronizes (unifies) the entire client server system by distributing the edit log file to clients other than the client 3a (S22). This operation will be described with reference to FIG. 5 after step S22.

On the other hand, the client 3a determines to release the lock on the object for which the editing operation has been completed (S1).
9) Then, the figure number of the object and the fact that the lock has been released are transmitted to the server 1 as lock information (S20). The management unit 4 of the server 1 receives the lock information and deletes the graphic number of the object indicated by the lock information from the graphic lock list 11 (S22).

FIG. 4 shows a processing flow in which the client server system synchronizes data of the entire system following step S22 of FIG.

The management unit 4 of the server 1 sends a request to a client other than the client 3a that has sent the edit log file (that is, the client 3b...) That has logged in to the server 1 (hereinafter referred to as a login client). Inquiry as to whether or not the map editing application is running (S31).

Each of the login clients has a server 1
When an inquiry is received (S32), an answer to the inquiry is transmitted to the server 1 (S33). Server 1
Determines whether the map editing application has been activated for each of the login clients based on the answer (S34). And the management unit 4 answers
The edit log file received from the client 3a is transmitted only to the login client (that is, running the map editing application) (S35). Upon receiving the edit log file, the edit log creating unit 21 of the login client analyzes the contents of the edit log file, and the login client updates the contents of the local file 19 based on the analyzed contents.

For a login client whose answer is no (ie, the map editing application has not been started), the operation of the management unit 4 ends. In this case, when the login client that has not activated the map editing application later activates the map editing application and requests the map data of the area to be edited, as described in step S3 of FIG. ,
The corresponding map file is read from the master file 9 and sent to the login client. Since the content of the sent file has already been updated in step S21 in FIG. 3, the content of the updated file is stored in the local file 1 in step S4 in FIG.
9 will be reflected.

Also, as described above, when the map editing application is started later, the contents of the file updated in the master file 9 are also updated in the local file for the client who has not logged in to the server 1 in step S31. This will be reflected in the file 9.

With the above operation, the client server system synchronizes (unifies) the map data throughout the entire system.

The preferred embodiment of the present invention has been described above. However, the above-described embodiment is an exemplification for describing the present invention, and is not intended to limit the scope of the present invention only to this embodiment. Without departing from the spirit of the invention, those skilled in the art
The present invention can be implemented in various other forms in which various modifications, improvements, modifications, simplifications, and the like are added to the above-described embodiment. For example, the configuration of the server-client system is
The present invention is not limited to the centralized server-type client server system described above, but may be a distributed server-type client server system having a plurality of servers.

The client server system can be used in various applications such as a text creation application and a spreadsheet application in addition to a map editing application. The object to be edited is not limited to a figure, but may be a character, a symbol, a video, music, or the like.

Further, various variations of the unit related to the exclusive control can be considered. For example, one unit of the exclusive control may be for each editing target group of the same type. For example, in a map editing application, a road data group including all road data on a map is defined as one unit of exclusive control, and a building data group including all building data is defined as one unit on a map. A method is also conceivable in which a group is created for each meaning indicated by an object, and the group is used as one unit of exclusive control. When a character or the like is to be edited, one unit of exclusive control is
Each character, one sentence, one paragraph, or one sentence may be used.

[Brief description of the drawings]

FIG. 1 is a diagram showing a change in data to be edited on an application.

FIG. 2 is a diagram showing an overall configuration of a client server system according to an embodiment of the present invention.

FIG. 3 is a flowchart showing the flow of an editing process.

FIG. 4 is a diagram showing a processing flow in which the client server system synchronizes the entire system.

[Explanation of symbols]

 Reference Signs List 1 server 3 client 5 storage unit 7 operation unit 9 master file 11 figure lock list 13 edit log analysis unit 15 storage unit 17 operation unit 18 user interface unit 19 local file 20 editing unit 21 edit log creation unit

 ────────────────────────────────────────────────── ─── Continuing on the front page (72) Inventor Daisuke Tabuchi 3-14-10 Sotokanda, Chiyoda-ku, Tokyo Sofmap Future Design Co., Ltd. In-house (72) Inventor Ichiro Nakajima 3-14 Sotokanda, Chiyoda-ku, Tokyo 10 Sofmap Future Design Co., Ltd. In-house (72) Inventor Yuki Ito 3-14-10 Sotokanda, Chiyoda-ku, Tokyo In-house (72) Inventor Katsunori Kuwashima 3-chome, Sotokanda, Chiyoda-ku, Tokyo 14-10 Sofmap Future Design Stock Company In-house F-term (reference) 5B082 FA17 GA04 GB02 GB06 5B085 AC14 BG07

Claims (9)

[Claims] 1. A client-server system comprising: a server for managing a large number of editable objects; and a plurality of clients for editing the objects managed by the server. A lock list in which the identification code of the object locked for editing is registered, and referring to the lock list, the client determines whether or not the object desired to be edited is locked. A client-server system including a notification unit that notifies each of them. 2. A client server system comprising: a server that manages a large number of editable objects; and a plurality of clients that edit the objects managed by the server. The client freely edits the object received from the server, and after the editing is completed, generates a difference log indicating the content of the object changed by the editing performed, and transmits the difference log to the server. A client-server system in which a server reflects the transmitted content of the difference log to the object managed by the server. 3. The server sends the transmitted difference log to a client other than the client that sent the difference log, and the client that receives the difference log sent from the server sends the difference log to the client. 5. The client server system according to claim 4, wherein the contents of the log are reflected on the self. 4. A method in which a client server system including a server that manages a large number of editable objects and a plurality of clients that edit the objects managed by the server exclusively controls the objects. Registering in the lock list the identification code of the object that is locked because any of the clients is editing; and referring to the lock list, the object that each of the clients wants to edit is locked. An exclusive control method comprising: a step of determining whether or not the client has been locked; and a step of permitting each of the clients to edit only an unlocked object as a result of the determining step. 5. A method for synchronizing the data by a client server system comprising a server managing a large number of editable objects and a plurality of clients editing the objects managed by the server. A step in which the server passes the object to the client, and after the client performs an editing process on the object received from the server, generates a difference log of the editing process, and sends the difference log to the server. A data synchronization method comprising: transmitting; and the server reflecting the contents of the difference log to the object managed by the server. 6. A process in which the server sends the received difference log to a client other than the client that sent the difference log, and wherein the client that receives the difference log sent from the server includes: 6. The data synchronization method according to claim 5, further comprising a step of reflecting the contents of the difference log to itself. 7. A method in which a client server system including a server that manages a large number of editable objects and a plurality of clients that edit the objects managed by the server exclusively controls the objects. Registering in the lock list the identification code of the object that is locked because any of the clients is editing; and referring to the lock list, the object that each of the clients wants to edit is locked. Storing a program for causing a computer to execute an exclusive control method comprising: a step of determining whether or not the client has been locked; and, as a result of the determining step, a step of allowing each of the clients to edit only an unlocked object. Computer readable recording medium. 8. A method for synchronizing the data by a client server system comprising a server managing a large number of editable objects and a plurality of clients editing the objects managed by the server. A step in which the server passes the object to the client, and after the client performs an editing process on the object received from the server, generates a difference log of the editing process, and sends the difference log to the server. A computer-readable recording storing a program for causing a computer to execute a data synchronization method, comprising: transmitting, and the server reflecting the contents of the difference log to the object managed by the server. Medium. 9. A process in which the server transmits the received difference log to a client other than the client that has transmitted the difference log, and the client that has received the difference log transmitted from the server includes: The computer-readable recording medium according to claim 11, further comprising a step of reflecting the contents of the difference log to the self.