WO2012032873A1 - 共有ファイル管理システム、その制御方法、およびプログラム - Google Patents

共有ファイル管理システム、その制御方法、およびプログラム Download PDF

Info

Publication number
WO2012032873A1
WO2012032873A1 PCT/JP2011/067246 JP2011067246W WO2012032873A1 WO 2012032873 A1 WO2012032873 A1 WO 2012032873A1 JP 2011067246 W JP2011067246 W JP 2011067246W WO 2012032873 A1 WO2012032873 A1 WO 2012032873A1
Authority
WO
WIPO (PCT)
Prior art keywords
shared file
client
state
editing
clients
Prior art date
Application number
PCT/JP2011/067246
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
貴史 野口
Original Assignee
株式会社 山武
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社 山武 filed Critical 株式会社 山武
Publication of WO2012032873A1 publication Critical patent/WO2012032873A1/ja

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/17—Details of further file system functions
    • G06F16/176—Support for shared access to files; File sharing support
    • G06F16/1767—Concurrency control, e.g. optimistic or pessimistic approaches
    • G06F16/1774—Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files

Definitions

  • the present invention relates to a shared file management system, a control method therefor, and a program, and in particular, includes a server, a plurality of clients, and a network that interconnects them, and the server is accessible to each of the plurality of clients.
  • the present invention relates to a shared file management system for storing files, a control method therefor, and a program.
  • the shared file may be left unchecked as the server, the client that was editing, or the network that connects them goes down. In such a case, even if the editing work is finished, the shared file is left in a locked state for a long time, and the shared file cannot be managed efficiently.
  • the present invention has been made to solve the above-described problems, and an object of the present invention is to provide a shared file management system, a control method for the shared file management system, and a program capable of managing shared files more efficiently.
  • the shared file management system locks a shared file that can be accessed by each of a plurality of clients via a network so that only the one client can edit the shared file based on an editing start request of the one client.
  • State control means for setting the shared file to the unlocked state in which the locked state is released based on the editing end request from the one client, and whether the shared file is in the locked state or the unlocked state
  • Status information storage means for storing status information representing the status information, and status information output means for outputting status information of the shared file stored in the status information storage means to each of the plurality of clients.
  • the shared file management system control method is based on an edit start request or an edit end request of one of the plurality of clients for a shared file that can be accessed by each of the plurality of clients via a network.
  • a state including at least a locked state in which only this one client can edit the shared file or an unlocked state in which the locked state is released, and at least whether the shared file is in the locked state or the unlocked state Storing information in a storage unit; and causing each of the plurality of clients to output status information of the shared file stored in the storage unit.
  • the program according to the present invention relates to a shared file that can be accessed by each of a plurality of clients via a network based on an edit start request or an edit end request of one of the plurality of clients.
  • the state information including at least whether the shared file is in the locked state or the unlocked state is stored, and the client is operated by causing each of the plurality of clients to output the state information of the shared file. Since the user can easily grasp whether or not the shared file is being edited by another user, the shared file can be managed more efficiently.
  • FIG. 1 is a diagram showing a configuration of a shared file management system according to an embodiment of the present invention.
  • FIG. 2 is a block diagram showing a configuration example of the server of the shared file management system according to the embodiment of the present invention.
  • FIG. 3 is a block diagram showing a configuration example of a client of the shared file management system according to the embodiment of the present invention.
  • FIG. 4 is a diagram showing a configuration example of a shared file management table stored in the shared file management system according to the embodiment of the present invention.
  • FIG. 5 is a flowchart showing an editing start routine executed by the server when a shared file editing start request is received from the client 2 in the shared file management system according to the embodiment of the present invention.
  • FIG. 1 is a diagram showing a configuration of a shared file management system according to an embodiment of the present invention.
  • FIG. 2 is a block diagram showing a configuration example of the server of the shared file management system according to the embodiment of the present invention.
  • FIG. 3 is a block diagram showing
  • FIG. 6A is a diagram showing an example of a monitoring screen when all shared files are unlocked in the shared file management system according to the embodiment of the present invention.
  • FIG. 6B is a diagram showing an example of a monitoring screen when a shared file in the shared file management system according to the embodiment of the present invention is in a locked state.
  • FIG. 7 is a flowchart showing an editing end routine executed by the server when a shared file editing end request is received from a client in the shared file management system according to the embodiment of the present invention.
  • FIG. 8 is a sequence diagram showing an example of the operation of the shared file management system according to the embodiment of the present invention.
  • FIG. 9 is a flowchart showing a forced termination routine executed by the server in the shared file management system according to the embodiment of the present invention.
  • FIG. 10 is a block diagram showing a modification of the shared file management system according to the embodiment of the present invention.
  • the shared file management system 100 includes a server 10, N clients 20 (20-1 to 20-N), and a LAN (Local Area) that interconnects them. Network) 30.
  • the server 10 includes a CPU, a storage device, an input / output device, and a communication interface (not shown), and functionally, as shown in FIG. 2, a storage unit 11, a state control unit 12, and a state information storage unit. 13, a reservation unit 14, a status information output unit 15, a forced termination unit 16, and a communication unit 17.
  • the storage unit 11 stores data such as shared files that can be accessed by each of the clients 20 (20-1 to 20-N).
  • the shared file refers to a file that can be accessed by each of a plurality of computers (clients 20) via a network (LAN 30).
  • the state control unit 12 puts the shared file into a locked state in which only one of the clients 20-1 to 20-N can be edited, or receives an edit end request from the client In response to this, the lock state of the shared file is released to the unlocked state.
  • the state information storage unit 13 stores state information of a shared file including whether the shared file stored in the storage unit 11 is in a locked state or an unlocked state.
  • the reservation unit 14 makes a reservation so that when the client 20 receives an edit start request for a shared file in a locked state, the client 20 can edit the shared file as soon as the shared file is unlocked. is there.
  • the status information output unit 15 reads the status information stored in the status information storage unit 13 and causes the client 20 to output the status information.
  • the forced termination unit 16 When the shared file is checked out by one of the clients 20-1 to 20-N and a locked state has passed for a long time (for example, 10 hours or 20 hours), the forced termination unit 16 The file is forced to be unlocked.
  • the communication unit 17 realizes a function of performing communication with the clients 20-1 to 20-N via the LAN 30.
  • the client 20 includes a CPU, a storage device, an input / output device, and a communication interface (not shown), and functionally includes a display unit 21, an operation unit 22, and a communication communication unit 23 as shown in FIG. I have.
  • the display unit 21 displays various screens such as a display device.
  • the operation unit 22 inputs signals such as characters, numbers, symbols, and directions to a CPU (not shown) provided in the client 20 based on user operations such as a keyboard and a mouse.
  • the communication communication unit 23 implements a function of performing communication with the server 10 and other clients 20 via the LAN 30.
  • the shared file management table stored in the state information storage unit 13 includes a “shared file ID”, “flag F1”, “editor ID”, “flag F2”, “reserver ID”, and It contains a record consisting of a field called “update time”.
  • the “shared file ID” is an ID for uniquely identifying the shared file, and for example, a path of each shared file or a character string uniquely assigned to each shared file can be used.
  • the “flag F1” indicates whether or not the corresponding shared file has been edited by the client 20, that is, whether or not the shared file is in a locked state or an unlocked state.
  • the value “0” is input when the shared file is unlocked, and the value “1” is input when the shared file is locked.
  • “Editor ID” indicates an ID for uniquely identifying the client who is editing the shared file when the corresponding shared file is being edited. For example, the IP address of the client, the MAC Address, authenticated user name, etc. are entered. For this reason, when the value of the “flag F1” is “1”, other clients 20 other than the client 20 specified by the “editor ID” cannot edit the shared file. When the shared file is not being edited, the value of the “flag F1” is “0”, and the value of the “editor ID” field is NULL.
  • the “flag F2” is edited by another client when the shared file is being edited by a client, that is, when the value of the “flag F1” is set to “1” and is locked. It indicates whether or not a right is reserved. Specifically, the value “0” is input when the shared file is not reserved, and the value “1” is input when the shared file has already been reserved.
  • “Reserver ID” indicates an ID for uniquely identifying the client who reserves the editing right of the shared file when the editing right of the shared file is reserved. An IP address, a MAC address, an authenticated user name, and the like are input.
  • the client 20 specified by the “reserver ID” edits the shared file. Will be able to. If the shared file is not reserved, the value of the “flag F2” is “0”, and the value of the “reserver ID” field is NULL.
  • the “update time” indicates the time when the editing operation of the shared file corresponding to the corresponding record is started, or the last saving time in the case of the shared file stored during the editing operation. This is used when the forced termination unit 16 checks whether a long time has passed with the shared file being locked. When the shared file corresponding to the corresponding record is not being edited, the value of this field is NULL.
  • the status information storage unit 13 stores the status information of the shared file by inputting data into the shared file management table.
  • the sharing is performed.
  • the operation of the file management system 100 will be described.
  • the communication communication unit 23 transmits a signal notifying the server 10 of a shared file editing start request.
  • the server 10 refers to the shared file management table and determines whether to approve the editing work. The contents will be described below with reference to the flowchart shown in FIG.
  • client ID an ID for specifying the client 20
  • client ID an ID for specifying the client 20
  • the client 20 displays the shared file management table.
  • “flag F1” and “flag F2” of the record corresponding to the corresponding shared file are read (step S100), and it is checked whether or not the value of “flag F1” is “0” (step S110).
  • step S110 when the value of the read “flag F1” is “0” (step S110; YES), it is determined that this shared file is not being edited, and the process of checking out this shared file, ie, this client A process of setting the lock state so that 20 can edit the shared file exclusively is performed.
  • the state control unit 12 updates the value of the “flag F1” of the record associated with the shared file ID to “1” and sets the client ID of the client 20 to “editor ID”.
  • the current time is input as “update time” (step S120).
  • the communication unit 17 downloads the corresponding shared file to the client 20 (step S130), and notifies all the clients 20-1 to 20-N that the shared file is being edited. (Step S140), and the editing start routine ends.
  • step S140 the fact that the corresponding shared file is being edited in the clients 20-1 to 20-N is output as follows.
  • an icon indicating the status of the shared file is attached to the side of the shared file name displayed for each area of the building, and is white when it is unlocked.
  • the icon that was a square has changed to a square icon with a “ ⁇ ” mark due to the locked state. Therefore, the user operating the client 20 can confirm whether or not the shared file is being edited by opening this screen and confirming the state of the icon in front of the shared file.
  • the user operating the client 20 edits the shared file using the function of the communication communication unit 23, for example, by clicking on the shared file name of the shared file that is being edited and locked.
  • a message can be transmitted to the client 20 or a telephone call can be made.
  • the users who wish to edit the shared file can communicate with each other and unlock the shared file. Since negotiation can be performed, management of shared files can be performed more efficiently.
  • a tree structure monitoring screen is described as an example. However, any display form may be used as long as the shared file status can be confirmed. May be displayed.
  • step S110 when the value of “flag F1” is “1” (step S110; NO), it is determined that this shared file is being edited, and the value of “flag F2” is “0”. It is further determined whether or not there is (step S150). When the value of “Flag F2” is “0” (step S150; YES), it is determined that the shared file has not been reserved yet, and the reservation unit 14 performs a reservation process. Specifically, the value of “Flag F2” is updated to “1”, and the client ID of this client 20 is input to “Reserver ID” (step S160), and the editing start routine ends.
  • step S160 The timing at which the authority to edit the shared file is transferred from the client 20 currently editing to the client 20 that has performed the reservation process will be described later.
  • step S150; NO when the value of “flag F2” is “1” (step S150; NO), it is determined that this shared file has already been reserved, and the reservation unit 14 starts editing without performing reservation processing. End the routine.
  • the communication communication unit 23 transmits a signal notifying the server 10 of the editing end request of the shared file.
  • the server 10 refers to the shared file management table, refers to whether or not reservation processing has been performed on the shared file, and releases the lock state of the shared file. To do. The contents will be described below with reference to the flowchart shown in FIG.
  • the state control unit 12 checks again whether there is an editing start request (that is, cancellation of an editing end request) from the same client 20 again within a predetermined time (for example, 10 seconds or 20 seconds) (step S200).
  • a predetermined time for example, 10 seconds or 20 seconds
  • the edit end routine is ended without performing a check-in described later. Therefore, the lock state of the shared file is not released, and the same client can continuously edit the shared file.
  • the state control unit 14 accepts only the edit start request from the same client 20 for a predetermined time because the user operating the client 20 accidentally ends the program or the like. This is to prevent the shared file from being locked by another client 20 when the editing operation is finished, and the editing cannot be performed.
  • step S200 when there is no editing start request again from the same client 20 within a predetermined time (step S200; YES), in order to check in this shared file, that is, the lock state of this shared file is released and the unlock state is set. Therefore, the following processing is performed.
  • the “flag F2” of the record of the corresponding shared file is read with reference to the shared file management table (step S210), and it is determined whether or not the value of this “flag F2” is “0” (step S210). S220). When the value of the read “flag F2” is “0” (step S220; YES), it is determined that this shared file is not reserved, and the state control unit 12 performs a check-in process.
  • the state control unit 12 updates the value of “Flag F2” to “0”, updates the value of “Editor ID” to NULL, and updates the value of “Update Time” to NULL (Step S1). S230). Further, the communication unit 17 notifies all clients that the shared file can be edited (step S240), and the editing end routine ends.
  • the communication unit 17 notifies the clients 20-1 to 20-N that the shared file can be edited, as described above, the display unit 21 of the clients 20-1 to 20-N When the shared file status monitoring screen is opened and the icon next to the shared file name of the shared file is confirmed, it can be seen that the square marked with “X” has changed to a white square. Therefore, the user can easily determine whether the corresponding shared file is being edited by opening this monitoring screen.
  • step S220 when the value of the read “flag F2” is “1” (step S220; NO), it is determined that the shared file is reserved, and the state control unit 12 reserves editing of the shared file.
  • the process of approving the editing to the client 20 that has been performed is performed. Specifically, the state control unit 12 inputs “reserver ID” in “editor ID”, updates “reserver ID” to NULL, and updates the value of “flag F2” to “0”. (Step S250).
  • the communication unit 17 downloads the shared file to the reserved client 20 and notifies that the editing request for the shared file has been approved (step S260), and ends the editing end routine.
  • a method for notifying the reserved client 20 that the editing request has been approved for example, when the above-described shared file monitoring screen is opened on the display unit 21 of the reserved client 20. And a method for displaying that the editing request has been approved by pop-up or generating a chime.
  • the user operating the client 20 bothers to check the status of the shared file. This makes it possible to concentrate on other tasks while waiting for a notification that the shared file editing request has been approved.
  • step S300 when a user using the client 20-1 executes a predetermined operation for starting editing of a shared file stored in the server 10, the client 20-1 requests the server 10 to start editing. Is transmitted (step S300), and the server 10 executes the editing start routine described with reference to FIG. 5 (step S310).
  • the shared file for which an edit start request has been made has not been edited by anyone, and the value of the “flag F1” of the corresponding record in the shared file management table is “0”.
  • the client ID of the client 20-1 is input to the “editor ID”
  • the current time is input to the “update time”
  • the shared file is downloaded to the client 20-1, and the clients 20-1, 20 are downloaded.
  • -2 is notified that this shared file has been locked.
  • step S320 the server 10 executes the editing start routine described with reference to FIG. 5 again (step S330).
  • step S330 the shared file for which an edit start request has been made has already been edited by the client 20-1, and the value of the “flag F1” of the corresponding record in the shared file management table is “1”. Therefore, an edit start request from the client 20-2 is not accepted, and it is determined in step S150 in FIG. 5 whether the value of “flag F2” is “0”. If this shared file has not yet been reserved for editing and the value of “Flag F2” is “0”, the value of “Flag F2” is updated to “1” in Step S160 of FIG. Enter the client ID of the client 20-2 in “Reserver ID”.
  • step S340 when the user operating the client 20-1 performs an operation of overwriting and saving the downloaded shared file, the shared file is uploaded to the server 10 (step S340). Further, when the editing work is finished by closing the shared file on the editing program, an editing end request is transmitted from the client 20-1 to the server 10 (step S350), and the server 10 uses FIG. The editing end routine described above is executed (step S360).
  • step S360 since the client 20-2 has already made a reservation so that the shared file can be edited next, and the value of the “flag F2” of the corresponding record in the shared file management table is “1”, step S250 in FIG.
  • step S260 in FIG. 7 the shared file is downloaded to the client 20-2 and the editing of the shared file is notified.
  • the user operating the client 20-2 can immediately know that the editing has been approved as soon as the editing by the client 20-1 is completed, and can immediately start editing the shared file.
  • step S370 When the user operating the client 20-2 performs an operation for overwriting and saving the shared file, the shared file is uploaded to the server 10 (step S370). Further, when the editing work is ended by closing the shared file on the editing program, an editing end request is transmitted from the client 20-2 to the server 10 (step S380), and the server 10 again returns to FIG.
  • the editing end routine described above is executed (step S390).
  • step S360 the value of “flag F2” is updated to “0” in the corresponding record of the shared file management table, and the reservation for the shared file is released. Therefore, an affirmative determination is made in step S220 of FIG.
  • step S370 the shared file upload (step S370) and the shared file editing end request (step S380) are independent of each other. This is because, in preparation for when the client 20 is down, the user has a desire to frequently upload the edited contents to the server 10 even during the editing of the shared file.
  • one record is extracted from the shared file management table (step S400).
  • a record to be extracted it is only necessary to extract and extract the record stored in the shared file management table with the value of “flag F1” being “1”, that is, the locked state.
  • the “update time” of this record is read, and the elapsed time ⁇ T from the “update time” is calculated (step S410).
  • this “update time” the time when the editing operation of the corresponding shared file is started, or the time when the file is overwritten in the middle of the editing operation is input last.
  • the elapsed time ⁇ T indicates the elapsed time since the start of the editing work when the shared file being edited has never been overwritten and saved, and the last time for the shared file overwritten and saved during the editing work. Indicates the elapsed time since it was overwritten.
  • the elapsed time ⁇ T calculated in this way is compared with the threshold value T1 and a larger threshold value T2 (step S420).
  • the threshold T2 is set as a time that can be predicted that the shared file is locked even though the editing of the shared file has already been completed, and is set to 10 to 20 hours, for example.
  • the threshold T1 is set as a time shorter by about 1 to 2 hours than the threshold T2, and is used to give a notice before the shared file in the locked state is forcibly set to the unlocked state.
  • step S420 When the elapsed time ⁇ T is less than the threshold value T1 (step S420; ⁇ T ⁇ T1), the shared file is not locked for a long time, so the process related to forced termination is not executed.
  • the elapsed time ⁇ T is equal to or greater than the threshold T1 and less than the threshold T2 (step S420; T1 ⁇ ⁇ T ⁇ T2), the elapsed time ⁇ T becomes equal to or greater than the threshold T2 after a while, and the shared file editing process is forcibly terminated as described later. Therefore, a pop-up prompting the user editing the shared file corresponding to the record to save the shared file is displayed (step S430).
  • the pop-up display content may be displayed with a message prompting to save the shared file and the remaining time until the forced termination process is executed.
  • the elapsed time ⁇ T is equal to or greater than the threshold T2 (step S420; T2 ⁇ T)
  • T2 ⁇ T it is determined that the shared file is left in a locked state even though the editing operation of the shared file has already been completed.
  • Performs forced termination processing Specifically, by executing the editing end routine described with reference to FIG. 7 (step S440), when there is no reservation for the shared file, the lock state is released and the unlock state is set. On the other hand, when there is a reservation, the editing work is approved for the client who made the reservation.
  • step S200 in FIG. 7 for accepting an edit request from a client that is editing only for a predetermined time may be omitted.
  • the user who has locked the shared file for a long time is notified by pop-up that the editing of the shared file has been forcibly ended (step S450).
  • step S460 After confirming that the processes in steps S400 to S450 have been executed for all the records in the shared file management table (step S460), the forced termination routine is terminated. In this way, if there is a shared file that has been locked for a long time by one client 20, the locked state is forcibly released, so that the shared file can be edited efficiently. . Further, since the user who is editing the shared file is notified to save the shared file before forcibly releasing the lock state (step S430), the editing operation of the shared file is continued. Nevertheless, forcibly releasing the lock state can also be suppressed.
  • the server 10 sets the value of “flag F1” indicating whether the shared file is in the locked state or the unlocked state in the shared file management table.
  • the value of this “flag F1” is updated, it is notified to all clients 20 (step S140 in FIG. 5 and step S240 in FIG. 7).
  • the user of the client 20 can easily edit the shared file by opening a monitoring screen for managing the status of the shared file on the display unit 21 and checking the status of the icon in front of the shared file. Whether or not there is can be grasped. Therefore, the shared file can be managed efficiently.
  • the server 10 keeps the predetermined time (for example, 10 seconds). Within 20 seconds), it is confirmed again that there is no editing start request from the same client 20 (step S200 in FIG. 7). For this reason, even if a user editing a shared file accidentally ends the shared file editing operation, the user can perform an operation for starting the shared file editing operation again within a predetermined time. Then, it can be prevented that the shared file is locked by another client 20 and cannot be edited.
  • the predetermined time for example, 10 seconds.
  • the user who operates the client 20 opens the shared file monitoring screen shown in FIGS. 6A and 6B and performs a predetermined operation, whereby the communication communication unit It is possible to negotiate with each other who wish to edit the shared file by using the function 23, and to release the lock state of the shared file. For this reason, the shared file can be edited efficiently.
  • the server 10 receives a request to start editing from another client 20 when the shared file is being edited and locked by the client 20 with the shared file.
  • a reservation is made so that the shared file can be edited (step S160 in FIG. 5), and as soon as the editing operation is completed, the shared file is downloaded and notified that the editing has been approved (FIG. 7). Steps S250 and S260), the shared file can be edited efficiently.
  • the server 10 is locked for a long time by one client 20 of the shared files by executing the forced termination routine described in FIG. If there is something, the locked state is forcibly released, so that the shared file can be edited efficiently.
  • the storage unit 11, the state control unit 12, the state information storage unit 13, the reservation unit 14, the state information output unit 15, and the forcible termination unit 16 are: Although all have been described as being provided in the same server 10, they may be provided in different servers as shown in FIG.
  • the server 10-1 includes the storage unit 11, and the server 10-2 includes the state control unit 12, the state information storage unit 13, the reservation unit 14, the state information output unit 15, and the forced termination unit 16. It has.
  • the server 10-1 executes the process of downloading the shared file described in step S130 of FIG. 5 and step S260 of FIG. 7 to the client 20, and the server 10-2 performs the other processes. It will be.
  • the state of the shared file is between the locked state and the unlocked state.
  • the server 10 notifies all the clients 20 when it fluctuates, it may not be notified.
  • each of the clients 20 sends an SQL to the server 10 for inquiring about a change in the shared file management table every predetermined time (for example, every few minutes or every several tens of minutes). That's fine.
  • the notification from the server 10 to all the clients 20 is only that the shared file management table has changed, and each of the clients 20 (20-1 to 20-N) uses the specific information as a trigger. It is good also as what transmits to the server 10 the SQL sentence which inquires.
  • the server 10 and the clients 20 (20-1 to 20-N) are connected by the LAN 30, but not via the LAN 30 but via the Internet network. It may be connected.
  • step S200 for accepting an editing start request (cancellation of editing end request) from a client who is editing the shared file for a predetermined time may be omitted.
  • reservation can be made only by one client 20, but reservations may be accepted from a plurality of clients 20, and in this case, for example, The client 20 may be able to edit in the order in which reservations are received.
  • the server 10 includes the reservation unit 14 and the forced termination unit 16, but may not include these.
  • the present invention has been described as a form of the shared file management system 100.
  • a form of a control method of the shared file management system 100 or a form of a program incorporated in the shared file management system 100 may be used.
  • each functional unit included in the server 10 and the client 20 includes hardware resources such as an interface with a CPU, a storage device, and an external device included in the server 10 and the client 20, and these hardware units.
  • hardware resources such as an interface with a CPU, a storage device, and an external device included in the server 10 and the client 20, and these hardware units.
  • a program for realizing the control method of the shared file management system 100 is provided in a state of being recorded on a non-transitory recording medium such as a flexible disk, a CD-ROM, a DVD-ROM, or a memory card. Is done.
  • the CPU writes the program read from the permanent recording medium into the storage device, and executes the processing described in the embodiment according to the program.
  • the present invention can be used for manufacturing a shared file management system.
