TWI402693B - An interface device and method for controlling documents edition - Google Patents

Description

File version management interface device and method

The invention relates to an interface device and method for controlling file version control.

Most people use version control systems or error tracking systems in system development. Such version control systems include the open source code development version of the Concurrent Versions System (CVS) and Microsoft's Visual SourceSafe (VSS). The CVS is mainly file, and the modified versions of each file are independently controlled.

In the team development or design, different personnel will modify the same file multiple times. The biggest function of version control is to ensure the independence of each modification, so that the new modification will completely cover the old modification and is irreparable. You can start another modification after the revision of one version is finished. If the modification is wrong, you can also recover the old modification and have the continuity of the modification.

For many current projects, especially open source projects, developers can often get their latest source code through various version control systems. Most of these projects are also controlled and protected by the relevant tools for the source code they develop.

However, the current version control system needs to be managed by the client software, and can only be run independently and cannot be integrated into other systems; even if there is a web page (Web) implementation, it can only be browsed, and there is no version control function.

In view of the above, the present invention provides an interface device for controlling file version control. The device is installed on a network server and is connected to a version control server and a webpage. The device includes a service layer, an archive control layer and an analog client layer.

The service layer is configured to respond to a request for a user to upload and download an archive received by the webpage, and convert the request into a command to transmit to the simulated client layer; the service layer is further configured to receive a short modification of the uploaded file filled in by the user. Information, the name of the file encoding the file, the short modification information of the file, and the information that the user name is recognized by the version control server, and then the encoded information is transmitted to the analog client layer.

The file control layer is used to establish a client directory on the network server, and the client directory is a temporary storage directory for temporarily storing files uploaded by the user.

The simulated client layer is connected to the version control server for simulating the operation performed by the client of the version control server. After receiving the command transmitted by the service layer, the module obtains the uploaded file from the client directory, and then the file is uploaded. Stored in the version control server; the analog client layer is further configured to receive the transmitted encoded information, and store the encoded information in the version control server as the modified version history information of the file.

The invention also provides a file version management interface method, which performs file version control through a file version management interface device installed on a network server, and the file version control interface device connects the webpage and the version control server.

The method includes the following steps: the file version interface device responds to a request for uploading a file submitted by a user through a webpage, receives a short modification information and a user name filled in by the user, and saves the uploaded file to a client of the network server. Directory; if the user uploads a new file, it is determined whether the file is being modified by other users. If the file is being modified by another user, the file is not allowed to be uploaded; if the file is not being modified by another user or if the user Uploading a new file, encoding: the short modification information and the user name is the information that the version control server can recognize, and converting the request for uploading the file into a command; obtaining the uploaded file from the client directory according to the above command, And storing the file in the version control server; storing the coded information in the version control server as the modified version history information of the file; and the user controls the version of the server through the version control server, including downloading the latest file Version, history version of downloaded file, view file A modified version history information.

The invention does not need to use the client-side installer software to manage the historical version of the file modification, but integrates on the network server to implement the file version control function, including the file newly added version control, the file modification, and the uploading to generate a new version and file. The download of the current version of the content and the download of the historical version of the file, the query of the historical information of the file modification, etc., can be applied to the workflow management of the network system development.

10‧‧‧Webpage

11‧‧‧Web server

110‧‧‧Service layer

111‧‧‧File Control Layer

112‧‧‧simulated client layer

113‧‧‧Client Directory

114‧‧‧Control record

12‧‧‧ version control server

13‧‧‧Interface device

1 is a block diagram of a preferred embodiment of a file version management interface device of the present invention.

2 is a flow chart of a preferred embodiment of a file version management interface method of the present invention.

3 is a flow chart of a preferred embodiment of file uploading of the file version management interface method of the present invention.

4 is a flow chart of a preferred embodiment of file downloading of the file version management interface method of the present invention.

FIG. 5 is a flow chart of returning information of a file history version of the file version control interface method of the present invention.

Referring to FIG. 1 , it is an architectural diagram of a preferred embodiment of a file version management interface device of the present invention. The interface device 13 is installed in the network server 11, and includes a service layer 110, an archive control layer 111 and an analog client layer 112. The webpage 10 and the version control server 12 are connected to the web server 11 through the interface device 13 to implement version control of the files uploaded by the user through the webpage 10.

