WO2018000618A1

WO2018000618A1 - Object file appending and truncation method and server

Info

Publication number: WO2018000618A1
Application number: PCT/CN2016/099970
Authority: WO
Inventors: 吴兴义
Original assignee: 乐视控股（北京）有限公司; 乐视云计算有限公司
Priority date: 2016-06-30
Filing date: 2016-09-23
Publication date: 2018-01-04
Also published as: CN106202275A

Abstract

The present application discloses an object file appending and truncation method and a server, used to prevent repeated uploading of an object file obtained by means of appending or truncation at a user equipment, so as to reduce the bandwidth occupied by an upload request and increase utilization efficiency of public network bandwidth. The method comprises: receiving a reservation request issued from a user equipment, wherein the reservation request includes an identifier of an object file requiring an appending operation; determining an object file corresponding to the identifier on the basis of the identifier of the object file to requiring the appending operation, and returning a response indicating whether the determined object file can undergo the appending operation; if the response returned indicates that the object file can undergo appending, receiving an appending request that the user equipment issues for the object file, wherein the appending request includes appending content and an appending start position; and performing appending on the object file according to the appending content and the appending start position to obtain an appended object file.

Description

Object file addition, truncation method, and server

This application claims the priority of the Chinese Patent Application filed on June 30, 2016, the Chinese Patent Application No. 201610506560.3, the title of the invention is "addition, cut-off method and device of the object file", the entire contents of which are incorporated herein by reference. In the application.

Technical field

The present application relates to the field of communications technologies, and in particular, to an object file addition, a truncation method, and a server.

Background technique

Object storage is different from the storage structure of file storage. Traditional file storage stores files through the structure of the directory tree. However, object storage is not stored in a directory-hierarchical structure. Instead, each object is placed in the same storage pool to form a flat and identical hierarchy. Each element of each level has a unique identifier in the storage system through which the user device accesses the storage pool or object. Because the flat data organization structure discards nested folders, it avoids the burden of maintaining a large directory tree. In the era of big data and the Internet, there are millions of files and objects stored, and the number of visits per unit of time and concurrent access has reached an unprecedented magnitude. In this case, traditional file storage is used. That is, the form of the directory tree will bring great overhead and burden to the storage system, which will seriously restrict the processing efficiency and become the bottleneck of the system speed increase. Object storage is provided with a large amount of storage space, and the Hyper Text Transfer Protocol (HTTP) interface also simplifies the developer's development process. Therefore, object storage has received a lot of attention and has been rapidly developed.

However, the inventor has found that in the object storage, if an object file is to be appended or truncated, the appended object file or the truncated object file can only be re-uploaded to the server. When the user stores the log or processes the big data, it needs to perform an append or truncation operation to the object file every hour on average. If the object file is re-transmitted every time the file is appended or truncated by the prior art. Over time, the public network bandwidth will be seriously wasted, affecting the processing efficiency of the server.

In summary, if the user uses the prior art to store the log or process the big data, the average or hourly object file needs to be retransmitted every hour, resulting in low utilization of the public network bandwidth.

Summary of the invention

The present invention provides a method for adding and truncating an object file, and a server for solving the problem that the utilization rate of the public network bandwidth is low and the processing efficiency of the server storing the object file is low, and the utilization rate of the public network bandwidth is improved.

In a first aspect, an embodiment of the present application provides a method for adding an object file, including:

Receiving a reservation request sent by the user equipment, where the reservation request includes an identifier of an object file that needs to perform an additional operation;

Determining, according to the identifier of the object file that needs to be added, determining an object file corresponding to the identifier, and returning, to the user equipment, a response of whether the determined object file is appendable;

If the returned response is a response that can be added to the determined object file, receiving an additional request for the object file sent by the user equipment, wherein the additional request includes the additional content and the added starting position;

The object file is added based on the additional content and the added start position, and the added object file is obtained.

In a second aspect, the embodiment of the present application provides a method for truncating an object file, including:

Receiving a truncation request sent by the user equipment, where the truncation request includes: an identifier of an object file that needs to perform a truncation operation, and a truncation length;

Determining an object file that needs to perform a truncation operation according to the identifier of the object file that needs to perform the truncation operation;

The object file is truncated according to the truncation length to obtain a truncated object file.

In a third aspect, an embodiment of the present application provides a server, including: at least one processor; and a memory; wherein the memory stores an instruction executable by the at least one processor, The instructions are executed by the at least one processor to enable the at least one processor to perform an append method of any of the above object files of the present application.