PCT/JP2011/067246 2010-09-08 2011-07-28 共有ファイル管理システム、その制御方法、およびプログラム WO2012032873A1 (ja)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2010-200846 2010-09-08
JP2010200846A JP5373723B2 (ja) 2010-09-08 2010-09-08 共有ファイル管理システム、その制御方法、およびプログラム

Publications (1)

Publication Number Publication Date
WO2012032873A1 true WO2012032873A1 (ja) 2012-03-15

Family

ID=45810477

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2011/067246 WO2012032873A1 (ja) 2010-09-08 2011-07-28 共有ファイル管理システム、その制御方法、およびプログラム

Country Status (3)

Country Link
JP (1) JP5373723B2 (zh)
TW (1) TWI475398B (zh)
WO (1) WO2012032873A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113656512A (zh) * 2021-10-21 2021-11-16 浙江太美医疗科技股份有限公司 数据解锁方法、装置、设备和存储介质
EP3783495A4 (en) * 2018-04-19 2022-01-05 Murata Machinery, Ltd. EXCLUSIVE ORDERING SYSTEM AND PROCEDURE

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103780642B (zh) * 2012-10-19 2017-08-01 宇瞻科技股份有限公司 网络存储系统的文件分享方法
JP6381190B2 (ja) * 2013-08-20 2018-08-29 キヤノン株式会社 クライアント装置、システム、情報処理方法及びプログラム
JP6180998B2 (ja) * 2014-06-05 2017-08-16 東芝テック株式会社 情報処理システム及び情報処理プログラム
US10452456B2 (en) 2016-12-27 2019-10-22 Dropbox, Inc. Kernel event triggers
US10331623B2 (en) * 2017-10-16 2019-06-25 Dropbox, Inc. Workflow functions of content management system enforced by client device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11338754A (ja) * 1998-05-22 1999-12-10 Mitsubishi Electric Corp 共有ファイル管理システム
JP2006011936A (ja) * 2004-06-28 2006-01-12 Konica Minolta Business Technologies Inc 共有ファイル管理システムおよびサーバー
JP2006285867A (ja) * 2005-04-04 2006-10-19 Nec Corp ファイル管理システム、監視サーバ、ファイルサーバ、ファイル管理方法、及び、プログラム
JP2007328392A (ja) * 2006-06-06 2007-12-20 Fuji Xerox Co Ltd 文書編集システム、文書編集制御サーバ、サーバ用プログラム、ユーザ端末、端末用プログラム

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH117405A (ja) * 1997-06-17 1999-01-12 Fujitsu Ltd ファイル共有システム
US8417666B2 (en) * 2008-06-25 2013-04-09 Microsoft Corporation Structured coauthoring

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11338754A (ja) * 1998-05-22 1999-12-10 Mitsubishi Electric Corp 共有ファイル管理システム
JP2006011936A (ja) * 2004-06-28 2006-01-12 Konica Minolta Business Technologies Inc 共有ファイル管理システムおよびサーバー
JP2006285867A (ja) * 2005-04-04 2006-10-19 Nec Corp ファイル管理システム、監視サーバ、ファイルサーバ、ファイル管理方法、及び、プログラム
JP2007328392A (ja) * 2006-06-06 2007-12-20 Fuji Xerox Co Ltd 文書編集システム、文書編集制御サーバ、サーバ用プログラム、ユーザ端末、端末用プログラム

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3783495A4 (en) * 2018-04-19 2022-01-05 Murata Machinery, Ltd. EXCLUSIVE ORDERING SYSTEM AND PROCEDURE
CN113656512A (zh) * 2021-10-21 2021-11-16 浙江太美医疗科技股份有限公司 数据解锁方法、装置、设备和存储介质

