CN104038520B - A kind of multi version distributive resource managing method and system - Google Patents

Abstract

Embodiments of the present invention provide a multi-version distributed resource management method and system to solve the problems of heavy workload, high cost, and large consumption of user disk resources in the current method. The method includes: judging whether the resource file of the original version is changed according to the resource file currently made; when changed, generating a new version number; deploying the resource file currently made to the resource server according to the new version number, and updating the resource file of the client The download path is modified; when the update server receives the version switching request from the client, the operation server corresponding to the new version number switched by the client sends the configuration file including the modified resource download path to the client; Resource download path to download resource files. In the embodiment of the present invention, by modifying the resource download path corresponding to the resource version, the client can automatically download the resource file of the new version under the path, thereby reducing the workload and cost.

Description

A multi-version distributed resource management method and system

technical field

The embodiments of the present invention relate to the technical field of network data processing, in particular to a multi-version distributed resource management method and system.

Background technique

Distributed resource management refers to the distributed management of client resources by splitting resources, integrating part of them into the client, and placing part in the resource server for users to download when using, so as to control the resources of the client. Disk usage.

The resources downloaded by the user from the Internet and stored in the system cache folder may be collectively referred to as IE resources. Pictures displayed on webpages browsed by users, content generated by flash players, and graphics and image resources in web games can all be counted as IE resources. In the IE resource management rules of Windows, any file stored in the system cache has the uniqueness of the file: when the file name of the file and the address path of the file do not change, the file will be directly accessed by the IE kernel. Called as a resource file, otherwise it will communicate with the server to download a new file.

Taking the graphics and image resources of the game as an example, some of them can be integrated into the client, and some of the resources can be placed in the resource server for users to download when using, so as to realize the distributed management of game resources.

During the operation of the game, different game versions will be run on different operation servers due to the needs of operation and publicity. The game client and the operation server need to be at the same version to ensure the consistency of game content, background logic, communication protocols, etc. during the game. During the game, users will choose the version of the game they want in the process of selecting and operating the server at will according to their own game preferences. The client will download the new version file corresponding to the operating server from the resource server when switching the operating server based on version consistency, so as to ensure the version consistency between the client and the server during runtime.

However, when the analysis rules of resources in the game are changed according to the needs of game development during the operation of the game, the overall resources of the game will be adjusted according to the new analysis rules. Based on the IE resource management rules, after the game version is updated, if the name and download path of the resource cannot be changed dynamically, the version of the cached resource read by the client will be inconsistent with the client resource resolution rules and operation rules stored on the operation server. Inconsistent server versions may cause problems such as display errors, client crashes, and logic exceptions.

For a conventional solution, all resources can be renamed during each version making process, so that new resource files can be downloaded during game play. However, the workload and game maintenance costs brought by the above method will increase suddenly; at the same time, because the new resource file is renamed, the original resource file and the new resource file will be saved in the client at the same time, so that a large number of Consumes the user's disk resources.

Contents of the invention

The technical problem to be solved by the embodiments of the present invention is to provide a multi-version distributed resource management method and system to solve the problems of heavy workload, high cost and large consumption of user disk resources in the current method.

In order to solve the above problems, the present invention discloses a multi-version distributed resource management method, which is characterized in that it includes:

During the production process of the resource version, judge whether the resource file of the original version is changed according to the resource file currently produced;

When the resource file of the original version is changed, a new version number is generated;

Deploying the currently produced resource file to the resource server according to the new version number;

Modify the resource download path of the client according to the new version number;

When the update server receives the version switching request from the client, the operation server corresponding to the new version number switched by the client sends a configuration file to the client, and the configuration file includes the configuration file modified according to the new version number. The modified resource download path; the client downloads the resource file from the resource server according to the modified resource download path.

Optionally, the resource download path includes a fixed download path and a variable download path, wherein the fixed download path is a download path of the resource server, and the variable download path is a version number.