In a fourth aspect, an embodiment of the present application provides a server, including: at least one processor; and a memory; wherein the memory stores an instruction executable by the at least one processor, the instruction being the at least one The processor executes to enable the at least one processor to perform the truncation method of any of the above object files of the present application.

The method for adding and cutting an object file and the server provided in the embodiment of the present application determine the position to add the additional content to the object file or determine the truncation by adding the initial start position in the request or the truncation length in the truncation request. The truncation area of the object file realizes the appending operation and the truncation operation on the object side on the server side, thereby avoiding the appending operation or truncation operation on the object file on the user equipment side, and then uploading the object file after the addition or truncation to the server again. The operation of the object file on the server side reduces the bandwidth occupied by the object file upload after the addition or truncation, and improves the utilization of the public network bandwidth.

DRAWINGS

The one or more embodiments are exemplified by the accompanying drawings in the accompanying drawings, and FIG. The figures in the drawings do not constitute a scale limitation unless otherwise stated.

FIG. 1 is a flowchart of a method for adding an object file according to an embodiment of the present application;

2 is a flowchart of a method for adding an object file according to an embodiment of the present application;

FIG. 3 is a flowchart of a method for adding an object file according to an embodiment of the present application;

4 is a flowchart of a method for truncating an object file according to an embodiment of the present application;

FIG. 5 is a flowchart of a method for truncating an object file according to an embodiment of the present application;

FIG. 6 is a flowchart of a method for truncating an object file according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of an apparatus for adding an object file according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a device for cutting an object file according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of a server according to an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a server according to an embodiment of the present application.

detailed description

The embodiments of the present application will be clearly and completely described in the following with reference to the drawings in the embodiments of the present application. Some embodiments, but not all of the embodiments.

The embodiment of the present invention provides an object file addition, a truncation method, and a server, which are used to solve the problem that the utilization rate of the public network bandwidth is low and the processing efficiency of the server storing the object file is low, and the utilization of the public network bandwidth is improved. rate.

Referring to FIG. 1 , an embodiment of the present application provides a method for adding an object file, including:

S101. Receive a reservation request sent by a user equipment, where the reservation request includes an identifier of an object file that needs to perform an additional operation;

S102: Determine an object file corresponding to the identifier according to the identifier of the object file that needs to be added, and return a response to whether the determined object file can be added to the user equipment;

S103. If the returned response is a response that can be added to the specified object file, receiving an additional request for the target file sent by the user equipment, where the additional request includes the additional content and the added starting position;

S104. Add the target file according to the additional content and the added starting position, and obtain the added target file.

Referring to FIG. 2, "Responding to whether the determined object file can be appended to the user equipment" in step S102 includes:

S201, determining whether the determined object file is set with a mutex lock, wherein the mutex lock is used to prohibit the user equipment other than the user equipment that sets the mutex lock from appending or truncating the object file for setting the mutex lock;

S202. If yes, return a response that the object file cannot be added to the user equipment; otherwise, return a response that the object file can be added to the user equipment.

The identifier of the object file to be added according to the need, and the preset data is queried. The library determines an object file that needs to be appended, and queries the database again according to the determined object file to determine whether the object file is provided with a mutex. The mapping includes a mapping relationship between the identifier of the object file and the object file, and a mapping relationship between the object file and the object file, and the mapping relationship is a one-to-one mapping.

In the embodiment of the present application, before the receiving user equipment sends the additional request, it is detected whether the object file that needs to be the additional operation is set with the mutual exclusion lock by the other user equipment, thereby avoiding that the object file is set by the other user equipment with the mutual exclusion lock. The resulting add operation fails, which improves the efficiency of the append operation.

The response that the object file can be appended includes an offset position of the object file, wherein the user equipment generates an additional start position and an added termination position according to the offset position of the object file.

Specifically, the additional starting position is an offset position of the object file.

In the embodiment of the present application, the user equipment receives a response that can be added by the object file sent by the server, and determines an additional start position and an added termination position according to the offset position of the object file in the response, and adds the determined An initial request, an added termination position, and additional content are generated to generate an additional request. By determining the additional range, that is, the appended starting position and the appended ending position, according to the offset position sent by the server, the length of the object file recorded in the server is prevented from being inconsistent with the length of the object file recorded in the user equipment, resulting in The addition fails, which improves the efficiency of the append operation.

Wherein the reservation request includes a length of the additional content;