The service layer 110 is configured to respond to a user request received by the webpage 10, and the user request includes requesting to upload an archive, requesting to download a file, requesting to view an archive history version information, and the like. The request to download the file further includes requesting to download a new version file, requesting to download a historical version file, and the like. The service layer 110 translates the requested request into a command delivery to the analog client layer 112.

The service layer 110 is further configured to receive short modification information of the uploaded file by the user. The user name, the short modification information, and the file name are encoded into information that the version control server 12 can recognize; and the encoded information is also sent to the analog client layer 112. Since different users may use different encoding systems, such as A user uses Traditional Chinese, B user uses Simplified Chinese, and C user uses Central European language, the different encoded information needs to be unified into one code and stored in the version control server 12. In the preferred embodiment, the user name, the short modification information, the file name, and the like are encoded into a Unicode code and stored in the version control server 12.

The file control layer 111 is configured to establish a client directory 113 on the network server 11, and the client directory 113 is a temporary storage directory for temporarily storing user uploaded files. For example, the file uploaded by the client of the webpage 10 is first stored in the client directory 113.

The file control layer 111 is further configured to create a control record 114 for each uploaded new file on the network server 11. The control record 114 records the file name and code used in the file uploading and is stored in the version control server. The corresponding relationship between the file names in the device 12 also records the current latest status of the file, and the current latest status includes: the user name currently modifying the file, the modified date and time, the version batch, and the flag bit being modified. The flag bit is being modified to indicate whether the file is currently being modified by the user.

The file control layer 111 is also used to set permissions on files uploaded or accessed by the client of the web page 10. The file permission set includes a certain period of time prohibiting the user from modifying a file and only browsing.

The simulated client layer 112 is used to simulate the client end of the version control server 12. After receiving the command transmitted by the service layer 110, the client client 112 obtains the uploaded file from the client directory 113, and stores the file in the version control server 12. . The simulated client layer 112 is also used to simulate other operations performed by the client of the version control server 12, such as downloading files. The analog client layer 112 is directly coupled to the version management server 12.

Referring to FIG. 2, it is a flow chart of a preferred embodiment of the file version management interface method of the present invention. First, in step S200, the user submits a request for uploading an archive through the webpage 10, and selects a file to be uploaded and fills in a short modification information, the short modification information includes a user name for uploading the file, a reason for modifying the file, and a brief description of the modified content. Wait.

Step S202: After receiving the request for uploading the file, the interface device in the network server 11 stores the file to be uploaded in the version control server 12 according to the request.

In step S204, the user can perform version control by using the version control server 12, such as downloading a new version file, downloading a history version file, viewing an archive modification version history information, and the like.

Referring to FIG. 3, it is a flowchart of a preferred embodiment of file uploading of the file version management interface method of the present invention. In step S300, the service layer 110 receives the request for uploading the file submitted by the webpage 10.

In step S302, the service layer 110 stores the uploaded file in the client directory 113 established by the file control layer 111 in the network server 11.

Step S304, the service layer 110 receives the login user name submitted by the user through the webpage 10 and the short modification information of the uploaded file.

Step S306, the service layer 110 encodes the received user name and the short modification information into a Unicode code.

In step S308, the service layer 110 determines, according to the request that the user clicks on the webpage 10, whether the file to be uploaded is a new file. In general, when a user uploads a file, he or she chooses to upload a new file or upload a modified file based on whether the file is a new file or not.

In step S310, if the file to be uploaded is not a new file, the service layer 110 reads the control record 114 of the file. The control record 114 is used to record the current state of the file. Each file has a control record 114 that is created and managed by the file control layer 111. The current latest status of the file includes the user name of the file that was last uploaded, the latest version batch of the file that was last uploaded, the date and time of modification, the flag bit being modified, and the like. The modifying flag bit can be used to indicate whether the file is being modified by a user.

Step S312, determining whether the uploaded file is being modified by another user according to the flag bit being modified in the control record 114. If the uploaded file is being modified by another user, the file cannot be uploaded and the upload process ends.

Step S314, if the uploaded file is not being modified by other users, the service layer 110 sends the encoded user name and short modification information to the simulated client layer 112, and converts the request for uploading the file received from the webpage 10 into The command is sent to the analog client layer 112. The simulated client layer 112 retrieves the uploaded file from the client directory 113 and stores the file in the version control server 12.

