JP4355530B2 - File management apparatus and file management method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a file management apparatus and a file management method for storing a predetermined file read and updated by a predetermined terminal under a predetermined directory.
[0002]
[Prior art]
“Rsync”, “CVS”, etc. are generally known as methods for sharing the same file among a plurality of terminals.
[0003]
“Rsync” means that when one terminal sends a file to the other terminal, only the difference between the file managed by one terminal and the file managed by the other terminal This is a method of realizing file synchronization by transmitting to the other terminal.
[0004]
“CVS” is a system in which a predetermined file (substance of a file) that is supposed to be read and updated by a plurality of terminals is managed by a predetermined file management device (for example, Patent Document 1). .
[0005]
In the following, “CVS” will be specifically described with reference to the drawings. FIG. 8 is a diagram for explaining “CVS”.
[0006]
As shown in the figure, “CVS” is a repository that manages file entities (eg, “a ver.1.txt” and “a ver.2.txt”) and real directories managed by each terminal. It is comprised by.
[0007]
First, the case where the worker a updates “a ver.3.txt” will be described.
[0008]
In step 101, worker a reads “a ver.3.txt” managed by the repository to the terminal (check out).
[0009]
In step 102, the operator a updates “a ver.3.txt” to “new file (1) .txt”.
[0010]
In step 103, the worker a registers “new file (1) .txt” in the repository (check in). At this time, the repository stores “new file (1) .txt” as “a ver.4.txt”.
[0011]
Thereby, a plurality of terminals can share the file (“a ver.4.txt”) updated by the worker a.
[0012]
Next, a case where worker a and worker b update “a ver.4.txt” simultaneously will be described.
[0013]
In step 111, the worker a reads “a ver.4.txt” managed by the repository to the terminal (check out).
[0014]
In step 112, the worker a updates “a ver.4.txt” to “new file (2) .txt”.
[0015]
In step 113, the worker b reads out “a ver.4.txt” managed by the repository to the terminal (check out).
[0016]
In step 114, worker b updates “a ver.4.txt” to “new file (3) .txt”.
[0017]
In step 115, the worker a registers “new file (2) .txt” in the repository (check in).
[0018]
In step 116, the worker b registers “new file (3) .txt” in the repository (check in).
[0019]
In step 117, the repository merges “new file (2) .txt” and “new file (3) .txt”. Specifically, if the part updated by the worker a and the part updated by the worker b do not overlap (no collision), the repository will be “new file (2) .txt”. A file merged with “new file (3) .txt” is stored as “a ver.5.txt”. Further, when the portion updated by the worker a and the portion updated by the worker b overlap (there is a conflict), the repository displays an error message indicating that fact to the worker a and the worker. b.
[0020]
Thereby, a plurality of terminals can share the file (“a ver.4.txt”) updated by the worker a and the worker b, respectively.
[0021]
[Patent Document 1]
Japanese Patent Laid-Open No. 6-52031
[Problems to be solved by the invention]
However, “rsync” does not assume that three or more terminals share the same file.
[0023]
On the other hand, in “CVS”, when a predetermined file is updated by a predetermined terminal, the updated file is saved with the file name changed, but the directory for managing the file is changed. There is nothing. In “CVS”, when the same file is updated by multiple terminals, if the updated parts overlap each other (collisions occur), the files updated on each terminal Not stored in the repository.
[0024]
That is, in the related art, when a predetermined file is updated by a predetermined terminal, there is a problem that the updated file cannot be stored and managed under an arbitrary directory. In addition, when the same file is updated simultaneously by a plurality of terminals, there is a problem that all the files updated by each terminal cannot be stored.
[0025]
Therefore, the present invention has been made to solve the above-described problem, and even when the same file is simultaneously updated by a plurality of terminals, all the files updated by each terminal are stored, It is an object of the present invention to provide a file management apparatus and a file management method capable of storing and managing an updated file under an arbitrary directory.
[0026]
[Means for Solving the Problems]
The first feature of the present invention is that a directory creating means for creating a second directory when a predetermined file stored under the first directory is read and updated by a predetermined terminal; The file management device includes file storage means for storing the updated file under the second directory.
[0027]
According to such a feature, the file management device creates a new directory (second directory) when a predetermined file stored under the first directory is read and updated by a predetermined terminal. Then, by storing the updated file under the second directory, the file management apparatus can be used even when the files managed by the file management apparatus are simultaneously updated by a plurality of terminals. All the updated files can be stored.
[0028]
Further, the file management apparatus can store and manage the updated file under an arbitrary directory (second directory) created according to a preset condition.
[0029]
As a result, the file management apparatus can prevent the file from being updated unexpectedly by the operator even when the files managed by the file management apparatus are simultaneously updated by a plurality of terminals.
[0030]
According to a second aspect of the present invention, in the first aspect of the present invention, between a predetermined file stored under the first directory and a predetermined file name managed by a predetermined terminal, The file management device includes a link means for creating a symbolic link.
[0031]
According to such a feature, the file management device creates a symbolic link between a predetermined file stored under the first directory and a predetermined file name managed by a predetermined terminal, An operator of a predetermined terminal can read the substance of a file stored under the first directory without being aware of the structure of the first directory.
[0032]
According to a third feature of the present invention, in the second feature of the present invention, the linking means replaces the symbolic link according to a preset condition.
[0033]
According to such a feature, the file management apparatus replaces the symbolic link in accordance with a preset condition (for example, a condition set to replace the symbolic link with the latest file). Can reduce the load of the operator re-symbolizing the symbolic link.
[0034]
The fourth feature of the present invention is that the file management device creates the second directory when a predetermined file stored under the first directory is read and updated by a predetermined terminal. And a file management method comprising the step of the file management device storing the updated file under the second directory.
[0035]
DETAILED DESCRIPTION OF THE INVENTION
The file management apparatus (hereinafter referred to as a servant) in the present embodiment creates a second directory when a predetermined file stored under a predetermined directory is read and updated by a predetermined terminal. The updated file is stored under the second directory.
[0036]
In the present embodiment, the servant is described as being provided separately from each terminal. However, the servant may be provided in each terminal or may be configured by a plurality of terminals.
[0037]
(Configuration of file management device)
Hereinafter, a file management apparatus (servant) in the present embodiment will be described with reference to the drawings. FIG. 1 is a diagram illustrating an environment in which a servant 10 according to the present embodiment is installed.
[0038]
Specifically, as shown in the figure, the servant 10 is connected to the terminals 20a to 20c via the network 30.
[0039]
A specific description of the servant 10 is as follows. FIG. 2 is a block diagram showing a configuration of the servant 10 in the present embodiment.
[0040]
As shown in FIG. 2, the servant 10 includes a transmission unit 11, a reception unit 12, a virtual repository 13, and a link creation unit 14.
[0041]
In response to a read request from the terminal 20, the transmission unit 11 transmits the file entity managed in the virtual repository 13 to the terminal 20. Further, the receiving unit 12 receives a file entity (update information) read and updated by the terminal 20.
[0042]
The virtual repository 13 stores an entity of a predetermined file under a predetermined directory (hereinafter referred to as a first directory). Further, when the receiving unit 12 receives the file entity (update information) read and updated by the terminal 20, the virtual repository 13 receives a new directory (hereinafter referred to as a second directory) corresponding to the updated file entity. ) And save the updated file entity under the second directory.
[0043]
Specifically, it is as shown below. 3 and 4 are diagrams showing an example of the virtual repository 13 in the present embodiment.
[0044]
As shown in FIG. 3, the virtual repository 13 defines the entity of the file specified by the first directory name (“my office \ original”) and the first file name (“report.txt”) in the first directory. Is stored under. In addition, the file entity stored under the first directory (the file entity specified by “my office \ original \ report.txt”) and a predetermined file name (“doc2” managed by the terminal 20a). .txt "(or" my doc \ file1 \ doc2.txt ") is a symbolic link.
[0045]
This symbolic link is set based on conditions set by the operator of the terminal 20.
[0046]
Further, as shown in FIG. 4, the virtual repository 13 has the receiving unit 12 that receives the updated file entity (the entity of “my doc \ file1 \ doc2'.txt” (update information)) read and updated by the terminal 20a. Upon receipt, a second directory is created, and the updated file entity (the entity of “my doc \ file1 \ doc2'.txt” (update information)) is stored under the second directory. At this time, the virtual repository 13 specifies the second directory name (“my office \ user” in order to specify the updated file entity (the entity (update information) of “my doc \ file1 \ doc2'.txt”)). a \ ver.2 ") and a predetermined file name (" report.txt ").
[0047]
The link creation unit 14 creates a symbolic link between the file entity managed by the virtual repository 13 and a predetermined file name managed by the terminal 20 in accordance with conditions preset by the worker. In addition, the link creation unit 14 replaces the symbolic link according to conditions preset by the operator.
[0048]
Specifically, it is as shown below. FIG. 5 is a diagram illustrating an operation in which a symbolic link is replaced by the link creation unit 14 in the present embodiment. In the figure, when the entity of “report.txt” stored under “my office” is updated, the worker a replaces the symbolic link with the updated entity of “report.txt”. It is assumed that the conditions are set so that
[0049]
As shown in the figure, in the virtual repository 13, the reception unit 12 receives a file entity (an entity (update information) of “my doc \ file1 \ paper2'.txt”) read and updated by the terminal 20 b. Then, the second directory is created, and the updated file entity (the entity of “my doc \ file1 \ paper2'.txt” (update information)) is stored under the second directory. At this time, the virtual repository 13 specifies the second directory name (“my office \ user” in order to specify the updated file entity (the entity (update information) of “my doc \ file1 \ paper2'.txt”)). b \ ver.3 ") and a predetermined file name (" report.txt "). In addition, the link creation unit 14 determines the file entity (“my office \ user a \ ver.2 \ report.txt”) managed by the virtual repository 13 according to the conditions set by the worker a. The symbolic link between the predetermined file name ("doc2.txt" (or "my doc \ file1 \ doc2.txt")) managed by the terminal 20a and the terminal 20b. The read and updated file entity (the file entity specified by “my office \ user b \ ver.3 \ report.txt”) and a predetermined file name (“doc2.” Managed by the terminal 20a). txt "(or" my doc \ file1 \ doc2.txt ")).
[0050]
The terminals 20a to 20c are terminals such as personal computers, mobile phones, and PDAs.
[0051]
In this embodiment, the virtual repository 13 has a predetermined file stored under the first directory (for example, the entity of the file specified by “my office \ original \ report.txt”) as a predetermined. A directory creating means for creating the second directory when it is read and updated by the terminal is configured.
[0052]
In the present embodiment, the virtual repository 13 constitutes a file storage unit that stores the updated file under the second directory.
[0053]
Further, in the present embodiment, the link creation unit 14 is configured to execute a predetermined file (for example, a file entity specified by “my office \ original \ report.txt”) stored under the first directory and a predetermined file. A link means for creating a symbolic link with a predetermined file name (for example, “doc.2.txt”) managed by the terminal is configured.
[0054]
(Operation of file management device)
The operation of the file management apparatus (servant) in this embodiment will be described below with reference to the drawings. FIG. 6 is a sequence diagram showing an operation in which the servant 10 in the present embodiment creates a new directory (second directory). In addition, the figure is a figure for demonstrating operation | movement of the servant 10 according to above-mentioned FIG.
[0055]
As shown in the figure, in step 11, the worker a (terminal 20a) has a predetermined file name ("doc2.txt" (or "my doc \ file1 \ doc2.txt") managed by the terminal 20a. ), The file entity managed by the servant 10 is read out. At this time, the servant 10 is identified by “my office \ original \ report.txt” based on the symbolic link attached to “doc2.txt” (or “my doc \ file1 \ doc2.txt”). The entity of the file is transmitted to the terminal 20a.
[0056]
In step 12, the worker a (terminal 20a) updates the substance of the file read in step 11.
[0057]
In step 13, the worker a (terminal 20 a) stores the file entity updated in step 12 (the entity “my doc \ file1 \ doc2′.txt”). At this time, the terminal 20a transmits update information (an entity of “my doc \ file1 \ doc2′.txt”) to the servant 10.
[0058]
In step 14, the servant 10 receives the update information (the substance of “my doc \ file1 \ doc2′.txt”) transmitted by the terminal 20a.
[0059]
In step 15, the servant 10 creates a second directory, and saves update information (an entity of “my doc \ file1 \ doc2′.txt”) under the second directory. At this time, the servant 10 specifies a second directory name (“my office \ user a \ ver.2”) and a predetermined number in order to specify update information (an entity of “my doc \ file1 \ doc2'.txt”). Set the file name ("report.txt").
[0060]
In step 21, the worker b (terminal 20 b), based on a predetermined file name (“paper2.txt” (or “my doc \ file1 \ paper2.txt”)) managed by the terminal 20 b, Read the actual file managed by. At this time, the servant 10 is identified by “my office \ original \ report.txt” based on the symbolic link attached to “paper2.txt” (or “my doc \ file1 \ paper2.txt”). The entity of the file is transmitted to the terminal 20b.
[0061]
In step 22, worker b (terminal 20 b) updates the substance of the file read in step 21.
[0062]
In step 23, worker b (terminal 20b) stores the file entity updated in step 22 (the entity of “my doc \ file1 \ paper2′.txt”). At this time, the terminal 20b transmits update information (an entity of “my doc \ file1 \ paper2′.txt”) to the servant 10.
[0063]
In step 24, the servant 10 receives the update information (the substance “my doc \ file1 \ paper2′.txt”) transmitted by the terminal 20b.
[0064]
In step 25, the servant 10 creates a second directory and saves the update information (the substance of “my doc \ file1 \ paper2'.txt”) under the second directory. At this time, the servant 10 specifies the second directory name ("my office \ user b \ ver.3") and the update information (the substance of "my doc \ file1 \ paper2'.txt") and Set a predetermined file name (“report.txt”).
[0065]
FIG. 7 is a sequence diagram showing an operation in which the servant 10 in this embodiment replaces the symbolic link. In addition, the figure is a figure for demonstrating operation | movement of the servant 10 according to above-mentioned FIG. Also, in the figure, when the entity of “report.txt” stored under “my office” is updated, the worker a replaces the symbolic link with the updated entity of “report.txt”. It is assumed that the conditions are set so that
[0066]
As shown in the figure, in step 31, the worker b (terminal 20b) has a predetermined file name ("paper2.txt" (or "my doc \ file1 \ paper2.txt") managed by the terminal 20b. ) Is updated, and the updated file entity (the entity of “my doc \ file1 \ paper2'.txt”) is saved. At this time, the terminal 20b transmits update information (an entity of “my doc \ file1 \ paper2′.txt”) to the servant 10.
[0067]
In step 32, the servant 10 receives the update information (the substance of “my doc \ file1 \ paper2′.txt”) transmitted by the terminal 20b.
[0068]
In step 33, the servant 10 creates a second directory and saves the update information (the substance of “my doc \ file1 \ paper2'.txt”) under the second directory. At this time, the servant 10 specifies the second directory name (“my office \ user b \ ver.3”) and a predetermined number in order to specify the update information (the substance of “my doc \ file1 \ paper2'.txt”). Set the file name ("report.txt").
[0069]
In step 34, the servant 10 is identified by the file entity ("my office \ user a \ ver.2 \ report.txt") managed by the virtual repository 13 in accordance with the conditions set by the worker a. A symbolic link extending between a file entity) and a predetermined file name ("doc2.txt" (or "my doc \ file1 \ doc2.txt")) managed by the terminal 20a. The file entity read and updated by (the office entity of the file specified by “my office \ user b \ ver.3 \ report.txt”) and the predetermined file name (“doc2” managed by the terminal 20a) .txt "(or" my doc \ file1 \ doc2.txt ")).
[0070]
(Operation and effect of file management device)
According to the file management apparatus (servant 10), when the servant 10 receives a file (update information) read and updated by the terminal 20, it creates a new directory (second directory) and updates the file. By storing the file (update information) under the second directory, the servant 10 is updated even when the files managed by the servant 10 are updated simultaneously by the plurality of terminals 20. All files (update information) can be stored.
[0071]
In addition, the servant 10 can store and manage the updated file under an arbitrary directory (second directory) created in accordance with preset conditions.
[0072]
As a result, the servant 10 can prevent the file from being updated unexpectedly by the operator even when the files managed by the servant 10 are simultaneously updated by the plurality of terminals 20.
[0073]
Further, the servant 10 creates a symbolic link between a file (substance of the file) stored under the first directory and a predetermined file name managed by the terminal 20, so that the terminal 20 An operator can read the substance of a file stored under the first directory without being aware of the structure of the first directory.
[0074]
Furthermore, the servant 10 can reduce the load of the operator changing the symbolic link by changing the symbolic link according to a preset condition.
[0075]
【The invention's effect】
According to the present invention, even when the same file is updated by a plurality of terminals, all the files updated by each terminal are stored, and the updated files are stored under an arbitrary directory. A file management apparatus and a file management method capable of performing the above can be provided.
[Brief description of the drawings]
FIG. 1 is a diagram showing an environment in which a servant 10 is installed in the present embodiment.
FIG. 2 is a block diagram showing a configuration of a servant 10 in the present embodiment.
FIG. 3 is a diagram showing an example of a virtual repository 13 in the present embodiment (part 1);
FIG. 4 is a diagram showing an example of a virtual repository 13 in the present embodiment (part 2).
FIG. 5 is a diagram illustrating an operation in which a symbolic link is replaced by a link creating unit 14 according to the present embodiment.
FIG. 6 is a sequence diagram showing the operation of the servant 10 in the embodiment (No. 1).
FIG. 7 is a sequence diagram showing the operation of the servant 10 in the embodiment (No. 2).
FIG. 8 is a diagram for explaining a conventional technique (“CVS”).
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 10 ... Servant, 11 transmission part, 12 ... Reception part, 13 ... Virtual repository, 14 ... Link creation part, 20a-20c ... Terminal, 30 ... Network

Claims (2)

If the substance of the files stored in the virtual repository under the first directory is updated is read by each of the plurality of terminals, in the virtual repository, the second corresponding to the plurality of terminals Directory creation means for creating a directory;
File storage means for storing an entity of a file updated by each of the plurality of terminals in the virtual repository under the second directory ;
Link establishment means for creating a symbolic link that associates a file name managed in a real directory provided in each of the plurality of terminals with a file entity stored in the virtual repository;
When the substance of the file stored in the virtual repository is read and updated by the first terminal among the plurality of terminals, it is set in advance for the second terminal among the plurality of terminals. In accordance with the specified conditions, the first terminal reads and updates the substance of the file associated with the file name managed in the real directory provided in the second terminal by the symbolic link. A file management apparatus comprising: a link replacement means for changing to a file entity . When the file management apparatus reads and updates the substance of the file stored under the first directory in the virtual repository by each of the plurality of terminals , each of the plurality of terminals in the virtual repository Creating a corresponding second directory;
The file management device storing an entity of a file updated by each of the plurality of terminals in the virtual repository under the second directory ;
The file management device creates a symbolic link that associates a file name managed in a real directory provided in each of the plurality of terminals with a substance of a file stored in the virtual repository;
When the file management device reads and updates the substance of the file stored in the virtual repository by the first terminal among the plurality of terminals, the second of the plurality of terminals In accordance with the conditions set in advance for the terminal, the first terminal sets the entity of the file associated with the file name managed in the real directory provided in the second terminal by the symbolic link. A file management method comprising the steps of: changing to a file entity that has been read and updated .

Images