Specifically, if the object file determined in step S202 is not provided with a mutex, the method further includes:

Setting a length of the additional content in the reservation request to be an agreed additional length;

Before the addition of the object file based on the additional content and the added starting position in step S104, the method further includes:

Determining whether the length of the additional content matches the agreed additional length;

Sending the length of the additional content to the user equipment if the length of the additional content does not match the agreed additional length A response to re-apply the offset position is sent; if they are consistent, step S104 is performed.

In the embodiment of the present application, it is determined whether or not the length of the added content matches the agreed additional length, and whether or not the addition is performed, and when the reservation request is received, the server takes up the additional content, thereby improving the server's additional operation. Speed, which increases operational efficiency.

If the object file determined in step S201 is not provided with a mutex, the method further includes:

Set a mutex lock on the object file.

In the embodiment of the present application, by setting a mutual exclusion lock on the determined object file, the problem that multiple user devices simultaneously add or truncate the same object file is prevented, so that only one user device operates the object file at the same time. , other users are prohibited from appending or truncating the object file.

After the object file is added in step S104, the method further includes:

Remove the mutex set on the object file.

In the embodiment of the present application, after the object file is added, the mutual exclusion lock set on the object file is removed, and at this time, other user equipments may perform an addition or a truncation operation on the object file.

For ease of understanding, the overall flow of object file addition will be further explained below with reference to FIG. 3.

S301. The user equipment sends a reservation request for adding an object file to the server, where the reservation request includes a length of the additional content.

S302. The server determines, according to the received reservation request, whether the object file is in an appendable state. If the object file is in an appendable state, performing the following steps; otherwise, returning a response that the object file cannot be added;

S303. The server sets a mutex lock on the object file, where the mutex lock is used to prohibit a user equipment other than the user equipment from appending or truncating an object file for setting a mutex lock.

S304. The server sets a length of the additional content in the reservation request to a predetermined additional length;

S305. The server returns a response including an offset position of the object file.

S306, the user equipment analyzes the response returned by the server; if the received response is a response that the object file cannot be added, then proceeds to step S301;

S307. If the received response is a response including the offset position of the object file, determine an additional start position and an end position according to the offset position of the object file, generate and send an additional request to the server. The additional request includes an added start location, a termination location, and the additional content;

S308. The server obtains additional content according to the received additional request, determines a length of the added content according to the added content, and determines whether the length of the determined additional content is equal to the agreed additional length;

S309. If yes, adding the additional content according to the added start position and the end position, generating an added target file, and returning a response including the length of the added target file, and opening the mutex; Otherwise, the server opens the mutex and returns a response to the failure to write the appended content;

S310. The user equipment receives the response sent by the server, and if the received response is a response including the length of the appended object file, the user equipment updates the length parameter of the object file; if the received response is If the response to the failure of the additional content is written, step S301 is re-executed.

The execution order of step S303, step S304, and step S305 is not limited.

Specifically, in step S307, determining an additional starting position according to the offset position of the object file, including:

The offset position of the object file and the length of the additional content are added to the header of the RANG of the HTTP request.

Specifically, after step S307, before step S308, the method further includes:

The server determines whether the user equipment that sends the additional request has the right to modify the object file, that is, whether the object of the mutex of the object file is the user equipment.

In order to ensure the integrity of the process of the present application, the portion before step S301 is supplemented. That is, the user equipment sends a request for uploading the object file to the server; the server writes the object file received in the request to the server, and records the length of the object file.

The server writes the object file in the request to the server, including: the server writes the object file in the request to the disk according to the number of copies rule.

It is assumed that, before the step S301, the length of the object file saved by the server is L0, and the length of the additional content is L1, the length of the additional content in the reservation request sent by the user equipment to the server is L1, the server In the returned response, the offset position is L0, the added start position is L0, the added termination position is L0+L1, and the interval of the additional position determined by the user equipment is [L0, L0+L1], and the server returns The length of the object file appended in the response is L0+L1.

Referring to FIG. 4, an embodiment of the present application provides a method for truncating an object file, including:

S401. Receive a truncation request sent by the user equipment, where the truncation request includes: an identifier of an object file that needs to perform a truncation operation, and a truncation length;

S402. Determine, according to the identifier of the object file that needs to perform the truncation operation, an object file that needs to perform a truncation operation;

S403. Cut the object file according to the truncation length to obtain a truncated object file.

Wherein, referring to FIG. 5, step S403 includes:

S501. Compare the truncation length with a length of the object file.

S502. Obtain a truncated object file according to the object file.

Specifically, step S502 includes the following three cases:

Case 1: If the truncation length is less than the length of the object file, the content of the object file is cleared from the position of the end of the object file until the length of the object file is equal to the truncation length. Obtain the truncated object file;

Case 2: if the truncation length is equal to the length of the object file, determining that the truncated object file is the object file before truncation;

Case 3: If the truncation length is greater than the length of the object file, the blank content is filled from the end of the object file until the length of the object file is equal to the truncation length, and the truncated Object file.

After the step S402, the method further includes:

If the object file is provided with a mutex lock, returning a non-trunable response of the object file, wherein the mutex lock is used to prohibit user equipment addition other than the user equipment that sets the mutex lock Or truncate the object file that sets the mutex.

For ease of understanding, the overall flow of the object file truncation will be further explained below with reference to FIG.

S601. The user equipment sends a reservation request including a truncation length to the server.

S602, the server determines whether the length of the truncation is equal to the length of the object file corresponding to the reservation request; if yes, step S605 is performed; otherwise, step S603 is performed;

S603. The server returns a response including an offset position of the object file to the user equipment.

S604, the user equipment determines the truncation length according to the returned offset position of the object file, and re-executes step S601;

S605. The user equipment sends a truncation request including a truncation length to the server.

S606, the server determines whether the received object file corresponding to the truncation request is in a truncated state; if yes, step S607 is performed; otherwise, step S609 is performed;

S607. Compare the truncation length with the length of the object file. If the truncation length is less than the length of the object file, clear the content of the object file from the position ending with the object file until the If the length of the object file is equal to the length of the truncation, the truncated object file is obtained; if the truncation length is equal to the length of the object file, it is determined that the truncated object file is the object file before truncation; If the truncation length is greater than the length of the object file, the blank content is filled from the end of the object file until the length of the object file is equal to the truncation length, and the truncated object file is obtained;

S608. The server returns a response including a length of the truncated object file.

S609. Return a response that the object file cannot be truncated.

Assuming that the length of the object file in the server is L0+L1, the truncation length in the reservation request is L2. Therefore, the first case in step S502, that is, if L2 is smaller than L0+L1, the content of the object file of the truncated section, that is, [L2, L0+L1] is cleared, and the truncated object file is obtained; If it is equal to L0+L1, it is determined that the truncated object file is the object file before truncation; in case three, if L2 is greater than L0+L1, the object file is in the truncation interval, that is, [L0+L1, L2] fills in the blank content and gets the truncated object file.

The blank content of the padding is a null character, that is, “0”.

Referring to FIG. 7, an embodiment of the present application provides an apparatus for adding an object file, including:

The first receiving module 701 is configured to receive a reservation request sent by the user equipment, where the reservation request includes an identifier of an object file that needs to perform an additional operation;

The response module 702 is configured to determine an object file corresponding to the identifier according to the identifier of the object file that needs to be added, and return a response to whether the determined object file can be added to the user equipment;

The second receiving module 703 is configured to receive an additional request for the target file sent by the user equipment, if the returned response is a response that can be added to the specified object file, wherein the additional request includes additional content and an additional request Starting position

The adding module 704 is configured to add the target file based on the additional content and the added starting position, and obtain the added target file.

Specifically, the user equipment is returned to the user equipment whether the determined object file is appendable. The response module 702 is specifically configured to:

Determining whether the determined object file is set with a mutex lock, wherein the mutex lock is used to prohibit the user equipment other than the user equipment that sets the mutex lock from appending or truncating the object file for setting the mutex lock;

If yes, return a response that the object file cannot be added to the user equipment; otherwise, return a response that the object file can be added to the user equipment.

Specifically, the response that the object file can be appended includes: an offset position of the object file, wherein the user equipment generates an additional starting position according to the offset position of the object file.

Specifically, the reservation request includes a length of the additional content;

If the determined object file is not provided with a mutex, the response module 702 is further configured to:

The appending module 704 is further configured to:

Determining whether the length corresponding to the added starting position is consistent with the agreed additional length;

If the length corresponding to the added start position does not match the agreed additional length, a response to re-apply the offset position is sent to the user equipment.

Specifically, if the determined object file is not set with a mutex lock, the response module 702 is further configured to:

Set a mutex lock on the object file.

Specifically, the appending module 704 is further configured to:

Remove the mutex set on the object file.

Referring to FIG. 8, an embodiment of the present application provides a device for cutting an object file, including:

The receiving module 801 is configured to receive a truncation request sent by the user equipment, where the truncation request includes: an identifier of an object file that needs to perform a truncation operation, and a truncation length;

The determining module 802 is configured to determine an object file that needs to perform a truncation operation according to the identifier of the object file that needs to perform the truncation operation;

The truncation module 803 is configured to truncate the object file according to the truncation length to obtain a truncated object file.

Specifically, the truncation module 803 is specifically configured to:

Comparing the truncation length with a length of the object file;

If the truncation length is less than the length of the object file, the content of the object file is cleared from the position at the end of the object file until the length of the object file is equal to the truncation length, and the truncation is obtained. Object file

If the truncation length is equal to the length of the object file, determining that the truncated object file is the object file before truncation;

If the truncation length is greater than the length of the object file, the blank content is filled from the end of the object file until the length of the object file is equal to the truncation length, and the truncated object file is obtained.

Specifically, the truncation module 803 is further configured to:

If the object file is provided with a mutex lock, returning an uninterruptible response of the object file, wherein the mutex is used to prohibit user equipment other than the user equipment that sets the mutex from appending or truncating the setting mutual The object file that is slammed.

Referring to FIG. 9 , an embodiment of the present application provides a server, including: at least one processor 901; and a memory 902. The processor 901 includes: a first receiving module 701, a response module 702, a second receiving module 703, and An additional module 704; wherein

The appending module 704 is further configured to:

Set a mutex lock on the object file.

Specifically, the appending module 704 is further configured to:

Remove the mutex set on the object file.

Referring to FIG. 10, an embodiment of the present application provides a server, including: at least one processor 1001; and a memory 1002. The processor 1001 includes: a receiving module 801, a determining module 802, and a truncating module 803.

Specifically, the truncation module 803 is specifically configured to:

Comparing the truncation length with a length of the object file;

Specifically, the truncation module 803 is further configured to:

If the object file is set with a mutex lock, returning an uninterruptible response of the object file, The mutex is used to prohibit the user equipment other than the user equipment that sets the mutex from appending or truncating the object file for setting the mutex.

The server provided by the embodiment of the present application may be an object storage cluster.

The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.

Through the description of the above embodiments, those skilled in the art can clearly understand that the various embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware. Based on such understanding, the above-described technical solutions may be embodied in the form of software products in essence or in the form of software products, which may be stored in a computer readable storage medium such as ROM/RAM, magnetic Discs, optical discs, etc., include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments or portions of the embodiments.

Finally, it should be noted that the above embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still The technical solutions described in the foregoing embodiments are modified, or the equivalents of the technical features are replaced by the equivalents. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A method for appending an object file to a server, comprising:

Receiving a reservation request sent by the user equipment, where the reservation request includes an identifier of an object file that needs to perform an additional operation;

Determining, according to the identifier of the object file that needs to be added, determining an object file corresponding to the identifier, and returning, to the user equipment, a response of whether the determined object file is appendable;

If the returned response is a response that can be added to the determined object file, receiving an additional request for the object file sent by the user equipment, wherein the additional request includes the additional content and the added starting position;

The object file is added based on the additional content and the added start position, and the added object file is obtained.
The method according to claim 1, wherein the returning to the user equipment whether the determined object file is appendable comprises:

Determining whether the determined object file is set with a mutex lock, wherein the mutex lock is used to prohibit the user equipment other than the user equipment that sets the mutex lock from appending or truncating the object file for setting the mutex lock;

If yes, returning, to the user equipment, a response that the object file cannot be added;

Otherwise, a response that the object file can be appended is returned to the user device.
The method according to claim 2, wherein the object file appendable response comprises: an offset position of the object file, wherein the user equipment generates an append according to an offset position of the object file starting point.
The method according to claim 2, wherein the reservation request comprises: a length of the additional content;

If the determined object file is not provided with a mutex, the method further includes:

Setting a length of the additional content in the reservation request to be an agreed additional length;

Chasing the object file based on the additional content and the added starting position Before adding, the method also includes:

Determining whether the length of the additional content matches the agreed additional length;

If the length of the additional content does not match the agreed additional length, a response to re-apply the offset position is transmitted to the user equipment.
The method according to claim 2, wherein if the determined object file is not set with a mutex, the method further comprises:

Set a mutex lock on the object file.
The method according to claim 5, wherein after the object file is appended, the method further comprises:

Remove the mutex set on the object file.
A method for truncating an object file, applied to a server, comprising:

Receiving a truncation request sent by the user equipment, where the truncation request includes: an identifier of an object file that needs to perform a truncation operation, and a truncation length;

Determining an object file that needs to perform a truncation operation according to the identifier of the object file that needs to perform the truncation operation;

The object file is truncated according to the truncation length to obtain a truncated object file.
The method according to claim 7, wherein the truncating object file is truncated according to the truncated length, and the truncated object file is obtained, including:

Comparing the truncation length with a length of the object file;

If the truncation length is less than the length of the object file, the content of the object file is cleared from the position at the end of the object file until the length of the object file is equal to the truncation length, and the truncation is obtained. Object file

If the truncation length is equal to the length of the object file, determining that the truncated object file is the object file before truncation;

If the truncation length is greater than the length of the object file, the blank content is filled from the end of the object file until the length of the object file is equal to the truncation length, and the truncated object file is obtained.
The method according to claim 7, wherein after determining the object file that needs to be subjected to the truncation operation, the method further comprises:

If the object file is provided with a mutex lock, returning an uninterruptible response of the object file, wherein the mutex is used to prohibit user equipment other than the user equipment that sets the mutex from appending or truncating the setting mutual The object file that is slammed.
A server, comprising: at least one processor; and a memory; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to Enabling the at least one processor to:

Receiving a reservation request sent by the user equipment, where the reservation request includes an identifier of an object file that needs to perform an additional operation;

Determining, according to the identifier of the object file that needs to be added, determining an object file corresponding to the identifier, and returning, to the user equipment, a response of whether the determined object file is appendable;

If the returned response is a response that can be added to the determined object file, receiving an additional request for the object file sent by the user equipment, wherein the additional request includes the additional content and the added starting position;

The object file is added based on the additional content and the added start position, and the added object file is obtained.
The server according to claim 10, wherein the returning to the user equipment whether the determined object file is appendable comprises:

Determining whether the determined object file is set with a mutex lock, wherein the mutex lock is used to prohibit the user equipment other than the user equipment that sets the mutex lock from appending or truncating the object file for setting the mutex lock;

If yes, return a response that the object file cannot be added to the user equipment; otherwise, return a response that the object file can be added to the user equipment.
The server according to claim 11, wherein the response that the object file can be appended includes: an offset position of the object file, wherein the user equipment generates an additional according to an offset position of the object file. starting point.
The server according to claim 11, wherein the reservation request comprises: a length of the additional content;

If the determined object file is not provided with a mutex, the computer executable instructions are also used to:

Setting a length of the additional content in the reservation request to be an agreed additional length;

The additional module is also used to:

Determining whether the length of the additional content matches the agreed additional length;

If the length of the additional content does not match the agreed additional length, a response to re-apply the offset position is transmitted to the user equipment.
The server according to claim 11, wherein if the determined object file is not provided with a mutex, the computer executable instructions are further used to:

Set a mutex lock on the object file.
The server according to claim 14, wherein said computer executable instructions are further for:

Remove the mutex set on the object file.
A server, comprising: at least one processor; and a memory; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to Enabling the at least one processor to:

Receiving a truncation request sent by the user equipment, where the truncation request includes: an identifier of an object file that needs to perform a truncation operation, and a truncation length;

Determining an object file that needs to perform a truncation operation according to the identifier of the object file that needs to perform the truncation operation;

The object file is truncated according to the truncation length to obtain a truncated object file.
The server according to claim 16, wherein the object file is truncated according to the truncated length, and the truncated object file is obtained, including:

Comparing the truncation length with a length of the object file;

If the truncation length is less than the length of the object file, the content of the object file is cleared from the position at the end of the object file until the length of the object file is longer than the truncation Obtain the object file after truncation until the degree is equal;

If the truncation length is equal to the length of the object file, determining that the truncated object file is the object file before truncation;

If the truncation length is greater than the length of the object file, the blank content is filled from the end of the object file until the length of the object file is equal to the truncation length, and the truncated object file is obtained.
The server according to claim 16, wherein the object file is truncated according to the truncated length, and the truncated object file is obtained, including:

If the object file is provided with a mutex lock, returning an uninterruptible response of the object file, wherein the mutex is used to prohibit user equipment other than the user equipment that sets the mutex from appending or truncating the setting mutual The object file that is slammed.