Also Published As

Publication number Publication date
JP2012058960A (ja) 2012-03-22
TWI475398B (zh) 2015-03-01
JP5373723B2 (ja) 2013-12-18
TW201217986A (en) 2012-05-01

Similar Documents

Publication Publication Date Title
JP5373723B2 (ja) 共有ファイル管理システム、その制御方法、およびプログラム
JP4060272B2 (ja) ピア・ツー・ピア・コラボレーション・システムを管理するための方法および装置
CN102713886B (zh) 跨越多个计算设备的漫游应用设置
CN105262588B (zh) 基于动态口令的登录方法、账号管理服务器及移动终端
CN102541552B (zh) 条件延迟排队
US7937432B2 (en) State transition management according to a workflow management policy
US8250132B2 (en) Managing messages related to workflows
US9558341B1 (en) Integrated user profile administration tool
JP5318719B2 (ja) 端末装置及び端末装置におけるアクセス制御ポリシー取得方法
JP4354950B2 (ja) 情報処理装置、情報処理方法、コンピュータプログラム、及び記憶媒体
CN110502487B (zh) 一种缓存管理方法与装置
US20130145277A1 (en) Graphical user interface for electronic file sharing
US20080263456A1 (en) Graphical user interface for electronic file sharing
JP2009207122A (ja) 認証印刷のための制御装置、システム及び方法
CN101978665A (zh) 对网络通信请求的选择性过滤
JP5011965B2 (ja) 情報の管理方法及び情報処理装置
JP5090809B2 (ja) 管理サーバおよび管理方法およびプログラムおよび記録媒体
JP4191239B2 (ja) アクセス権限制御システム
CN109361757A (zh) 一种数据传输方法、装置及计算机可读存储介质
CN114499905B (zh) 应用账号更换绑定的方法、装置、计算机设备和存储介质
KR100727057B1 (ko) 메시지 상태 점검 방법 및 시스템
JP5532040B2 (ja) 情報処理装置、情報処理システム、制御方法、及びプログラム
US20070250507A1 (en) Electronic file sharing
JP5302712B2 (ja) クライアント端末、ユーザ管理方法、端末管理プロセッサ、プログラム
AU2007305072A1 (en) Method and system for controlling the release of data for multiple-level security systems

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11823352

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11823352

Country of ref document: EP

Kind code of ref document: A1