Optionally, the modifying the resource download path of the client according to the new version number includes:

Modify the variable download path in the resource download path to the new version number.

Optionally, the deploying the currently produced resource file to the resource server according to the new version number includes:

compressing the currently produced resource file into a resource file compression package, the resource file compression package takes the new version number as the file name;

Decompressing the resource file compression package to the fixed download path of the resource server.

Optionally, the judging whether the original version of the resource file is changed according to the currently produced resource file includes:

Compare the currently produced resource file with the original version of the resource file;

When the resource file currently produced is the same as the resource file of the original version, or the resource file currently produced is an incremental change, it is determined that the resource file of the original version has not been changed;

When the currently produced resource file is a resource resolution rule change, it is determined that the original version of the resource file is changed.

On the other hand, the present invention also discloses a multi-version distributed resource management system, which is characterized in that it includes:

The judging module is used for judging whether the resource file of the original version is changed according to the resource file currently made during the production process of the resource version;

A generation module is used to generate a new version number when the resource file of the original version is changed;

a deployment module, configured to deploy the currently produced resource file to the resource server according to the new version number;

A modification module, configured to modify the resource download path of the client according to the new version number;

A sending module, configured to send a configuration file to the client according to the operation server corresponding to the new version number switched by the client when the update server receives the version switching request from the client, and the configuration file includes The resource download path modified by the new version number; the client downloads the resource file from the resource server according to the modified resource download path.

Optionally, the resource download path includes a fixed download path and a variable download path, wherein the fixed download path is a download path of the resource server, and the variable download path is a version number.

Optionally, the modification module modifies the variable download path in the resource download path to the new version number.

Optionally, the deployment module includes:

The compression submodule is used to compress the currently produced resource file into a resource file compression package, and the resource file compression package uses the new version number as the file name;

The decompression submodule is used to decompress the resource file compression package to the fixed download path of the resource server.

Optionally, the judging module includes:

The comparison sub-module is used to compare the resource file currently produced with the resource file of the original version;

A determination submodule is used to determine that the resource file of the original version has not changed when the resource file currently produced is the same as the resource file of the original version, or the resource file currently produced is an incremental change; When the resource file is a resource parsing rule change, it is determined that the original version of the resource file is changed.

Compared with the background technology, the embodiments of the present invention include the following advantages:

In the embodiment of the present invention, during the production process of the resource version, it is possible to judge whether the resource file of the original version is changed according to the resource file currently produced; when the resource file of the original version is changed, a new version number is generated; and according to the new The version number of the currently produced resource file is deployed to the resource server, and the resource download path of the client is modified; when the update server receives the client’s version switching request, the operation The server sends the modified resource download path according to the new version number to the client, and the client can download the resource file from the resource server according to the modified resource download path.

In the embodiment of the present invention, all resources are not renamed, but by modifying the resource download path corresponding to the resource version, the client can automatically download the resource file of the new version under the path, thereby reducing the workload and cost; and after downloading, the original local resource files of the client can be directly replaced, thereby saving the user's disk resources.

Description of drawings

FIG. 1 is a schematic diagram of client switching game versions in the current technology;

Fig. 2 is a flowchart of the game version production process described in Embodiment 1 of the present invention;

FIG. 3 is a flow chart of a multi-version distributed resource management method described in Embodiment 1 of the present invention;

Fig. 4 is a structural block diagram of a multi-version distributed resource management system according to Embodiment 2 of the present invention.

detailed description

In order to make the above objects, features and advantages of the present invention more comprehensible, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

The embodiments in this article are mainly introduced by taking game resources as an example. However, it should be noted that the embodiments of the present invention are not limited to game resources. Other IE resources (such as web page image resources, etc.) can also use this The technical solutions proposed by the embodiments of the invention solve the problem.

Embodiment one:

During the operation of the game, different game versions will be run on different operation servers due to the needs of operation and publicity. The game client and the operation server need to be at the same version to ensure the consistency of game content, background logic, communication protocols, etc. during the game. During the game, users will choose the version of the game they want in the process of selecting and operating the server at will according to their own game preferences. The client will download the new version file corresponding to the operating server from the resource server when switching the operating server based on version consistency, so as to ensure the version consistency between the client and the server during runtime.

Version switching refers to using the same game client to automatically modify client files according to the server version when logging in to different operating servers, so that users can use the same client to log in to operating servers of different versions to play games.

As shown in FIG. 1 , it is a schematic diagram of client switching game versions in the current technology.

When the client C logs in to the operation server, the update server S1 can provide the client with a list of operation servers, and the client can select the operation server to log in to (for example, the client C can choose to log in to the operation server S21). When client C requests to switch the game version, that is, to switch the operation server (for example, client C requests to switch to the operation server S22), if the game version on the operation server S21 is 1.0, the game version on the operation server S22 is 2.0 , when the update server S1 detects the change of game resources, it can send the configuration file to the client C, and guide the client C to download the resources corresponding to version 2.0 from the resource server S3.

Based on the IE resource management rules, after the game version is updated, if the name and download path of the resource cannot be changed dynamically, the version of the cached resource read by the client will be inconsistent with the client resource resolution rules and operation rules stored on the operation server. Inconsistent server versions may cause problems such as display errors, client crashes, and logic exceptions.

For a conventional solution, all resources can be renamed during each version making process, so that new resource files can be downloaded during game play. However, the workload and game maintenance costs brought by the above method will increase suddenly; at the same time, because the new resource file is renamed, the original resource file and the new resource file will be saved in the client at the same time, so that a large number of Consumes the user's disk resources.

In order to solve the above problems, an embodiment of the present invention proposes a multi-version distributed resource management method, which can reduce workload and maintenance costs, and can save disk resources of users.

First, the version making process of the embodiment of the present invention will be explained. In the embodiment of the present invention, during the production process of the resource version, a special game version production tool can be used. As shown in Figure 2, it is a flow chart of the game version production process in Embodiment 1 of the present invention, and the production process may include:

Step 200, start making the game version.

Step 201, judging whether the resource is changed.

If it is determined that the resource has changed, it can enter the automatic logic of the version creation tool; if it is determined that the resource has not changed, no processing will be performed in the embodiment of the present invention.

The following steps 202 to 204 are the automatic logic of the version creation tool.

Step 202, determining resource changes.

Step 203, automatically generating a resource download path of the client.

Step 204, automatically generating deployable resource files.

In the embodiment of the present invention, in the production process of downloadable resources, all resource files can be automatically retrieved through the version creation tool, and changes in the files can be judged. When a file changes, a new version number can be automatically generated, and Do the following two-part operation:

(1) Automatically modify the resource download path of the client according to the new version number (that is, step 203 above);

(2) Compress all produced resource files into a new resource file compressed package according to the new version number (that is, step 204 above).

Later, when the operation and maintenance personnel deploy server resources, they only need to decompress the new resource file compression package to the download path of the resource server.

The specific process of the multi-version distributed resource management method described in the embodiment of the present invention will be discussed in detail in the description of FIG. 3 below.

Referring to FIG. 3 , it shows a flowchart of a multi-version distributed resource management method described in Embodiment 1 of the present invention. The method may include:

Step 300, in the process of making the resource version, judge whether the resource file of the original version is changed according to the resource file currently being made.

In the embodiment of the present invention, it can be judged whether the resource file of the original version has been changed through the comparison between the resource files. Specifically, this step 300 may include:

a1, compare the currently produced resource file with the resource file of the original version.

In the embodiment of the present invention, the comparison between the currently produced resource file and the resource file of the original version can be automatically performed by means of code. For the specific comparison process, those skilled in the art may perform relevant processing according to the actual situation, and the embodiments of the present invention will not be discussed in detail here.