In step S316, the simulated client layer 112 notifies the file control layer 111 to update the control record 114 of the file, and replaces the original control record 114 with the user name, version batch, modification date and time, etc. of the file uploaded this time. In addition, the simulated client layer 112 also adds the updated control record 114 to the file modification version history information corresponding to the file in the version control server 12.

In step S308, if the uploaded file is a new file, in step S318, the service layer 110 sends the encoded user name and short modification information to the simulated client layer 112, and the request for uploading the file received from the web page 10 is received. The conversion to command is sent to the analog client layer 112. The simulated client layer 112 retrieves the uploaded new archive from the client directory 113 and stores the new archive in the version control server 12.

In step S320, the file control layer 111 creates a control record 114 for the new file, and records the uploading user name, version, and upload date and time of the new file. And the file modification version history information of the new file is created by the simulation client layer 112 in the version control server 12, and the newly created control record 114 is added.

Referring to FIG. 4, it is a flowchart of a preferred embodiment of file downloading of the file version management interface method of the present invention. Step S400, the user submits a request for downloading the file through the webpage 10, and selects a version of the downloaded file, the selected version package Includes the latest version and historical version.

In step S402, the service layer 110 determines whether the version selected by the user is the latest version or the historical version.

Step S404, if the user selects the historical version of the downloaded file, the control record 114 of the file is read to obtain the correspondence between the file name when the file is uploaded and the file name stored in the version control server 12 after encoding and The status of the latest version of the file.

Step S406, the service layer 110 transmits the correspondence relationship of the obtained file name, the latest version batch of the file, and the version batch that the user needs to download as a parameter to the simulation client layer 112, and simultaneously converts the download request into a command and sends the simulation to the simulation. Customer layer 112.

In step S408, the simulated client layer 112 downloads the historical version required by the user to the version control server 12 according to the above parameters, and stores the historical version in the client directory 113. The service layer 110 reads the file into the HttpResponse object in the Http protocol.

Step S410, the simulated client layer 112 deletes the file from the client directory 113 after the service layer 110 reads the file.

In step S412, the historical version of the file read by the user on his webpage 10 is saved.

In step S402, if the user needs to download the latest version of the file, then in step S414, the service layer 110 converts the download request into a command transmission. The simulation client layer 112 is given.

In step S416, the simulated client layer 112 downloads the latest version of the file from the version control server 12 to the client directory 113. The service layer 110 reads the file into the HttpResponse object in the Http protocol. Then, the process proceeds to step S412.

Referring to FIG. 5, it is a flow chart of returning archive history version information in the file version management interface method of the present invention.

In step S500, the service layer 110 receives a request from the webpage 10 that the user needs to browse the archive history version information.

In step S502, the service layer 110 reads the control record 114 of the file to obtain the correspondence between the file name when the file is uploaded and the name stored in the version control server 12 after encoding.

Step S504, the service layer 110 converts the request into a command to transmit to the simulated client layer 112, and transmits the corresponding relationship of the file name to the simulated client layer 112. The simulated client layer 112 controls the server according to the information from the version. Get the historical version information of the file in 12. The historical version information includes short information of each modification of the file, a user name corresponding to each modification, and a date and time of each modification.

In step S506, the simulated client layer 112 parses the user name in the historical version information as the actual user name, and parses the short information of each modification to be the information that the user can recognize and displays on the user end. Because the user name and the submitted short modification information are encoded into Unicode code when the file is uploaded, the historical version information needs to be re-encoded into a code that the user can recognize.

The present invention has been described above in terms of preferred embodiments, and is not intended to limit the invention. The scope of the present invention is defined by the scope of the appended claims, unless otherwise claimed.

10‧‧‧Webpage

11‧‧‧Web server

110‧‧‧Service layer

111‧‧‧File Control Layer

112‧‧‧simulated client layer

113‧‧‧Client Directory

114‧‧‧Control record

12‧‧‧ version control server

13‧‧‧Interface device

Claims (11)

