201217986 六、發明說明： 【發明所屬之技術領域】 本發明係關於一種分享檔案管理系統、其控制方法及 程式’尤其是關於由伺服器、複數個客戶、及將此等相互 連接之網路構成且該伺服器儲存該複數個客戶分別可存取 之分享檔案之分享檔案管理系統、其控制方法及程式。 【先前技術】 以往，複數個客戶分享並同時編輯儲存於伺服器之一 個分享檔案之情形’ 一般而t，設成在一個客戶編輯分享 檔案時其他客戶無法編輯此分享檔案之狀態（以下，稱為「鎖 定狀態」），確認一個客戶結束分享檔案之編輯後其他客戶 可編輯之狀態（以下’稱為「未較狀態」）。此處，讀出分 :檔案並編輯時將此分享檔案設成鎖定狀態之作業稱為 簽出」’結束分享稽案之編輯並將此分享檀案設成未鎖 定狀態之作業稱為「簽入」。 此種方法中，雖不會產生 享檔案而產生資料之不一致， 享檔案，則其他客戶無法進行 佳。 複數個客戶同時編輯一個分 但若一個客戶長時間編輯分 此分享樓案之編輯，效率不 相對於此，已提案將一個分享樓案分成複數個部分區 就各部分區域管理客戶之存取之技術(例如，參照專利 =此技術中，即使為了編輯分享㈣之中某個部分 域而存取該部分區域，亦會有該部分區域已被一個客戶 201217986 2鎖定狀態之情形，在此情形其他客戶無法 :域’即使能存取亦成為無法編輯之讀取 ：： 二-以’以-個客戶編輯此分享檔案之使用者，= 子 免產生上述問題，力八* 未了避 簽出。 77享檀案之編輯時必須隨時想到簽入/ 專利文獻1 :日本特開2。。5 —3〇 1 838號公報 【發明内容】 ㈣然而由於與分享檔案之編輯相關之所有使用者並不 習慣進行“/簽H 使用者並不 ^ m ^ ^ I有馮了編輯分享檔案而簽出之 使用者在編輯作業結束後忘記簽入 合出之 服器或進行編輯作業 月/ ，亦會有伺 隨之分享檔宰唯持此等之網路故障所伴 此益法享擋案亦維持鎖定狀態而長時間放置，因 匕…法回效率管理分享檔案。 本發明係為了解決上述問題 一種能争古β 攻其目的在於提供 種此更阿效率管理分享檔案之分享 檔案管理^之㈣方Μ程式。、分享 本發明之分享檔案管理***， 針對複數侗Α \ /、備.狀態控制手段， 子複數個客戶分別可透過網路 個客戶夕绝is扣 刀早私案，根據一 吝戶之編輯開始要求設成僅 案之鎖定狀態，且根據來自該—個客固戶客::編輯該分享播 成將該分直0也 戶之，扁輯結束要求設 风將荔刀享檔案解除鎖定狀態之 恃手段，枝—± 鎖疋狀悲；狀態資訊記 隐乎奴，儲存表示該分享檔案為鎖 疋狀態或非鎖定狀態之 4 201217986 記:1 ’以及狀態貝訊輸出手㉟，將儲存於該狀態資訊 ‘·、又之該刀享檔案之狀態資訊輸出至該複數個客 每一個。 又’該狀態控制手段，A w ^ . 奴在從該一個客戶要求該編輯結 ;、時’在要求該編輯結束要求起經過既定時間後，將 該分享檔案設成未鎖定狀態亦可。 再者，該複數個客戶分別進一步具備與該 之中編輯該分車授宏夕# 2 ^ ^ 铒亥刀享檔案之該-個客戶透過該網路通訊之通訊 手段亦可。 又’進-步具備預約手段亦可，該預約手段預先受理 =其他客戶之對設成較狀態之該分享檔案之編輯開始 ’在該狀態控制手段該分享檔案成為未鎖定狀離之後 =將該分享㈣作為較狀態並僅使該其他客戶編輯該 分予檔案。 ^再者，進一步具備強制結束手段亦可，該強制結束手 段在該分享檔案設成該鎖定狀態後之經過時間達到閾值 時將該分享檔案強制地設成該未鎖定狀態。 本發明之分享檔案管理系統之控制方法，具備：針對 複數個客戶分別可透過網路存取之分享檔 個客戶之中-個客戶之編輯開始要求或編輯結束^ = 設成僅該-個客戶可編輯該分享檔案之鎖定狀態或解除該 鎖疋狀態之非鎖；t狀態之步，驟；將至少&含該分享檐案為 該鎖定狀態或該非鎖$狀態之狀態資訊儲存於記憶手段之 步驟；以及將儲存於該記憶手段之該分享槽案之狀態資訊 201217986 輸出至該複數個客戶之每一個之步驟。 本發明之程式’使電腦實現下述功能·· 戶分別可透過網路存直 设數個客 中一個客戶之編輯根據該複數個客戶之 一個客戶可編束要求分別設成僅該 μ 7刀享檔案之鎖定狀態或解除該 之非鎖定狀態之功能；將至少包含該分享播 μ卜貞疋狀態之狀態資訊儲存於記 及將儲存於哕々β * 仅疋功此，以 、-退憶手段之該分享檔案之狀態資 複數個客戶之每-個貝。扎輸出至该 根據本發明，儲存至少包含分享檔 鎖定狀離之壯能次〜 只疋狀態或非 個客戶:每一’將分享㈣之狀訊輪出至複數 母個，藉此操作客戶之使用者可容易掌握八一 享樓案。由其他使用者編輯中，因此可更高效率管理分 在要X在從編輯分享㈣之客戶要求編輯結束要求時， # w編輯結束要求起經過既定時間後，將該分享檔 «又成未鎖疋狀態’藉此即使編輯分享擋案之绝 輯結束要求時，只要該客戶在該既定時間之期間 =開始要求’則能防止該分享檔案被其他客戶設成鎖定 再者，複數個客戶分別能在與客戶之中編輯分享權案 之者之間透過網路取得聯絡，因此希望編輯分享播案之客 戶彼此可進行交涉。藉此，可更高效率進行分享槽案 6 201217986 藉由進行下述預約，即在分享檔案為鎖定狀態時， 從複數個客戶之任一個要求編輯開始要求時，在該分享檔 案成為未鎖定狀態之後立刻使該客戶能編輯，可高效 行該分享檔案之編輯作業。 再者在刀享檔案设成鎖定狀態後之經過時間達到閾 值時’㈣分享㈣設成未敎狀態並強㈣結束該分享 檔案之編輯作業’藉此可抑制分享檔案被某個客戶長時間 編輯導致其他客戶無法編輯之情形。 【實施方式】 接著，參照圖式詳細說明本發明之實施形態。此外， 各圖中，對相同構成要素賦予相同符號。 (實施形態） 首先，參照圖1〜圖3說明本發明實施形態之分享檔案 官理系統100之構成。本實施形態之分享檔案管理系統 100，如圖1所示，係由伺服器10、N台客戶2〇(2〇_ ―N)、及將此等相互連接之LAN(L〇cal Area Netw〇rk)3〇構 成。 其中’伺服1§ 10具備未圖示之CPU、記憶裝置、輸出 入裝置、及通訊介面，功能上，如圖2所示，具備記憶部 11、狀態控制部12、狀態資訊記憶部13、預約部14、狀態 資訊輸出部15、強制結束部16、及通訊部17之各功能部。 記憶部11係儲存客戶2〇(2〇— —N)分別可存取之 分享槽案等之資料者。此處，分享㈣係指複數台電腦（客 201217986 户2〇)分別可透過網路（以_)存取之檔幸β 狀態控制部u依據來自客戶2〇之 享檔案設成僅客戶20— 1〜^ 要求將刀 Ν之中一個客戶能 定狀態，或依據來自該客戶 “輯之鎖 之編軏結束要求設成解除該分 旱槽案之鎖疋狀態之非鎖定狀熊。 狀態13儲存包含儲存在記憶部U之分享 槽案為鎖定狀態或非鎖定狀態之分享槽案刀享 預約部Μ進行下述預約，即從客戶2Q對設2定狀 態之分享檔案有編輯開始要求時，解除 狀態之後立刻使該客戶20能編輯。 案之鎖疋 狀態資訊輸出部15讀出儲存在狀態資訊記憶部"之 狀態資sfL並輸出至客戶2〇。 強制結束部1 6，在分寒持安、^ & 在刀旱檔案被客戶20—1〜2〇—Ν^φ 一個客戶簽出成為鎖定狀態下經過長時間（例如，心 2〇小時等）時，將該分享檔案強制設成非鎖定狀離。- 通訊部η透過LAN30實現在與客戶2〇—n 間進行通訊之功能。 < 另一方面，客戶20具備未圖示之咖、記 出入裝置、及通訊介面，功能上，如輸 部21、操作部22、及通訊聯絡部^ 〇備顯不 顯示部21為顯示器裝置等顯示各種晝面者。 操作部22根據鍵盤或滑鼠等使用者之操作 數字、記號、方向等之訊號輸出 3201217986 VI. Description of the Invention: [Technical Field] The present invention relates to a shared file management system, a control method thereof and a program, in particular, relating to a server, a plurality of clients, and a network connected to each other And the server stores the shared file management system, the control method and the program of the shared file accessible by the plurality of customers respectively. [Prior Art] In the past, a plurality of customers shared and simultaneously edited a shared file stored on the server's general 't', and the other customers were unable to edit the shared file when a customer edited the shared file (hereinafter, For the "locked status", confirm the status that other customers can edit after editing the shared file (hereinafter referred to as "not compared status"). Here, the readout point: the operation of setting the shared file to the locked state when the file is edited and edited is called "checkout", the operation of ending the sharing of the audit file and setting the shared copy file to the unlocked state is called "signing". Enter." In this method, although there is no inconsistency in the data generated by the file, and the file is enjoyed, other customers cannot perform well. A number of customers edit one point at the same time, but if a customer edits the share of the building for a long time, the efficiency is not relative to this. It has been proposed to divide a shared building into multiple parts for the management of each part of the regional management customers. Technology (for example, refer to the patent = this technology, even if a part of the area is accessed for editing a part of the sharing (4), there will be a situation where the part of the area has been locked by a customer 201217986 2, in this case other The customer can't: the domain 'can't be edited even if it can be accessed:: 2 - The user who edited the shared file with '---------------------------------------------------------------- In the editing of the Tan Tan case, you must always think of the check-in / Patent Document 1: Japanese Special Report 2. 5 -3〇1 838 [Invention] (4) However, since all users related to the editing of the shared file are not It is customary to "/sign H user does not ^ m ^ ^ I have Feng edited the shared file and the checked out user forgets to check in the outfit server or edit the month after the editing job ends. / , there will be a share of the network to maintain the file, and this network failure is accompanied by this benefit law. The file is also locked for a long time, because the law returns to the efficiency management sharing file. The present invention is To solve the above problems, one can compete for the ancient beta attack. The purpose is to provide a more efficient management and share the file sharing file management ^ (4) square program. Share the shared file management system of the present invention, for the plural 侗Α \ /, preparation The state control means, the sub-multiple customers can separately set up the lock-only status of the case through the online customer's eve, and according to the editing of a tenant, according to the customer-only ::Editing the sharing broadcast will be the direct 0-home, the end of the flat series requires the wind to save the file to unlock the file, the branch - ± lock sorrow; state information remembers slaves, storage Indicates that the shared file is locked or unlocked. 2012 17986 Note: 1 'and the status of the output of the button 35, the status information stored in the status information', and the status information of the file is output to the complex Each of the guests. 'The state control means, A w ^. The slave asks the editor from the customer;; 'Set the share file to unlock after the specified time has elapsed after requesting the editor to finish the request. In addition, the plurality of customers respectively further have communication means for communicating with the customer through the network communication with the user who edits the car to the Hongxi #2 ^ ^ 铒 刀 knife. Further, the advancement means may be provided with an appointment means, and the reservation means may be accepted in advance = the editing of the shared file of the other customer is set to the state in which the shared file becomes unlocked after the state control means = Sharing (4) as a state and only allowing the other customer to edit the distribution file. ^ Further, there may be further a forced termination means, which will be when the elapsed time after the shared file is set to the locked state reaches a threshold The share file is forcibly set to the unlocked state. The control method of the shared file management system of the present invention has: for a plurality of customers, each of which can be accessed through a network, a client, a client, an editor, a request to start or an editor to finish ^ = set to only the client Editing the locked state of the shared file or unlocking the locked state; the step of t state, storing at least the status information containing the shared file as the locked state or the unlocked $ state in the memory means And the step of outputting the status information 201217986 of the shared slot stored in the memory means to each of the plurality of clients. The program of the present invention enables the computer to realize the following functions: • Each user can directly set up a number of customers through the network to edit one of the customers according to the requirements of one of the plurality of customers. The function of locking the file or unlocking the unlocked state; storing the state information including at least the state of the shared broadcast buffer in the record and storing it in the 哕々β* only to do this, to - recall The means of sharing the file means the number of customers per customer. According to the present invention, the storage includes at least the strength of the sharing file lock-up-only status or non-customer: each 'shared (four) message is sent out to the plurality of mothers, thereby operating the customer Users can easily master the Bayi Building case. It is edited by other users, so it can be managed more efficiently. When the user wants to edit the end request from the editor (4), the #w editing end request is passed after the specified time, and the share file is again unlocked.疋 ' ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’ ’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’’ The contact is made through the Internet between those who edit and share the rights with the customer, so it is hoped that the customers who edit the sharing broadcast can negotiate with each other. In this way, the sharing file can be made more efficiently. 6 201217986 By making the following reservation, when the sharing file is locked, when the request is requested from any of a plurality of customers, the sharing file becomes unlocked. Immediately afterwards, the customer can edit the file and edit the shared file efficiently. In addition, when the elapsed time after the knife is set to the locked state reaches the threshold value, (4) sharing (4) is set to the unfinished state and strong (4) ending the editing operation of the shared file 'to prevent the shared file from being edited by a customer for a long time A situation that prevents other customers from editing. [Embodiment] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the drawings, the same components are denoted by the same reference numerals. (Embodiment) First, the configuration of the shared file management system 100 according to the embodiment of the present invention will be described with reference to Figs. 1 to 3 . As shown in FIG. 1, the shared file management system 100 of the present embodiment is composed of a server 10, N clients 2〇(2〇_―N), and a LAN connected to each other (L〇cal Area Netw〇). Rk) 3〇 constitutes. The 'servo 1 § 10 includes a CPU, a memory device, an input/output device, and a communication interface (not shown). Functionally, as shown in FIG. 2, the memory unit 11, the state control unit 12, the state information storage unit 13, and the reservation are provided. Each of the functional units of the unit 14, the status information output unit 15, the forced end unit 16, and the communication unit 17. The memory unit 11 stores information such as a share slot that can be accessed by the customer 2〇(2〇-N). Here, sharing (4) means that a plurality of computers (guest 201217986 households 2〇) can be accessed through the network (by _), and the beta state control unit u is set to only the customer 20 based on the files from the customer 2〇— 1~^ Requires that one of the customers in the knife can be in a state, or according to the end of the compilation of the lock of the customer, the non-locking bear that is set to release the lock state of the dry tank case. State 13 storage The sharing slot containing the shared slot stored in the memory unit U is in a locked state or an unlocked state, and the reservation unit performs the following reservation, that is, when the client 2Q requests the editing of the shared file in the fixed state, the request is released. Immediately after the status, the client 20 can edit the file. The lock status information output unit 15 reads the status attribute sfL stored in the status information storage unit and outputs it to the client 2〇. Forced end unit 1 6 Ann, ^ & In the knife and drought file is the client 20-1~2〇-Ν^φ When a customer checks out and becomes locked, after a long time (for example, heart 2 hours, etc.), the shared file is forcibly set to Non-locking away. - Communication Department η through The LAN 30 realizes a function of communicating with the client 2 〇 - n. On the other hand, the client 20 includes a coffee, a recording device, and a communication interface (not shown), and functions such as the transmission unit 21 and the operation unit 22, And the communication unit 2 displays the various types of facets for the display device, etc. The operation unit 22 outputs signals according to the operation numbers, symbols, directions, etc. of the user such as a keyboard or a mouse.
Cpu。 广^具備之未圖示之 8 201217986 通訊聯絡部23透過LAN30實現在與飼服器ι〇或其他 客戶2 0之間進行通訊之功能。 —接著，說明狀態資訊記憶部13儲存之分享檔案之狀態 圖4係顯示狀態資訊記憶部13儲存之分享檔案管理表 之構造之-例的圖。狀態資訊記憶部13儲存之分享檔案管 理表，如圖4所示，包含由「分享檔案％、「旗標以」、 「編輯者1D」、「旗標F2」、「預約者⑴」、及「更新時 刻」之欄位構成之記錄。 「分享檔案ID」係用以一義地特定分享檔案之⑴，能 使用例如各分享標案之路徑或對各分享棺案一 文字列等。 々 「旗標F1」係表示對應之分享檔案是否被客戶 \亦即表示該分享檔案為鎖定狀態或非鎖定狀態。具體 而吕’在該分享標案為非鎖定狀㈣輸人值「q」 狀態時輸入值「1」。 ’、’、又 「編輯者ID」係表示在該分享權案為編輯中時用以— 義地特定編輯該分享構案之客戶之m，例如，輸人 位址、說（媒體存取控制）位址、認證使用者 rr旗標、F1」之值為、時，藉由「編…二 疋之f2〇以外之其他客戶2〇無法編輯該分享檔案。此 外，在該分享檔案不為編輯中時「旗標fi」之值為「' 「編輯者1D」之襴位之值成為NULL。 」’ 「旗標F2」係表示在該分享稽案被某個客戶編輯中 9 201217986 戶^F1」之值為而成為鎖定狀態時其他客 戶疋否已預約接著編輯之權利。具體而言，在該分享播案 未被預約時輸入值「0」，已預約時輪入值…。 用以一「I:者1D」係表示在該分享檔案之編輯權被預約時 用以二義地特定預約該分享檔案之編輯權之客戶之ID，例 口’，入客戶之ΠΜ立址、MAC位址、認證使用者名等。因 此，針對此「旗標F2」之值為「1之八直 業結束解除該鎖定狀態之後立刻能使藉由「::者在:輯:: 二=:該分享檔案。此外’若該分享《^ 值成為NULL。 '編輯者A之攔位之 編輯=!1刻」係'表示開始與該記錄對應之分享稽案之 編輯作業之時刻、或對編輯作業之途中所儲存之分享檔案 最後儲存之時刻。此係用於強制結束部16調查分享標案在 =狀態下是否經過長時間時。此外，在與該記錄對應之 刀享棺案不為編輯中時，此欄位之值成為null。 狀態資訊記憶部1 3俜囍由胳眘M 表儲存W之狀態=科輪入該分享槽案管理 接著，說明分享檔案管理系統1〇〇中之各動作。 A首先八，說明操作客戶20之使用者進行點擊顯示在顯示 =幸之之m㈣既定操作、㈣編輯用程式欲開始該分 享棺案^扁輯作業時之分享擋案管理系統⑽之動作。如 ΐ达則=呆作客戶2〇之使用者欲開始分享樓案之編輯作 …戒聯絡部23對飼服器10傳送通知分享擋案之編 10 201217986 輯開始要求之訊號。若伺服器10從客戶2〇 始要求，則參照分享檔案管理表決定是否承認編輯作= 以下，使用流程圖說明其内容。 圖5係顯示本發明實施形態之分享槽案管理系統⑽ 透過LA_從客戶2°受理分享檔案之編輯開 始要求時執行之編輯開始常式的流程圖。 首先，若舰器H)從客戶2G受理分享㈣⑴及特定 該客戶20之ID(以下，稱為「客戶1〇」）及分享楷案之編輯 開始要求’則客戶20參照分享檔案管理表，讀入與該分享 =對記錄之「旗標F1」及「旗標F2」(步驟議)， 調—旗払F1」之值是否為「〇」（步驟s"〇” 是…「旗標A之值為A時，(步驟_: 之處理厂旱㈣不在編輯中，進行對該分享檔案簽出 成為dr行該客戶20可對該分享檔案拼他性編輯之 成為鎖疋狀態之處理。 具體而言，首先，狀態控制部12將以分享槽案 生關聯之記錄之「旗標F1 ^產 者一…2。之客戶ID，更在新為二^ 在時刻」（步驟S120)。如上述，藉々」輸入「現 新故「1 j 將旗仏F1」之Y杳Φ 新為】」，狀態控制部12限制藉由 更 客戶20以外之客戶2〇存取該分享檔案。 」特定之 接著，通訊部17對該客戶2〇 、 WO)，對所有客戶2〇—卜2〇— 載4享槽案（步騍 輯中之消息(步驟_)，結束編輯享槽案成為編 11 201217986 藉由步驟S140之處理’在客戶— N，： 槽案成為編輯中之消息係以下述方式輸出。 I刀享 圖6係以大廈管理系統相關之複數個分享檔 之情形為例來顯示本發明實施形態之分享檔案理系 1 〇 〇中用L”办 ’、理系統 態之監列畫面認顯示在客戶20之顯示部21之分享樓案之狀 狀離昧 —例。圖6⑷係顯示所有分享檔案為非鎖定 “之監測晝面’圖6(b)係顯示某個分 狀態時之於制蚩二于仏茶成為鎖疋 之各八直，在顯示在大厦之各區域 狀離:=案之分享樓案名之旁邊附有表示該分享檔案之 為鎖定狀離’為非鎖定狀態時原本白色四角形之圖像因成 此：：態而變化成帶有「X」標記之四角形之圖像。因 ▲操作客戶20之使用者開啟該晝面確認位在分享禮案之 別之圖像之狀態，藉此能確認該分享檔案是否為編輯中。 鎖二操2戶Μ之使用者’例如，點擊在編輯中成為 Μ 旱槽案之分享棺案名，藉此亦能使用通訊聯 =3二功能對編輯該分享檑案之客"。傳送訊息或進 兮書 1述’在客戶2〇開啟分享檔案之監測畫面崖在 i彼此取^丁既定操作’藉此希望分享楷案之編輯之使用 Γ:眚可交涉以解除分享槽案之鎖定狀態。 此卜，在本實施形態雖以樹狀結構之 =:::為可確認分享檔案之狀態之輪出狀態，則顯 7態為何者皆可，例如以表形狀來顯示亦可。 返回圖5之步驟su〇之處理之說明。 在步驟si ίο之處理中，「旗標fi」之值為「1」時（少 12 201217986 驟S 1 1 0 :否），剌辦 .ffi 斷ο刀享檔案為編輯中，進一步&邮「 標F2」之值是否為「0」_S15()卜 Μ斷「旗Cpu.广广的未图8 201217986 The communication department 23 realizes the function of communicating with the feeder ι〇 or other customers 20 via the LAN30. - Next, the state of the shared file stored in the state information storage unit 13 will be described. Fig. 4 is a view showing an example of the structure of the shared file management table stored in the state information storage unit 13. As shown in FIG. 4, the shared file management table stored in the status information storage unit 13 includes "share file %, "flag", "editor 1D", "flag F2", "reservation (1)", and A record of the fields of the "Update Time". The "Shared File ID" is used to uniquely share a file (1). It can use, for example, the path of each shared document or a list of shared files. 「 “Flag F1” indicates whether the corresponding shared file is locked by the customer\, that is, the shared file is locked or unlocked. Specifically, Lu's input value "1" when the shared title is non-locked (four) input value "q" status. ', ', and "Editor ID" means that when the sharing rights are edited, the client who uses the sharing structure is specifically edited, for example, the input address, said (media access control) When the address, the authenticated user rr flag, and the value of F1" are used, the shared file cannot be edited by the other users other than the f2〇2. In addition, the shared file is not edited. The value of the "flag fi" value of "" "Editor 1D" is NULL. "Flag F2" indicates the right of other customers to make an appointment and then edit when the shared account is edited by a customer and the value of 201215986 is ^F1". Specifically, the value "0" is entered when the share play is not reserved, and the value is entered when the reservation is made. An "I: person 1D" system indicates that the ID of the customer who ambiguously reserves the right to edit the shared file when the editing right of the shared file is reserved is taken as an example, the address of the customer, MAC address, authentication user name, etc. Therefore, the value of this "flag F2" is "1 of 8" and the immediate release of the lock state can be immediately followed by ":: in: series:: two =: the shared file. In addition, if the share "The value of ^ becomes NULL. 'Editor of Editor A's == 1" means 'the time at which the editing of the shared audit file corresponding to the record is started, or the shared file stored on the way to the editing job. The moment of storage. This is used to force the end section 16 to investigate whether the shared standard has passed a long time in the = state. In addition, the value of this field becomes null when the file corresponding to the record is not in edit. The state information storage unit 1 3 is stored in the state of the lock table by the key sheet M = the round of the share slot management. Next, each action in the shared file management system 1 is explained. A first eight, the user who operates the client 20 clicks to display the action of the shared file management system (10) when the display is displayed on the display m = 4 (four) predetermined operation, and (4) the editing program wants to start the sharing operation. For example, ΐ达==Users who are customers 2〇 want to start sharing the edits of the building... The liaison department 23 sends the notification sharing file to the feeding device 10 10 201217986 The signal to start the request. If the server 10 requests from the client 2, it is determined by referring to the shared file management table whether or not the edit is made = below, and the contents thereof are explained using a flowchart. Fig. 5 is a flow chart showing the editing start routine executed when the shared slot management system (10) according to the embodiment of the present invention executes the editing request from the client 2° through the LA_. First, if the ship H) accepts the sharing (4) (1) from the customer 2G and the ID of the specific customer 20 (hereinafter referred to as "customer 1") and the editing of the sharing case, the client 20 refers to the shared file management table and reads Enter and share = "flag F1" and "flag F2" (step discussion), whether the value of flag - F1 is "〇" (step s "〇" is... "flag A When the value is A, (step _: the processing plant drought (four) is not in the editing, the checkout of the shared file becomes the dr line, and the client 20 can edit the shared file to become the lock state. In other words, the state control unit 12 will "the customer ID of the flag F1^producer one...2." in the record associated with the shared slot file (step S120). By inputting "the new one", "Y j Φ new" of the flag f1", the state control unit 12 restricts access to the shared file by the client 2 other than the customer 20. "Specific success , the communication department 17 for the customer 2〇, WO), for all the customers 2〇—卜2〇—loading 4 slots (in the step series) The message (step _), the end of the edit enjoyment case becomes edited 11 201217986 by the process of step S140 'in the customer - N,: the slot is edited in the message is output in the following way. I knife enjoys Figure 6 is the building The case of managing a plurality of sharing files related to the system is used as an example to show that the shared file system in the embodiment of the present invention is displayed in the display unit 21 of the client 20 by using the "L" in the system. The shape of the building is different from that of the case. Figure 6 (4) shows that all the shared files are not locked "monitoring face" Figure 6 (b) shows a certain state when the system is locked into the lock Each of the eight straight, in the display of the various areas of the building: = the case of the shared building case is accompanied by a picture indicating that the shared file is locked from the 'unlocked state' of the original white quadrangle image because of this: The state changes to an image with a square of the "X" mark. The user who operates the client 20 opens the confirmation of the image in the state of sharing the image of the gift, thereby confirming the shared file. Whether it is for editing. Lock two operations 2 households The user's name, for example, clicks on the share name of the sloppy case in the editor, so that the user can also be edited using the communication link = 3 function to transmit the message or enter the book 1 Said 'in the customer 2 〇 open the sharing file monitoring screen cliff in i to take each other's established operation 'by this hope to share the use of the editor of the Γ Γ 眚 眚 交 交 交 交 交 交 交 交 交 交 交 交 交 交 交 交 交 交 交 交 交 交 交 。 。 。 。 In the present embodiment, the =::: tree structure is a round-up state in which the state of the shared file can be confirmed, and the display state can be displayed, for example, in a table shape. Return to the step of FIG. In the process of step si ίο, when the value of "flag fi" is "1" (less 12 201217986 S 1 1 0 : no), the file is edited. , further & post "F2" value is "0" _S15 () Μ Μ "" flag
「旗標F2丨之信ϋ r λ I 值為〇」時（步驟S150 :是），划啦— :案仍未預約，預約部14進 〜分 「旗標之值更新為、，且在「…H，將 客戶20之客戶在預約者ID」輪入該 疋客戶iD(步驟S]6〇)，結束編輯 輯分享檔案之權限從現扃 *式。關於編 客戶μ之移動Β=Γ 戶20往進行預約處理之 〈移動時序將於後述 預約處理之前， 在進仃步驟S160之 以針對是否f 之^部21自動跳出顯示 進仃預約確認使用者之意思之處理亦 相對於此’「旗樑F2」之值 判斷該分享檔案已祜 ’」、，驟s 150 ··否）， 束編輯開始常式。、.預約部14不進行預約處理，結 接著，說明操作客戶20之使用者結束 案之編輯之程今弋仃为享播 编蛭你聲 式或關閉以此程式編輯之分享檔案等而牡束 =業時之分享槽案管理系統1〇〇之動作。如上述.，若 絡部=之t用者結束分享標案之編輯作業，則通訊聯 1號“彳_ 5服益1G傳送通知分享㈣之編輯結束要求之 照分享器Μ從客”°被通知編輯結束要求，則參 並解卜S^理表’參照該分享槽案是否已進行預約處理 容。示分享檔案之鎖定狀態。以下’使用流程圖說明其内 =7係顯示本發明實施形態之分享稽案管理系統⑽ 又理分享檔案之編輯結束要求時伺服器丨〇執 13 201217986 行之編輯結束常式的流程圖。 首先，狀態控制部1 2確認在既定時間（例汝 ::少等)以”否再次有來自相同客戶2。之編二 (亦P編輯結束要求之取消）（步驟S200)。 在既定時間以内再次有來自相同客戶2 求時(步驟否)，不進行後述簽入，結束=始要 式。因此，不解除分享檀案之鎖定狀態，相同客戶Γ束节 編輯該分享檔案。 戶此繼續 如上述，狀態控制部14在既定時間僅受 戶2〇之編輯開始要求之原因在於，用以防止操作客戶2〇 之使用者㈣束程式等而結束分享㈣之編輯作 分享檔案被其他客戶20設成鎖定狀態而無法編輯、。… 編輯:=時再:無來自相同客… 亦即解除該分=:=由於對該分享_人， 進行以下之處理Γ、疋U成4非鎖定狀態，因此 之「I二參f分享檔案管理表，讀入該分享檔案之記錄 '」（步驟S210)，判斷該「旗標F2」之值是否為 0」（步驟S220)。 」m疋否為 讀入之旗標F2」之值為「〇」時（ I::㈣未預約，狀態控制部心行簽入:處理 將、「旗標A之值更新為'， 更新為NULL(步驟s ‘、NUU；，將「更新時刻」之值 )。又，通訊部17對所有客戶通知 14 201217986 该分享檀案可編輯之消自，此 科（步驟S240)，結束 此處，若通訊部1 7對宏肖 、，。束常式。 吝戶20— 1〜2〇—N通知 編輯之消息，則如上述，在客戶2〇叫〜刀享檔案可 2 1，開啟分享檔宰之妝能 之顯示部 分享槽案名之旁邊之圖像，可知從帶有享棺案之 形變化成白色之四角形。 ^ 」枯记之四角 則能容易判斷該分梓宰右使用者開啟此監測畫面 刀手榣莱疋否為編輯中。 另方面°貞入之「旗標F2」之值為「1技^ 否），判斷該分享㈣已預約，狀態控制部 分享檔案之編輯之客戶2〇承認編輯之處理。預相 具體而言，狀態控制部12在「編輯者％輸入 者1D」，將「預約者ID」更新為Νυιχ 預約 值更新為「〇」（卡驟旗k F2」之 …二 認對該分享檔案之編輯要求之 S26〇)，結束編輯結束常式。此處，作為針預约 之客戶20通知承認編輯要求之消息之方法，可== 預約之宏·自〇 λ « J举出例如在 時_由自f ^ 21開啟上述分享檔案之監測畫面 寺藉由自動跳出顯示承認編輯要求之消息、 方法。如上述，由於進行對 — 鈴聲之 、 對預約之客戶20通知承句、说錯西 ，之4息之處理，因此操作客戶20 分享檔柰少也& 使用者不需為了確認 子檔案之狀態而刻意存取伺服器10，能 享檔案之編輯要求之消息之通 5“ 技 透杲中在其他作業。 者’使用圖8所示之程序批制 態之分隼沪安& β ㈣圖說月本發明實施形 刀享檔案管理系統1〇〇之動作之一例。 15 201217986 此外，為了方便說明，在 及客戶20—2之2二客戶< *制圆僅描繪客戶20— i 首先，若:用：戶戶：Γ戶20之台數並不限於“。 在飼服…分享檔宰I:1輯之之使用者執行用以開始館存 „ 要求（步驟§300)，伺服哭1Λ 執行使用® 5說明之編輯開 1〇 要炎……+輯開始以(步驟S310)。此處，被 !求編輯開始要求之分享檔案未被任何人編輯，分享檔宰 官理表之該記錄之「旗椤 刀旱檔案 〜。 褀铩F1」之值成為「0」。接著，由於 承§忍編輯開始要求，因此 ; C140 ,» A 迴仃在圖 5 之步驟 S120、Sl3〇、 广之一般之簽出處理，亦即進行下述處理，將八享 檔案管理表之該記錄之「旗標Fl」 處=享 輯者1〇」輸入客戶20— i之客戶二值更新為…在「編 現在時刻，對客戶2。叫：在「更新時刻」輸入 進仃/刀享檔案之下載，對客戶20 ， 通知該分享檔案成為較狀態之消息。 接著，若操作客戶2〇~2夕你屯& 之分享檔案之操作，則從客戶^ 用以編輯相同 分享㈣之編輯開始要求(^20—2對飼服器1〇傳送對該 在圖 求^ S32〇)，伺服器10再次執行 在圖5說明之編輯開 fa ^ , °式驟S330P此處，被要求編 輯開始要求之分享檀岽 ”被客戶20 — 1編輯，分享檔案管 理表之4 s己錄之「旅择 示」之值為「1」。因此，來自客戶 「二之編輯開始要求不被承認，在圖5之步驟S15。判斷 粒而^2」之值是否為「0」。若該分享播案仍未被預約編 =旗標F2」之值為「G」，則在圖5之步驟S16〇將「旗 ㈢」之值更新為…且在「預約者m」輸入客戶2。_2 201217986 之客戶ID。 接著，若操作安 v ^ 客戶20— 1之使用者進行覆蓋儲存下載 二二）=之#作’則該分享檔案上傳至伺服11 1〇(步驟 輯要求，則從客式關閉該分享檔案等結束該編 谷尸對伺服器！〇傳送編輯結束要 驟S350)，飼服器 服器10執仃使用圖7說明之編輯結束常式 驟S360)。此處，由於p、士办λ ;已被客戶20一2預約接著能編輯分享 檔案，分享檔幸營理志 午 '、巨里表之该記錄之「旗標F2」之值為「 因此在圖7之步驟S25〇在 輯者ID」輸入「預約者：錄之「編 )者1D」之值，將「預約者ID」之值更 新為NULL，將「短挪μ 丄 將旗私F2」之值更新為「〇」之後，在圖7 之步驟讓對客戶2卜2下載分享㈣且通知承認該分享 :案之編輯之消息。其結果’操作客彳20—2之使用者能 旱握客戶⑼―1之編輯結束之後立刻承認編輯，能立刻處 理分享檀案之編輯作業。 。若操作客戶20-2之使用者進行覆蓋儲存分享標案之 刼作’則該分享檔案上傳至伺服器1〇(步驟Μ?㈨。再者， ^以編輯用程式關閉該分享檔案等結束該編輯作業，則從 客戶20—2對伺服器10傳送編輯結束要求(步驟叫伺 H)再次執行使用圖7說明之編輯結束常式(步驟 ㈣〇)。此處’在上述步驟S360之處理，在分享稽案管理表 之該記錄「旗標F2」之值更新為'，解除對該分享標案 之預約。因此，在圖7之步驟㈣進行肯定之判斷，在圖 7之步驟S230將分享樓案管理表之該記錄之「旗標ρι」之 17 201217986 = ’將「編輯者ID」之值更新為舰 新時刻」之值更新為NULL， +更 力驟S240對客戶2() 客戶2。— U 20-2 f 編輯之消息。其結果，操作 之使用者不用刻意存 問’能掌握分享檔案成為可編輯。 1〇並询 。卜如上述，分享檔案之上傳（步驟S370)虚分享檀 J之編輯結束要求(步驟_)為彼此獨立之處…原因 於，預防客戶20系統故障時， 編輯作業之途中亦能將至此為止編輯之内案之 10之要求。 幵及門令上傳至伺服器 最後’說明針對長時間成為鎖定狀態之分享 制結束部強制地解除該鎖定狀態之方法。， 圖9係顯示伺服器1〇執行之強制 此痛兹I¥l I?- 术韦式之〉;IL程圖。 例如’每數十分或每數小時)執行。 此處，二管:表取出-個記錄(步驟_)。 之記錄之中「旗# 〃要抽出儲存在分享檔案管理表 者並取出即可。 者亦即权成鎖定狀態 接著，讀出此記錄之「更新時 刻」起之經過時間△ τ(步驟S4i〇)。此斤時 對應之分享衅安々μ & 更新時刻_]輸入有 覆蓋健存之二開始之時刻或編輯作業之途* 刀孕檔案之最後霜簦少卩生+丨 △Τ表示在編輯中之分享播覆二：此，經過時間 開始起之經過，夹“有覆羞錯存時從編輯作業 時間表不在編輯作業之途令覆蓋錯存之分 18 201217986 享槽案之最後覆蓋儲存起之經過時間。 接著，將以上述方式運算後之經過時間Δτ與閨值τι 及較其大之閾值T2比較（步驟S42〇)。此處，閾值τ2係設 定成可預測即使分享擋案之編輯作f已結束亦成為鎖定= 態之程度之時間，例如設定成1〇〜2〇小時。又，閾值以 係設定成較閾值Τ2短卜2小時程度之時間，用在將鎖定 狀態之分享檔案強制地設成非鎖定狀態之前進行其預告。 在經過時間ΔΤ為閨值T1未滿時（步驟S42〇、： T1)，由於分享檀案不會長時間成為鎖定狀態，因此不執 關於強制結束之處理。 S420. St間Μ為間值η以上且閾值T2未滿時(步驟 WT<T2)，再不久經過時間U成為閾值丁2以 編輯Π述成為將分享檔案之編輯處理強制結束，因此對 ==對應之分享檔案之使用者顯示催促分享檔案 示内=(!驟S43°)。此外，作為自動跳出之顯 為止催促分享檔案之儲存及至執行強制結束處理 為止之剩餘時間亦可。 丁），判在斷=時間△τ為閾值T2以上時（步驟S420:T2 < △ 鎖定狀離V:分享槽案之編輯作業已結束分享稽案亦維持 置，執行強制結束處理。具體…藉由： 編輯結束常式(步驟S440)，在對兮分隼 :案沒有預約時解除鎖定狀態成為非鎖定狀離在:：t 種處理，可抑制八編輯作業。藉由執行此 抑制刀享槽案被-個客戶20長時間設成鎖定狀 19 201217986 態導致其他客戶2〇無法編輯之事態。此時，僅在 從編輯之客戶受理編輯要求之圖7之步驟s2⑽省略亦可間 在執行編輯結束常式後，對將分享播案長時間設成鎖定狀 態之使用者藉由自動跳出通知將分享楷案 結束之消息(步驟S450)。 铒乍菜強制 針對分享檔案管理表之所有記錄確認執行 Γ=°:處理後(步驟_)，結束強制… / “旱檔案之中有被—個客戶2G長時間設成鎖 狀態者’則f㈣地解除該鎖定狀態，因 享棺案之編輯料。又，t ⑪ ^率進行分 h享㈣之使用者進行催促分享檔案之儲存之通 S430) ’因此即使分享檔案之編輯作業繼續亦可抑制地 解除鎖定狀態。 強制地 根據以上說明之太杳 兄月之本貫施形態之分享擋案管理 ⑽’伺服^ 1G’在分享檔案管理表，儲存表*分享檔案為 鎖定狀態或非鎖定狀態之「旗標F1」之值，若該「特7 之值更新則對所有客戶2。通知(圖5之步驟、圖'」 :驟Γ°);客戶20之使用者在顯示…啟用以管I: 之狀態，藉此能容易掌握二:宰？享標案之前之圖像 能高效率管理分享㈣否為編輯中。是以， 又，本實施形態之分享檔案管理系統10"， 分享棺案之客戶2。對伺服器i。有編輯結束 器10確認在既定時_如，1。秒或2〇秒等)以内是否再 20 201217986 次有來自相同客戶20之編輯開始要求 因此，編輯分享檔案之使用者誤結束7之步驟S200)。 時’若該使用者在既定時間之期間1 ^案之編輯作業 享檔案之編輯作業之操作，行用以開始該分 戶20設成鎖定狀態而無法編輯。 刀享檔案破其他客 再者，本實施形態之分享檔案管理 客戶20之使用者，開啟圖6所示之⑭100中’操作 行既定之操作’藉此使用通訊聯絡部案▲監測畫面，進 檔案之編輯之使用者彼此取得聯絡， 力此在希望分享 享檔案之鎖定I態。因此，可高 4行交涉以解除分 作業。 案之編輯 又’本實施形態之分享檔案管理系統 10在为享檔案被某個客戶2G編輯中而成為鎖定狀態=服器 =他客戶20有編輯開始要求時，進行接著:、分享二 案之預約(圖5之步驟咖)，編輯作業結束後立二享槽 享檔案並通知承認編輯之消息(圖7之步驟S25载分 可高效率進行分享檔案之編輯作業。 260)， 再者，本實施形態之分享檔案管理系統⑽ 器1〇藉由執行圖9說明之強制結束常式，若分享檔幸词： 有被-個客戶20長時間設成鎖定狀態者，：之中 鎖定狀態，因此能高效率進行分享檔案之編 除該 (變形例） 業。 此外’上述實施形態之分享檔案管理系統_ 說明_ U、狀態控制部12、狀態 ’雖 U β 13、預約 21 201217986 部1 4、狀態資訊輸出部丨$、 同之飼服器1〇,但如圖 lJ結束部16皆具備在相 亦可》 '、刀別具備在不同之伺服器 圖10所示之例巾，飼服器1〇叫 器W-2具備狀態控制部i -肯3己憶部11，飼服 14、狀態資訊輸出部15 二貝訊記憶部13、預約部 7之步驟⑽說明之對客戶執2= 於圖5之步驟_或圖 器1。-2進行以外之處理。 冑刀旱檔案之處理，伺服 之步=述實施形態之分享檔案管理系統⑽中，如圖5 之步驟SU0或圖7之步 Η圖5 分享播案之狀態在鎖定狀態與非鎖之定處::說明’雖說明在 服器1。對所有客戶2。通知，：:通=之間變動時從飼 如，口 I安ό V . 仁不通知亦可。此情形’例 :要客戶20分別每隔既定時間(例如，每數分 丨 y刀專）向伺服器10傳送用以詢 十 SQL即可。 刀旱檔案官理表之變動之 從舰器1G對所有客戶2。之通知僅在分享指 Z表有變動之消息，以此為動機客戶20(20—^、 )为別對伺服器1〇傳送詢問具體内容之sql文亦可。 又’上述實施形態之分享權案管理***1〇〇中，词服 透、客戶—20-n)係藉由Lan3〇連接，但不 达過LAN30而透過網際網路連接亦可。 ,再者，在上述實施形態之圖7之編輯結束常式，省略 受理來自在既定時間編輯分享檔案之客戶之編輯開始要求 22 201217986 (、扁輯，.Ό束要求之取消）之步驟S 2 〇 〇之處理亦可。 又，上述實施形態之分享檔案管理系統丨〇〇中雖說 明僅一個客戶20能預約，但受理來自複數個客戶之預 約亦可’此時，例如依照受理預約之順序使客戶2G能編輯 亦可。 再者，上述實施形態之分享檔案管理系統100中伺 服盗10雖具備預約部14或強制結束部16，但不具備此 亦可。 、 又 上述貫施形態中，將本發明說明為分享檔案管理 系統100之形態，但為分享槽案管理系統⑽之控制方法 之形態或組裝於分享權案管理系統100之程式之形態亦可。 此外，上述實施形態中，伺服器10或客戶20具備之 各功能部，可藉由伺服器1〇或客戶2〇分別具備之咖、 记憶裝置、及與外部機器之介面等之硬體資源與控制 硬體資源之程式協力運作來實現。用以實現此分享檔案管 理系統100之控制方法之程式，係以記錄在軟碟、CD — ROM、DVD-R〇M、或記憶卡等記錄媒體之狀態提供。 將從記錄媒體讀人# @ 皆 研'遛项入之私式寫入至記憶裝置，依據程 在實施形態說明之處理。 本發明可利用於分享檔案管理系統之製造業等。 L圃八間皁說明】 圖1係顯示本發明實施形態之分享檔案管理系 成的圖。 I構 23 201217986 案管理系統之伺 圖2係顯示本發明實施形態之分享檔 服器之一構成例的方塊圖。 享檔案管理系統之客 享檔案管理系統儲存 圖3係顯示本發明實施形態之分 戶之一構成例的方塊圖。 圖4係顯示本發明實施形態之分 之分享檔案管理表之一構成例的圖。 圖5係顯示本發明實施形態之分享檔 s叉糸統中從 客戶2纟理分享檔案之編輯開始要求時飼服器執行之 開始常式的流程圖。 圖6(a)、（b)係顯示本發明實施形態之分享檔案管理系 統中用以確認顯示在客戶之顯示部之分享檔案之狀熊之# 測晝面之一例的圖。 圖7係顯示本發明實施形態之分享檔案管理系統中從 客戶受理分享檔案之編輯結束要求時伺服器執行之編輯結 束常式的流程圖。 ° 圖8係顯示本發明實施形態之分享檔案管理系統之動 作之一例的程序控制圖。 圖9係顯示本發明實施形態之分享檔案管理系統中飼 服器執行之強制結束常式的流程圖。 圖10係顯示本發明實施形態之分享檔案管理系統之變 【主要元件符號說明】 10(10- 15 1〇_ 2) 伺服器 24 201217986 11 12 13 14 15 16 17 20(20— 1 〜20— N) 21 22 23 30 100 記憶部 狀態控制部 狀態資訊記憶部 預約部 狀態資訊輸出部 強制結束部 通訊部 客戶 顯示部 操作部 通訊聯絡部"When the flag F2 ϋ ϋ r λ I value is 〇" (step S150: YES), the plan is drawn: the case is still not reserved, and the reservation unit 14 enters and divides the "flag value to be updated to, and is in" ...H, the customer of the customer 20 is entered into the customer iD in the subscriber ID" (step S] 6), and the right to edit the shared file is ended. Regarding the movement of the client μ, the user 20 proceeds to the reservation processing. The movement timing is before the reservation processing described later, and in step S160, the user 21 automatically jumps out of the display to confirm the user's reservation. The meaning of the processing is also relative to the value of the "flag beam F2" to determine that the shared file has been 祜 '", step s 150 · · No), the bundle editing start routine. The reservation unit 14 does not perform the reservation processing, and then the operation of the user who operates the client 20 to complete the editing of the case is to edit the voice of the program or to close the shared file edited by the program. At the same time, share the action of the slot management system. As described above, if the user of the network = t is the end of the editing operation of the sharing standard, the communication link No. 1 "彳 _ 5 service benefits 1G transmission notification sharing (4) editing end request photo sharing device Μ guest" ° If the editor's end request is notified, then the reference is made to the S2 table to see if the reservation slot has been processed. Show the lock status of the shared file. The following is a flow chart showing the editing completion routine of the shared audit management system (10) according to the embodiment of the present invention when the shared audit management system (10) of the embodiment of the present invention is shared. First, the state control unit 1 2 confirms that there is a second time from the same customer 2 (or the cancellation of the P editing end request) (step S200) at the predetermined time (example:: less), etc. (step S200). Once again, there is a request from the same customer 2 (step No), no check-in is performed later, and the end = the initial form. Therefore, the lock status of the shared Tan case is not released, and the shared file is edited by the same customer. As described above, the reason why the state control unit 14 is only required to be edited by the user at a predetermined time is to prevent the user (4) bundle program or the like of the operation client from ending the sharing (4). The edit share file is set by the other client 20 It is locked and cannot be edited.... Edit: =Time again: No from the same guest... That is, the score is released =:=Because the share _ person, the following processing is performed, 疋U is 4 unlocked, so The "I two-part f share file management table reads the record of the shared file" (step S210), and determines whether the value of the "flag F2" is 0" (step S220). "m疋 is the value of the flag F2 read" when the value is "〇" (I:: (4) is not reserved, the state control department checks in: the processing will, "the value of flag A is updated to", updated to NULL (steps s ', NUU;, the value of "update time"). In addition, the communication unit 17 notifies all customers 14 201217986 that the shared copy of the file can be edited, this section (step S240), ending here, If the communication department is 7 to macro, and the bundle is normal. Seto 20-1~2〇-N informs the editor of the message, as described above, in the customer 2 screaming ~ knife to enjoy the file 2 1, open the share file The display of the makeup of the slaughter can share the image of the name of the slot, and it can be seen that it changes from a shape with a copy to a white square. ^ "The corners of the record can easily judge the opening of the user. This monitoring screen is not in the middle of editing. In addition, the value of "Flag F2" is "1 skill ^ no", and it is judged that the sharing (4) has been reserved, and the state control department shares the editing of the file. 2. Recognizing the processing of editing. Specifically, the state control unit 12 is in "Editor % Input 1D", Reservation ID is "updated Νυιχ reservation value is updated to" square "(card sudden flag k ... F2 'share of the two recognize the requirements of the S26〇 edit files), to finish the end of the routine. Here, as the method for the client 20 of the needle reservation to notify the message of the recognition request, the == reservation macro·self 〇λ «J cites, for example, at the time _ by the self-f ^ 21 to open the above-mentioned shared file monitoring screen temple The message and method of recognizing the editing request are displayed by automatically jumping out. As described above, since the client 20 is notified of the ringtone, and the client 20 is notified of the sentence, and the error is handled, the operation client 20 shares the file and the user does not need to confirm the status of the child file. Deliberate access to the server 10, can enjoy the message of the editor's request for the message 5 "Technology through the other operations." Use the program shown in Figure 8 batch state of the 隼 Hu An & β (four) map An example of the action of the file management system in the present invention is as follows: 15 201217986 In addition, for the convenience of explanation, the customer in the customer 20-2 2<*the circle only depicts the customer 20-i first, if : Use: Household: The number of Seto 20 is not limited to ". In the feeding service...Share the file of the I:1 user to start the library „ request (step §300), the servo crying 1Λ Execute the use of the 5 instructions to edit the opening 1 〇 want to inflammatory... (Step S310). Here, the share file requested by the editor is not edited by anyone, and the value of the flag of the file is "0. "." Then, due to the request of the editor, the C140, » A returns to the general check-out process of steps S120, S13, and 广 of Figure 5, that is, the following processing is performed, and the eight-access file management table is The "flag Fl" of the record = the sharer 1〇" enters the customer 20-i customer's binary update to... in the "editing time, to the customer 2. Calling: input in the "update time" By downloading the file, the customer 20 is notified that the shared file becomes a status message. Then, if you operate the customer's 2〇~2 屯 屯 & share file operation, then the client ^ is used to edit the same share (4) edit start request (^20-2 pair of feed device 1 〇 transfer to the map Seek ^ S32〇), the server 10 executes the edit fa ^ described in Fig. 5 again, ° step S330P here, is required to edit the start of the request to share the Tan Tan" edited by the customer 20-1, share the file management table The value of the "Travel Guide" recorded in 4 s is "1". Therefore, it is determined from the customer that the second editing request is not recognized, and the value of the judgment "2" in step S15 of Fig. 5 is "0". If the share broadcast is still not reserved, the value of the flag F2" is "G", then the value of "flag (3)" is updated to ... in step S16 of Fig. 5 and the customer 2 is entered in "reservation m" . _2 Customer ID of 201217986. Then, if the user of the user's client -20 is overwritten and downloaded, the user is uploaded to the server 11 1〇 (the step is requested, the shared file is closed from the guest, etc.) The end of the editing of the corpse server is completed in step S350), and the feeding server 10 is executed using the editing end routine S360 described with reference to FIG. Here, since p, 士 λ; has been reserved by the customer 20-2, and then can edit the shared file, share the file of the lucky flag, and the value of the flag "F2" of the record of the giant watch is "so in In step S25 of FIG. 7, the value of "reservation person: recorded "1D" is entered in the album ID", and the value of "reservation person ID" is updated to NULL, and "short move μ 丄 flag private F2" After the value is updated to "〇", the user is allowed to download and share (4) in the step of FIG. 7 and the message acknowledging the sharing: the editing of the case is notified. As a result, the user who operates the customer 20-2 can immediately recognize the editor immediately after the editing of the client (9)-1, and can immediately process the editing of the sharing of the Tan. . If the user of the operation client 20-2 performs the operation of overwriting the storage sharing standard, the shared file is uploaded to the server 1 (step Μ? (9). Furthermore, ^ the editing application closes the shared file, etc. When the editing job is transmitted from the client 20-2 to the server 10, the editing end request (step call H) is executed again using the editing end routine described in Fig. 7 (step (4) 〇). Here, in the processing of the above step S360, In the shared audit management table, the value of the flag "F2" is updated to ', and the reservation for the shared title is released. Therefore, the affirmative judgment is made in step (4) of FIG. 7, and will be shared in step S230 of FIG. 17 of the "flag ρι" of the record of the building management table 201217986 = 'Update the value of "Editor ID" to the new time of the ship" is updated to NULL, + more force S240 to customer 2 () customer 2 - U 20-2 f Editing the message. As a result, the user of the operation does not have to deliberately ask 'can grasp the shared file becomes editable. 1〇 and ask. Bu as above, share file upload (step S370) virtual share Tan J's editing end requirement (step _) for each other The reason for this is that, in the case of preventing the customer 20 system failure, the request of the 10th edition of the case can be edited in the middle of the editing operation. 幵 and the door order is uploaded to the server. The sharing system ends the method of forcibly releasing the locked state. Fig. 9 shows that the server 1〇 enforces the pain of this Izl I?--------------------------- Or every few hours). Here, the two tubes: the table is taken out - one record (step _). In the record, "flag# is extracted and stored in the shared file management table and can be taken out. The right is locked, and then the elapsed time Δτ from the "update time" of the record is read (step S4i〇) ). The corresponding time to share the 衅安々μ & update time _] input has the time to cover the beginning of the second or the home of the editing work * The last frost of the file is less than 卩 Τ Τ Τ Τ Τ Τ Τ Τ Share the broadcast 2: This, after the beginning of the time, the folder "when the shame is lost, the time from the editing work schedule is not in the way of the editing operation, the coverage is lost. 18 201217986 The last cover of the slot is stored. Next, the elapsed time Δτ after the above operation is compared with the threshold value τι and the larger threshold T2 (step S42〇). Here, the threshold τ2 is set to predict even if the sharing file is edited f The time has elapsed to become the state of the lock = state, for example, set to 1 〇 to 2 〇 hours. Further, the threshold is set to be shorter than the threshold Τ 2 by 2 hours, and is used for forcibly sharing the locked file. If the elapsed time ΔΤ is less than the threshold value T1 (steps S42〇, T1), since the sharing of the Tan case does not become locked for a long time, the forced end is not performed. S420. When St is equal to or greater than the inter-value η and the threshold T2 is not full (step WT < T2), the elapsed time U becomes the threshold value 2, and the editing process is forced to end the editing process of the shared file, so == The corresponding user who shared the file displays the reminder to share the file in the display = (! S43 °). In addition, as the automatic jump out of the display, the remaining time of the storage of the shared file and the execution of the forced end processing may be used. When it is determined that the time Δτ is equal to or greater than the threshold value T2 (step S420: T2 < Δ lock-like from the V: the shared slot file has been completed, the sharing of the audit file is also maintained, and the forced end processing is executed. Specifically... : Editing the end routine (step S440), in the case of splitting: the case is unlocked, the unlocking state becomes non-locking, and the :: t kinds of processing can suppress eight editing jobs. By executing the suppressing knife Being locked by a customer 20 for a long time 19 201217986 state that other customers can't edit the situation. At this time, only the step s2 (10) of Figure 7 of the editing request is accepted from the editing client, and the editing can be performed. After the bundled routine, the user who has set the sharing broadcast for a long time to the locked state will share the end of the file by automatically jumping out the notification (step S450). The leek is forced to execute all the records of the shared file management table. Γ=°: After processing (step _), the end of the forced... / "There is a customer in the dry file 2G is set to the lock state for a long time", then f (four) to cancel the lock state, because of the editing material. In addition, the user who performs the sharing of the file is transferred to the user of the sharing of the file (S). Therefore, even if the editing operation of the shared file continues, the unlocking state can be suppressed. It is mandatory to share the file management according to the above-mentioned description of the mode of the Taishou Brothers (10) 'Servo ^ 1G' in the shared file management table, the storage table * share the file as the locked state or the non-locked state "flag F1" The value, if the value of the special 7 is updated for all customers 2. Notification (steps of Figure 5, figure '": Γ °); the user of the customer 20 is enabled to display the status of the tube I: This can be easily mastered two: slaughter? The image before the standard can be managed efficiently (4) or not. Therefore, the shared file management system 10" of the present embodiment shares the customer 2 of the case. For server i. The editor end 10 confirms that it is at the same time _, for example, 1. Within seconds or 2 seconds, etc.) If there are more than 20, 2012, 17,986 times, there are editors starting from the same customer 20. Therefore, the user who edits the shared file erroneously ends step S200). If the user edits the file during the scheduled time period, the user can start the editing operation of the file, and the line is used to start the user 20 to be locked and cannot be edited. If the user of the shared file management client 20 of the present embodiment is turned on, the operation of the operation line of the 14100 shown in FIG. 6 is opened, thereby using the communication department ▲ monitoring screen to enter the file. The editors of the user get in touch with each other, and they want to share the locked I state of the file. Therefore, it is possible to negotiate four lines to cancel the assignment. Editing of the case and the shared file management system 10 of the present embodiment becomes locked when the file is edited by a client 2G = server = when the client 20 has an editing start request, then proceed: share the second case Appointment (step coffee in Figure 5), after the end of the editing operation, the second enjoys the file and informs the editor of the news (step S25 in Figure 7 can effectively edit the shared file. 260), again, this The shared file management system (10) of the embodiment is configured to execute the forced end routine described in FIG. 9, and if the share partner is fortunate: the client 20 is locked for a long time, the lock state is It is possible to edit the file in a highly efficient manner. Further, the shared file management system of the above-described embodiment_description_U, the state control unit 12, the state 'U β 13, the reservation 21 201217986 part 1 4, the state information output unit 丨$, the same as the feeding device 1〇, but As shown in Fig. 1J, the end portion 16 is provided with the same phase, and the knife has a different type of server as shown in Fig. 10. The feeder 1 squeaker W-2 has a state control unit i - Ken 3 The memory unit 11, the feeding device 14, the state information output unit 15, the second memory unit 13 and the reservation unit 7 are described in the step (10), and the client is in the step 2 or in the step 1 of FIG. -2 performs processing other than . The processing of the file of the sickle, the step of the servo = the shared file management system (10) of the embodiment, as shown in step SU0 of Fig. 5 or the step of Fig. 5, the state of the shared broadcast is in the locked state and the non-locked position. :: Description 'Although stated in the server 1. For all customers 2. Notice, :: pass = change from the feeding, such as mouth, mouth I am safe V. Ren does not notify. In this case, the client 20 is required to transmit the SQL 10 to the server 10 every predetermined time (for example, every few minutes). The change of the knife and drought file official table from the ship 1G to all customers 2. The notification only refers to the news that there is a change in the Z-form, and the customer 20 (20-^, ) is not allowed to transmit the sql text of the specific content to the server. Further, in the sharing right management system 1 of the above embodiment, the word service and the client 20-n are connected by Lan3, but the Internet connection may be made without going through the LAN 30. Furthermore, in the editing completion routine of FIG. 7 of the above-described embodiment, the step S 2 of accepting the editing start request 22 201217986 (the cancellation of the request, the end request) from the client who edited the shared file at a predetermined time is omitted. You can also handle it. Further, in the shared file management system of the above-described embodiment, only one client 20 can make a reservation, but a reservation from a plurality of clients can be accepted. At this time, for example, the client 2G can be edited in accordance with the order of accepting the reservation. . Further, in the shared file management system 100 of the above-described embodiment, the server 10 includes the reservation unit 14 or the forced end unit 16, but this is not the case. Further, in the above-described embodiments, the present invention has been described as a form of the shared file management system 100, but may be in the form of a control method of the shared slot management system (10) or a form of a program incorporated in the shared rights management system 100. Further, in the above-described embodiment, each of the functional units included in the server 10 or the client 20 can be provided with hardware resources such as a coffee maker, a memory device, and an interface with an external device, respectively, by the server 1 or the client 2 Implemented in conjunction with a program that controls hardware resources. The program for realizing the control method of the shared file management system 100 is provided in the state of recording on a floppy disk, a CD-ROM, a DVD-R〇M, or a memory card. It will be written from the recording medium to the reader, and the private input will be written to the memory device according to the procedure described in the embodiment. The present invention can be utilized in a manufacturing industry that shares a file management system. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a view showing a shared file management system according to an embodiment of the present invention. I. 23 201217986 The management system of the present invention Fig. 2 is a block diagram showing an example of the configuration of the sharing server according to the embodiment of the present invention. The guest file management system is stored in the file management system. Fig. 3 is a block diagram showing an example of the configuration of a user in the embodiment of the present invention. Fig. 4 is a view showing an example of the configuration of a shared file management table in the embodiment of the present invention. Fig. 5 is a flow chart showing the starting routine of the execution of the feeder when the request is made from the editing of the shared file of the client 2 in the sharing file of the embodiment of the present invention. Fig. 6 (a) and Fig. 6(b) are diagrams showing an example of a # 昼 之 昼 确认 确认 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 Fig. 7 is a flow chart showing the editing completion routine executed by the server when the client finishes the editing completion request of the shared file in the shared file management system according to the embodiment of the present invention. Fig. 8 is a program control 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 flow chart showing the forced end routine of the feeder execution in the shared file management system according to the embodiment of the present invention. Figure 10 is a diagram showing the variation of the shared file management system according to the embodiment of the present invention. [Main component symbol description] 10 (10 - 15 1 〇 _ 2) Server 24 201217986 11 12 13 14 15 16 17 20 (20-1 to 20 - N) 21 22 23 30 100 Memory unit status control unit status information memory unit reservation unit status information output unit forced end unit communication unit customer display unit operation unit communication unit
LAN 分享檔案管理系統 25LAN Share File Management System 25