a2. When the currently produced resource file is the same as the original version of the resource file, or the currently produced resource file is an incremental change, it is determined that the original version of the resource file has not been changed.

a3. When the currently produced resource file is a resource analysis rule change, determine that the original version of the resource file is changed.

After comparison, if the resource file currently produced is the same as the resource file of the original version, it means that the resource file of the original version has not changed; in addition, if compared with the resource file of the original version, the resource file currently produced only increases If some content is changed, then in the embodiment of the present invention, it is also considered that the resource file of the original version has not been changed. For the situation that the resource files of the above two original versions have not been changed, they may not be processed in the embodiment of the present invention.

If compared with the resource file of the original version, when the resource resolution rule of the currently produced resource file is changed, the embodiment of the present invention considers that the resource file of the original version is changed. At this point, resource management can be performed according to the method described in the embodiment of the present invention.

Step 301, when the resource file of the original version is changed, a new version number is generated.

In the embodiment of the present invention, when it is determined in step 300 that the original version of the resource file is changed, a new version number can be automatically generated, and the new version number indicates the version of the currently produced resource file.

Step 302, deploying the currently produced resource file to the resource server according to the new version number.

In the embodiment of the present invention, a fixed download path can be set for the resource server, for example, the fixed download path of the resource server can be set to 10.1.1.123/pets/, and after a new version number is generated, the new The resource file corresponding to the version number is deployed to the resource server.

Specifically, this step 302 may include:

b1, compressing the currently produced resource file into a resource file compression package, and the resource file compression package uses the new version number as the file name.

In the version making process, when the resource file of the original version is determined to be changed and a new version number is generated, the resource file currently being made can be compressed into a resource file compression package, and the new version number is used as the resource The filename of the compressed file.

b2. Decompress the resource file compression package to the fixed download path of the resource server.

After the version is made. When the operation and maintenance personnel deploy resources, the operation and maintenance personnel can decompress the resource file compression package to the fixed download path of the resource server (for example, decompress to the fixed download path 10.1.1.123/pets/), at this time , to complete the deployment of the currently produced resource files to the resource server, and subsequent clients can download these resource files from the resource server.

Step 303, modify the resource download path of the client according to the new version number.

In the embodiment of the present invention, the resource download path of the client may include a fixed download path and a variable download path, wherein the fixed download path may be the download path of the resource server, and the variable download path may be the version No. By using the version number of the operation server as a part of the resource download path, it can be ensured that the resource download path configuration of the client corresponds to the version number of the operation server. For example, the resource download path of the client may be 10.1.1.123/pets/100, wherein 10.1.1.123/pets/ is the fixed download path of the resource server, and 100 is the version number.

After the resource file of the original version is changed and a new version number is generated, the resource download path of the client can also be modified according to the new version number, so as to ensure that the client can download the correct resource version from the resource server.

In the embodiment of the present invention, since the resource download path of the client is a fixed download path plus a variable download path (that is, the version number), the operating server pointed to by the client can be adjusted by modifying the version number in the resource download path .

Therefore, in step 303, the resource download path of the client is modified according to the new version number. Specifically, the variable download path in the resource download path can be modified to the new version number, so the client is The resource version corresponding to the new version number may be downloaded from the resource server.

For example, if the new version number is 101, the resource download path of the client can be modified to 10.1.1.123/pets/101, and the client can download the resource file of version 101 under this path.

Step 304, when the update server receives the client's version switching request, the operation server corresponding to the new version number switched by the client sends a configuration file to the client, the configuration file includes Resource download path after version number modification.

When the user wants to switch the version, the user client can send a version switching request to the update server, and the update server can send the configuration file to the client according to the operation server switched by the client.

In the embodiment of the present invention, when the user wants to switch to the resource version corresponding to the new version number (that is, the user requests to switch to the operation server corresponding to the new version number), a version switching request may be sent to the update server. For example, the client may trigger the version switching request by selecting the operation server corresponding to the new version number from the operation server list provided by the update server.