A file version management interface device installed on a network server and connected to a version control server and a webpage, the device comprising a service layer, an archive control layer and an analog client layer, wherein: the service layer is used to respond to a webpage Receiving a request for uploading and downloading a file by the user, and converting the request into a command to transmit to the simulated client layer; the service layer is further configured to receive short modification information of the uploaded file filled in by the user, and encode the file name of the file, The short modification information of the file and the information that the user name is recognized by the version control server, and then the encoded information is transmitted to the simulated client layer; the file control layer is used to establish a client directory on the network server, The client directory is a temporary storage directory for temporarily storing files uploaded by the user; the simulated client layer is connected to the version control server for simulating the operation performed by the client of the version control server, and receiving the service layer transmission After the command comes in, go to the client directory to get the uploaded file, and then store the file in version control. Server reactor; the analog customer receiving layer further for encoding information transmitted from, the encoded version of the information stored in the control server as a modified version of the file history information. For example, in the file version management interface device described in claim 1, the file control layer is further configured to create a control record for the uploaded file and update it in time, and the control record is used to record the file name and the file name when the file is uploaded. After encoding In the correspondence between the name of the version control server and the current latest status of the uploaded file of the file, the current latest status includes: the user name currently modifying the file, the modified date and time, the version batch, and the flag bit being modified. For example, in the file version management interface device described in claim 2, the simulated client layer is further configured to add the current latest status of the file in the control record to the modified version history information of the file. For example, in the file version management interface device described in claim 1, the file control layer is further configured to set an access permission for the file uploaded or accessed by the web page user. For example, in the file version control interface device described in the first item of the patent scope, the modified version history information of the file includes the file name after the file is encoded, the user name of each version modification, the short modification description filled in by the user, and the modification date and time. Modified version. A file version control interface method for performing file version control by a file version control interface device installed on a network server, the file version control interface device connecting a webpage and a version control server, the method comprising the steps of: the file version The management interface device responds to the request for uploading the file submitted by the user through the webpage, receives the short modification information and the user name filled in by the user for the uploaded file; saves the uploaded file to the client directory of the network server, and the client directory is temporarily The file uploaded by the user is stored; if the user uploads a new file, it is determined whether the file is being modified by other users, and if the file is being modified by other users, the file is not allowed to be uploaded. Pass the file; if the file is not being modified by another user or if the user uploads a new file, then: encode the short modification information and the user name is the information that the version control server can recognize, and convert the request for uploading the file. The command is obtained according to the above command, and the uploaded file is obtained from the client directory, and the file is stored in the version control server; the coded information is stored in the version control server as the modified version history information of the file; and the user The version control is controlled by the version control server, including downloading the latest version of the file, downloading the historical version of the file, and viewing the modified version history information of the file. For example, the file version control interface method described in claim 6 of the patent scope further includes the step of: if the user uploads a new file, creating a control record for the new file, the control record records the file uploaded by the file. The correspondence between the name and the name in the version control server and the current latest status of the file, the current latest status includes: the current user name of the file, the modification date and time, the version batch, and the flag bit being modified. . For example, in the file version management interface method described in claim 7, the method further includes the step of: adding the current latest status of the file in the control record to the modified version history information of the file. For example, the file version control interface method described in claim 7 of the patent scope, the party The method further includes the steps of: if the user uploads a new file, the control record of the file is updated, and the user name, version, and modification date of the modification are replaced with the original control record content. For example, the file version management interface method described in claim 7 is characterized in that the step of downloading the historical version of the file includes: receiving a request for a historical version of the downloaded file submitted by the user through the webpage; and obtaining the file according to the control record of the file Correspondence between the pre-encoding and the encoded file name and the latest version of the file, and convert the download request into a command; according to the correspondence of the file name, the latest version of the file, and the version that the user needs to download to the version control server Download the historical version required by the user, store the historical version in the client directory; read the file from the client directory into the HttpResponse object in the Http protocol; after the user reads the required file, The file is deleted from the client directory; and the user reads the historical version of the file on their web page and saves it. For example, the file version control interface method described in claim 7 is characterized in that the step of viewing the modified version history information of the file includes: receiving a request submitted by the user through the webpage to browse the historical version information of the file; and reading the control record of the file Obtaining the correspondence between the file and the encoded file name before encoding; The request is converted into a command, and the historical version information of the file is obtained from the version control server according to the correspondence between the command and the file name; the historical version information is analyzed to be information that the user can recognize and displayed on the web user end.