When the update server receives the version switching request from the client, it may send a configuration file to the client according to the operation server corresponding to the new version number switched by the client, wherein the configuration file may include The resource download path after the version number is modified.

Step 305, the client downloads the resource file from the resource server according to the modified resource download path.

When the user enters the game, he can directly obtain the resource file of the operation server version corresponding to the user's login from the resource download path, and directly replace the original local resource file with the downloaded resource file to complete the resource update operation .

For example, if the new version number in the operation server switched by the user is 101, the configuration file sent by the update server to the client may include the resource download path 10.1.1.123/pets/101, and the client downloads the resource according to the resource in the configuration file. path to download the resource file with version number 101 from the resource server.

In the embodiment of the present invention, the resource download path of the client is set as a fixed download path plus a variable download path. In the process of making a new version, instead of renaming all resources, a new version number is automatically generated during the version making process, and the variable download path in the resource download path is modified according to the new version number. In this way, the client can automatically download new versions of resource files under the resource download path, avoiding the problems of heavy workload and high cost caused by renaming all resource files; and, since resource files are not renamed Named, so after downloading, the resource file corresponding to the downloaded new version number can be used to directly replace the original local resource file of the client, thereby saving the user's disk resources.

Embodiment two:

Referring to FIG. 4 , it shows a structural block diagram of a multi-version distributed resource management system according to Embodiment 2 of the present invention.

The system may include: a version creation tool 40 , an update server 41 , a resource server 42 , a client 43 , a first operation server 44 and a second operation server 45 , and may also include a deployment module 402 . Wherein, the version creation tool 40 may include a judgment module 400 and a generation module 401 , and the update server 41 may include a modification module 403 and a sending module 404 .

in,

The judging module 400 is used for judging whether the resource file of the original version has been changed according to the resource file currently made during the production process of the resource version;

The judging module 400 may include:

The comparison sub-module is used to compare the resource file currently produced with the resource file of the original version;

A determination submodule is used to determine that the resource file of the original version has not changed when the resource file currently produced is the same as the resource file of the original version, or the resource file currently produced is an incremental change; When the resource file is a resource parsing rule change, it is determined that the original version of the resource file is changed.

A generating module 401, configured to generate a new version number when the resource file of the original version is changed;

Deployment module 402, for deploying the resource file currently produced to the resource server 42 according to the new version number;

The deployment module 402 may include:

The compression submodule is used to compress the currently produced resource file into a resource file compression package, and the resource file compression package uses the new version number as the file name;

The decompression submodule is used to decompress the resource file compression package to the fixed download path of the resource server.

A modification module 403, configured to modify the resource download path of the client according to the new version number;

Wherein, the resource download path includes a fixed download path and a variable download path, the fixed download path is a download path of the resource server, and the variable download path is a version number.

The modification module 403 may specifically modify the variable download path in the resource download path to the new version number.

The sending module 404 is configured to send a configuration file to the client according to the operation server corresponding to the new version number switched by the client when the update server receives the version switching request from the client, and the configuration file includes Describe the resource download path after the new version number modification.

When the client 43 requests to switch from the first operation server 44 to the second operation server 45 (wherein, the version number in the second operation server 45 is the new version number), the client 43 can send the version to the update server 41. Switching request, the update server 41 can send the configuration file to the client 43 . After receiving the configuration file sent by the update server 41, the client 43 can download the resource file from the resource server 42 according to the modified resource download path.

In the embodiment of the present invention, during the production process of the resource version, it is possible to judge whether the resource file of the original version is changed according to the resource file currently produced; when the resource file of the original version is changed, a new version number is generated; and according to the new The version number of the currently produced resource file will be deployed to the resource server, and the resource download path of the client will be modified; when the update server receives the client’s version switching request, the operating The server sends the modified resource download path according to the new version number to the client, and the client can download the resource file from the resource server according to the modified resource download path.

In the embodiment of the present invention, all resources are not renamed, but by modifying the resource download path corresponding to the resource version, the client can automatically download the resource file of the new version under the path, thereby reducing the workload and cost; and after downloading, the original local resource files of the client can be directly replaced, thereby saving the user's disk resources.

As for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the related parts, please refer to the part of the description of the method embodiment.

Embodiments of the invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

For the aforementioned method embodiments, for the sake of simple description, they are expressed as a series of action combinations, but those skilled in the art should know that the present invention is not limited by the described action sequence, because according to the present invention, Certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification belong to preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

Finally, it should also be noted that in this text, relational terms such as first and second etc. are only used to distinguish one entity or operation from another, and do not necessarily require or imply that these entities or operations, any such actual relationship or order exists. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, commodity, or apparatus. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

The above is a detailed introduction of a multi-version distributed resource management method and system provided by the present invention. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The description of the above embodiments is only for helping Understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, the content of this specification is not It should be understood as a limitation of the present invention.

Claims (8)

1. A multi-version distributed resource management method, characterized in that, comprising: During the production process of the resource version, judging whether the resource file of the original version has been changed according to the resource file currently produced includes: comparing the resource file currently produced with the resource file of the original version; when the resource file currently produced It is the same as the resource file of the original version, or when the resource file currently produced is an incremental change, it is determined that the resource file of the original version has not changed; when the resource file currently produced is a resource analysis rule change, the original version is determined resource file changes; When the resource file of the original version is changed, a new version number is generated; Deploying the currently produced resource file to the resource server according to the new version number; Modify the resource download path of the client according to the new version number; When the update server receives the version switching request sent by the client when switching the operation server, the operation server corresponding to the new version number switched by the client sends a configuration file to the client, and the configuration file includes The resource download path modified according to the new version number; the client downloads the resource file from the resource server according to the modified resource download path. 2. The method according to claim 1, wherein the resource download path includes a fixed download path and a variable download path, wherein the fixed download path is the download path of the resource server, and the variable The download path is the version number. 3. The method according to claim 2, wherein said modifying the resource download path of the client according to the new version number comprises: Modify the variable download path in the resource download path to the new version number. 4. The method according to claim 2, wherein the deploying the currently produced resource file to the resource server according to the new version number comprises: compressing the currently produced resource file into a resource file compression package, the resource file compression package takes the new version number as the file name; Decompressing the resource file compression package to the fixed download path of the resource server. 5. A multi-version distributed resource management system, comprising: The judging module is used to judge whether the resource file of the original version has been changed according to the resource file currently made during the production process of the resource version. The judging module includes: a comparison sub-module for comparing the resource file currently made with the original version of the resource file; determine the sub-module, used to determine that the original version of the resource file does not have Change; when the currently produced resource file is a resource analysis rule change, determine that the original version of the resource file has changed; A generation module is used to generate a new version number when the resource file of the original version is changed; a deployment module, configured to deploy the currently produced resource file to the resource server according to the new version number; A modification module, configured to modify the resource download path of the client according to the new version number; The sending module is configured to send the configuration file to the client according to the operation server corresponding to the new version number switched by the client when the update server receives the version switching request sent by the client when switching the operation server, the The configuration file includes a resource download path modified according to the new version number; the client downloads the resource file from the resource server according to the modified resource download path. 6. The system according to claim 5, wherein the resource download path includes a fixed download path and a variable download path, wherein the fixed download path is the download path of the resource server, and the variable The download path is the version number. 7. The system according to claim 6, wherein the modification module modifies the variable download path in the resource download path to the new version number. 8. The system according to claim 6, wherein the deployment module comprises: The compression submodule is used to compress the currently produced resource file into a resource file compression package, and the resource file compression package uses the new version number as the file name; The decompression submodule is used to decompress the resource file compression package to the fixed download path of the resource server.