CN104038520A - Multi-version distributed resource management method and multi-version distributed resource management system - Google Patents
Multi-version distributed resource management method and multi-version distributed resource management system Download PDFInfo
- Publication number
- CN104038520A CN104038520A CN201310070313.XA CN201310070313A CN104038520A CN 104038520 A CN104038520 A CN 104038520A CN 201310070313 A CN201310070313 A CN 201310070313A CN 104038520 A CN104038520 A CN 104038520A
- Authority
- CN
- China
- Prior art keywords
- resource
- file
- resource file
- version
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 25
- 238000000034 method Methods 0.000 claims abstract description 41
- 230000006835 compression Effects 0.000 claims description 26
- 238000007906 compression Methods 0.000 claims description 26
- 230000008569 process Effects 0.000 claims description 24
- 238000004458 analytical method Methods 0.000 claims description 11
- 238000004519 manufacturing process Methods 0.000 claims description 10
- 230000008859 change Effects 0.000 claims description 9
- 230000004048 modification Effects 0.000 claims description 5
- 238000012986 modification Methods 0.000 claims description 5
- 230000006837 decompression Effects 0.000 claims description 3
- 238000012423 maintenance Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Landscapes
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention provides a multi-version distributed resource management method and a multi-version distributed resource management system to solve the problems of the existing method such as heavy workload, high cost, and high consumption of user's disk resources. The method comprises the following steps: whether a resource file of an original version needs to be changed is judged according to a currently produced resource file; a new version number is generated when the resource file of the original version is changed; the currently produced resource file is deployed to a resource server according to the new version number, and a resource downloading path of a client is modified; an updating server sends a configuration file including the modified resource downloading path to the client according to an operation server corresponding to the new version number switched by the client when receiving a version switching request of the client; and the client downloads the resource file according to the modified resource downloading path. According to the embodiment of the invention, the client is enabled to automatically download the new-version resource file according to the path by modifying the resource downloading path corresponding to the resource version, thereby reducing the workload and cost.
Description
Technical Field
The embodiment of the invention relates to the technical field of network data processing, in particular to a multi-version distributed resource management method and a multi-version distributed resource management system.
Background
The distributed resource management means that resources are split, part of the resources are integrated into a client, and part of the resources are placed in a resource server to provide downloading for a user when the user uses the resources, so that the distributed management of the resources of the client is realized, and the occupation amount of a disk of the client is controlled.
Resources stored in the system cache folder that are downloaded by a user from the network may be collectively referred to as IE resources. The IE resource can be calculated by the user browsing the picture displayed in the webpage, the content generated by the flash player and the graphic image resource in the webpage game. In the windows IE resource management rule, any file stored in the system cache has file uniqueness: when the file name of the file is not changed and the address path of the file is not changed, the file is directly called as a resource file by the IE kernel, otherwise, the file is communicated with the server to download a new file.
Taking the graphic image resource of the game as an example, a part of the resource can be integrated into the client, and a part of the resource is placed in the resource server to provide downloading for the user when in use, so as to realize distributed management of the game resource.
During the game operation, different game versions can be run on different operation servers due to the operation and promotion requirements. The game client and the operation server need to be in the same version, so as to ensure the consistency of game content, background logic, communication protocols and the like of users in the game process. The user can freely select the version of the game in the process of selecting the operation server according to the game preference of the user in the game process. And the client downloads a new version file corresponding to the operation server from the resource server when switching the operation servers based on the reason of version consistency so as to ensure the version consistency of the client and the server in operation.
However, when the analysis rule of the resources in the game is changed according to the development requirement of the game during the operation of the game, the resources of the whole game are adjusted according to the new analysis rule. Based on the IE resource management rule, after the game version is updated, if the name and the download path of the resource cannot be dynamically changed, the version of the cache resource read by the client may be inconsistent with the client resource analysis rule and the operating server version stored in the operating server, which may cause problems such as display error, client crash, and logic abnormality.
With conventional solutions, all resources may be renamed during each versioning so that new resource files may be downloaded at game time. But the workload and the game maintenance cost brought by the mode are increased sharply; meanwhile, because the new resource file is renamed, the original resource file and the new resource file are simultaneously stored in the client, so that a large amount of disk resources of a user are consumed.
Disclosure of 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, so as to solve the problems of large workload, high cost and large consumption of user disk resources in the current method.
In order to solve the above problem, the present invention discloses a multi-version distributed resource management method, which is characterized by comprising:
in the process of making the resource version, judging whether the resource file of the original version is changed or not according to the currently made resource file;
when the resource file of the original version is changed, a new version number is generated;
deploying the currently manufactured resource file to a resource server according to the new version number;
modifying the resource downloading path of the client according to the new version number;
when the update server receives a version switching request of a client, sending a configuration file to the client according to an operation server corresponding to the new version number switched by the client, wherein the configuration file comprises a resource downloading path modified according to the new version number; and the client downloads the resource file from the resource server according to the modified resource downloading path.
Optionally, the resource download path includes a fixed download path and a variable download path, where 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:
and modifying the variable download path in the resource download path into the new version number.
Optionally, the deploying the resource file currently manufactured to the resource server according to the new version number includes:
compressing the resource file which is manufactured currently into a resource file compression package, wherein the resource file compression package takes the new version number as a file name;
and decompressing the resource file compression packet to a fixed download path of the resource server.
Optionally, the determining whether the resource file of the original version is changed according to the currently manufactured resource file includes:
comparing the currently manufactured resource file with the resource file of the original version;
when the currently manufactured resource file is the same as the resource file of the original version or the currently manufactured resource file is changed in increment, determining that the resource file of the original version is not changed;
and when the currently manufactured resource file is changed according to the resource analysis rule, determining the change of the resource file of the original version.
On the other hand, the invention also discloses a multi-version distributed resource management system, which is characterized by comprising the following steps:
the judging module is used for judging whether the resource file of the original version is changed or not according to the currently manufactured resource file in the manufacturing process of the resource version;
the generating module is used for generating a new version number when the resource file of the original version is changed;
the deployment module is used for deploying the resource file which is manufactured currently to the resource server according to the new version number;
the modification module is used for modifying the resource downloading path of the client according to the new version number;
the sending module is used for sending a configuration file to the client according to the operation server corresponding to the new version number switched by the client when the version switching request of the client is received by the updating server, wherein the configuration file comprises a resource downloading path modified according to the new version number; and the client downloads the resource file from the resource server according to the modified resource downloading path.
Optionally, the resource download path includes a fixed download path and a variable download path, where 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 a variable download path in the resource download paths to the new version number.
Optionally, the deployment module comprises:
the compression submodule is used for compressing the resource file which is manufactured at present into a resource file compression package, and the resource file compression package takes the new version number as a file name;
and the decompression sub-module is used for decompressing the resource file compression packet to a fixed download path of the resource server.
Optionally, the determining module includes:
the comparison submodule is used for comparing the currently manufactured resource file with the resource file of the original version;
the determining submodule is used for determining that the resource file of the original version is not changed when the currently manufactured resource file is the same as the resource file of the original version or the currently manufactured resource file is changed in increment; and when the currently manufactured resource file is changed according to the resource analysis rule, determining the change of the resource file of the original version.
Compared with the background art, the embodiment of the invention has the following advantages:
the embodiment of the invention can judge whether the resource file of the original version is changed according to the currently manufactured resource file in the manufacturing process of the resource version; when the resource file of the original version is changed, a new version number is generated; deploying the currently manufactured resource file to a resource server according to the new version number, and modifying a resource downloading path of the client; when the update server receives a version switching request of the client, the operation server corresponding to the new version number switched by the client sends the resource downloading path modified 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 downloading path.
In the embodiment of the invention, all resources are not renamed, but the resource downloading path corresponding to the resource version is modified, so that the client can automatically download the resource file of the new version under the path, and the workload and the cost can be reduced; and the local original resource file of the client can be directly replaced after downloading, so that the disk resource of the user can be saved.
Drawings
FIG. 1 is a diagram illustrating a client switching game version according to the prior art;
FIG. 2 is a flow chart of a game version creation process according to one embodiment of the present invention;
fig. 3 is a flowchart of a multi-version distributed resource management method according to a first embodiment of the present invention;
fig. 4 is a block diagram of a multi-version distributed resource management system according to a second embodiment of the present invention.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.
Although the embodiments herein are mainly described by taking game resources as an example, it should be noted that the embodiments of the present invention are not limited to game resources, and other IE resources (e.g., web page picture resources, etc.) may also be solved by the technical solutions proposed in the embodiments of the present invention.
The first embodiment is as follows:
during the game operation, different game versions can be run on different operation servers due to the operation and promotion requirements. The game client and the operation server need to be in the same version, so as to ensure the consistency of game content, background logic, communication protocols and the like of users in the game process. The user can freely select the version of the game in the process of selecting the operation server according to the game preference of the user in the game process. And the client downloads a new version file corresponding to the operation server from the resource server when switching the operation servers based on the reason of version consistency so as to ensure the version consistency of the client and the server in operation.
The version switching means that the same game client is used, and when logging in different operation servers, the client file is automatically modified according to the server versions, so that a user can log in the operation servers with different versions by using the same client to play games.
Fig. 1 is a schematic diagram illustrating a client switching game version in the prior art.
When the client C logs in to the operation server, the update server S1 may provide the client with a list of operation servers, and the client may select an operation server that the client wants to log in (e.g., the client C may select to log in to the operation server S21). When the client C requests to switch the game version, that is, to switch the operation server (for example, the client C requests to switch to the operation server S22), if the game version on the operation server S21 is 1.0 and the game version on the operation server S22 is 2.0, the update server S1 may send a configuration file to the client C when detecting a game resource change, and direct the client C to download the resource corresponding to the version 2.0 in the resource server S3.
Based on the IE resource management rule, after the game version is updated, if the name and the download path of the resource cannot be dynamically changed, the version of the cache resource read by the client may be inconsistent with the client resource analysis rule and the operating server version stored in the operating server, which may cause problems such as display error, client crash, and logic abnormality.
With conventional solutions, all resources may be renamed during each versioning so that new resource files may be downloaded at game time. But the workload and the game maintenance cost brought by the mode are increased sharply; meanwhile, because the new resource file is renamed, the original resource file and the new resource file are simultaneously stored in the client, so that a large amount of disk resources of a user are consumed.
In order to solve the above problem, an embodiment of the present invention provides a multi-version distributed resource management method, which can reduce workload and maintenance cost, and can save disk resources of a user.
First, a version process of the embodiment of the present invention is described. In the embodiment of the invention, the process of making the resource version can be carried out by a special game version making tool. As shown in fig. 2, which is a flowchart of a process for making a game version according to an embodiment of the present invention, the process may include:
step 200, starting game version production.
Step 201, determine whether the resource is changed.
If the resource change is judged, the automatic logic of the version making tool can be entered; if the resource is judged not to be changed, the embodiment of the invention does not process.
The versioning tool automation logic is defined as steps 202-204 below.
At step 202, a resource change is determined.
Step 203, automatically generating a resource downloading path of the client.
Step 204, automatically generating a deployable resource file.
In the embodiment of the invention, in the process of manufacturing the downloadable resources, all resource files can be automatically retrieved through a version manufacturing tool, the change of the files is judged, when the files are changed, a new version number can be automatically generated, and the following two operations are carried out:
(1) automatically modifying the client resource download path according to the new version number (i.e. step 203);
(2) and compressing all the manufactured resource files into a new resource file compression package according to the new version numbers (namely step 204).
When the operation and maintenance personnel deploy the server resources subsequently, the new resource file compression package is only required to be decompressed to a download path of the resource server.
The specific process of the multi-version distributed resource management method according to the embodiment of the present invention will be discussed in detail in the following description of fig. 3.
Referring to fig. 3, a flowchart of a multi-version distributed resource management method according to a first embodiment of the present invention is shown, where the method may include:
step 300, in the process of making the resource version, judging whether the resource file of the original version is changed according to the currently made resource file.
In the embodiment of the invention, whether the resource file of the original version is changed or not can be judged through comparison among the resource files. Specifically, the step 300 may include:
a1, comparing the resource file produced currently with the original version of the resource file.
In the embodiment of the invention, the comparison between the currently manufactured resource file and the resource file of the original version can be automatically carried out in a code mode. For the specific comparison process, those skilled in the art can perform relevant processing according to actual situations, and the embodiment of the present invention is not discussed in detail here.
a2, when the resource file of the current production is the same as the resource file of the original version, or the resource file of the current production is changed in increment, determining that the resource file of the original version is not changed.
a3, when the resource file is changed according to the resource analysis rule, determining the original version of the resource file.
After the comparison, if the resource file manufactured currently is the same as the resource file of the original version, the resource file of the original version is not changed; in addition, if the resource file currently manufactured is only added with some contents compared with the resource file of the original version, the embodiment of the present invention also considers that the resource file of the original version is not changed. In the embodiment of the present invention, processing may not be performed on the two original versions of the resource file in response to the situation that the two original versions of the resource file are not changed.
If the resource file is changed according to the resource analysis rule compared with the resource file of the original version, the resource file of the original version is considered to be changed in the embodiment of the invention. At this time, the resource management may 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 the step 300 determines that the resource file of the original version is changed, a new version number may be automatically generated, and the new version number represents the version of the currently manufactured resource file.
Step 302, deploying the resource file currently manufactured to a resource server according to the new version number.
In the embodiment of the present invention, for the resource server, a fixed download path may be set, for example, the fixed download path of the resource server may be set to 10.1.1.123/pets/, and after a new version number is generated, the resource file corresponding to the new version number may be deployed to the resource server.
Specifically, the step 302 may include:
b1, compressing the resource file into resource file compression package, the resource file compression package takes the new version number as file name.
In the process of making the version, after the resource file of the original version is determined to be changed and a new version number is generated, the resource file which is made currently can be compressed into a resource file compression package, and the new version number is used as the file name of the resource file compression package.
b2, decompressing the resource file compression packet to the fixed download path of the resource server.
After the version is made. When the operation and maintenance personnel deploy the resources, the operation and maintenance personnel can decompress the resource file compression packet to a fixed download path of the resource server (for example, to a fixed download path 10.1.1.123/pets /), at this time, the currently manufactured resource files can be deployed to the resource server, and the subsequent client can download the resource files from the resource server.
Step 303, modifying the resource downloading path of the client according to the new version number.
In this embodiment of the present invention, the resource download path of the client may include a fixed download path and a variable download path, where the fixed download path may be a download path of the resource server, and the variable download path may be a version number. By using the version number of the operation server as a part of the resource download path, the configuration of the resource download path of the client can be ensured to correspond 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 a fixed download path of the resource server, and 100 is a version number.
After the original version of the resource file is changed and a new version number is generated, the resource downloading path of the client can be modified according to the new version number, so that the client can download a 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 (i.e., a version number), the operation server pointed by the client can be adjusted by modifying the version number in the resource download path.
Therefore, in this 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 may be modified to the new version number, so that the client can download the resource version corresponding to the new version number from the resource server.
For example, the new version number is 101, at this time, the resource download path of the client may be modified to 10.1.1.123/pets/101, and the client may download the resource file of version 101 under the path.
Step 304, when the update server receives a version switching request of a client, sending a configuration file to the client according to an operation server corresponding to the new version number switched by the client, wherein the configuration file comprises a resource downloading path modified according to the new version number.
When a user wants to switch versions, the user client may send a version switching request to the update server, and the update server may send a configuration file to the client according to an operation server to which the client switches.
In the embodiment of the present invention, when a user wants to switch to a resource version corresponding to the new version number (that is, the user requests to switch to an 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 an operation server corresponding to the new version number from an operation server list provided by the update server.
When receiving a version switching request of a client, the update server may send a configuration file to the client according to an operation server corresponding to the new version number switched by the client, where the configuration file may include a resource download path modified according to the new version number.
And 305, the client downloads the resource file from the resource server according to the modified resource downloading path.
When the user enters the game, the resource file corresponding to the version of the operation server logged in by the user can be directly obtained from the resource downloading path, and the downloaded resource file can be used for directly replacing the local original resource file to complete the resource updating 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 may download the resource file with the version number of 101 from the resource server according to the resource download path in the configuration file.
In the embodiment of the invention, the resource download path of the client is set to be a fixed download path plus a variable download path. In the process of making a new version, all resources are not renamed, but a new version number is automatically generated in the process of making the version, and a variable download path in the resource download path is modified according to the new version number. Therefore, the client can automatically download the resource file of the new version under the resource downloading path, and the problems of large workload and high cost caused by renaming all the resource files are avoided; in addition, because the resource files are not renamed, the resource files corresponding to the downloaded new version numbers can be directly used for replacing the local original resource files of the client after downloading, and therefore the disk resources of the user can be saved.
Example two:
referring to fig. 4, a block diagram of a multi-version distributed resource management system according to a second embodiment of the present invention is shown.
The system may include: versioning tool 40, update server 41, resource server 42, client 43, first operations server 44, and second operations server 45, may also include deployment module 402. The version tool 40 may include a determining module 400 and a generating module 401, and the update server 41 may include a modifying module 403 and a sending module 404.
Wherein,
a judging module 400, configured to judge whether a resource file of an original version is changed according to a currently manufactured resource file in a manufacturing process of a resource version;
the determining module 400 may include:
the comparison submodule is used for comparing the currently manufactured resource file with the resource file of the original version;
the determining submodule is used for determining that the resource file of the original version is not changed when the currently manufactured resource file is the same as the resource file of the original version or the currently manufactured resource file is changed in increment; and when the currently manufactured resource file is changed according to the resource analysis rule, determining the change of the resource file of the original version.
A generating module 401, configured to generate a new version number when a resource file of an original version is changed;
a deployment module 402, configured to deploy the currently manufactured resource file to the resource server 42 according to the new version number;
the deployment module 402 may include:
the compression submodule is used for compressing the resource file which is manufactured at present into a resource file compression package, and the resource file compression package takes the new version number as a file name;
and the decompression sub-module is used for decompressing the resource file compression packet to a fixed download path of the resource server.
A modification module 403, configured to modify a resource download path of the client according to the new version number;
the resource downloading path comprises a fixed downloading path and a variable downloading path, wherein the fixed downloading path is the downloading path of the resource server, and the variable downloading path is the version number.
The modifying module 403 may specifically modify the variable download path in the resource download path to the new version number.
A sending module 404, configured to send, when the update server receives a version switching request of a client, a configuration file to the client according to an operation server corresponding to the new version number switched by the client, where the configuration file includes a resource download path modified according to the new version number.
When the client 43 requests to switch from the first operation server 44 to the second operation server 45 (where the version number in the second operation server 45 is the new version number), the client 43 may send a version switching request to the update server 41, and the update server 41 may send the configuration file to the client 43. After receiving the configuration file sent by the update server 41, the client 43 may download the resource file from the resource server 42 according to the modified resource download path.
The embodiment of the invention can judge whether the resource file of the original version is changed according to the currently manufactured resource file in the manufacturing process of the resource version; when the resource file of the original version is changed, a new version number is generated; deploying the currently manufactured resource file to a resource server according to the new version number, and modifying a resource downloading path of the client; when the update server receives a version switching request of the client, the operation server corresponding to the new version number switched by the client sends the resource downloading path modified 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 downloading path.
In the embodiment of the invention, all resources are not renamed, but the resource downloading path corresponding to the resource version is modified, so that the client can automatically download the resource file of the new version under the path, and the workload and the cost can be reduced; and the local original resource file of the client can be directly replaced after downloading, so that the disk resource of the user can be saved.
For the system embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial 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 memory storage devices.
While, for purposes of simplicity of explanation, the foregoing method embodiments have been described as a series of acts or combination of acts, it will be appreciated by those skilled in the art that the present invention is not limited by the illustrated ordering of acts, as some steps may occur in other orders or concurrently with other steps in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The method and system for managing multi-version distributed resources provided by the present invention are introduced in detail, and a specific example is applied in the text to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A multi-version distributed resource management method is characterized by comprising the following steps:
in the process of making the resource version, judging whether the resource file of the original version is changed or not according to the currently made resource file;
when the resource file of the original version is changed, a new version number is generated;
deploying the currently manufactured resource file to a resource server according to the new version number;
modifying the resource downloading path of the client according to the new version number;
when the update server receives a version switching request of a client, sending a configuration file to the client according to an operation server corresponding to the new version number switched by the client, wherein the configuration file comprises a resource downloading path modified according to the new version number; and the client downloads the resource file from the resource server according to the modified resource downloading path.
2. The method of claim 1, wherein the resource download path comprises 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.
3. The method of claim 2, wherein modifying the resource download path of the client according to the new version number comprises:
and modifying the variable download path in the resource download path into the new version number.
4. The method of claim 2, wherein deploying the currently manufactured resource file to the resource server according to the new version number comprises:
compressing the resource file which is manufactured currently into a resource file compression package, wherein the resource file compression package takes the new version number as a file name;
and decompressing the resource file compression packet to a fixed download path of the resource server.
5. The method of claim 1, wherein the determining whether the original version of the resource file is changed according to the currently manufactured resource file comprises:
comparing the currently manufactured resource file with the resource file of the original version;
when the currently manufactured resource file is the same as the resource file of the original version or the currently manufactured resource file is changed in increment, determining that the resource file of the original version is not changed;
and when the currently manufactured resource file is changed according to the resource analysis rule, determining the change of the resource file of the original version.
6. A multi-version distributed resource management system, comprising:
the judging module is used for judging whether the resource file of the original version is changed or not according to the currently manufactured resource file in the manufacturing process of the resource version;
the generating module is used for generating a new version number when the resource file of the original version is changed;
the deployment module is used for deploying the resource file which is manufactured currently to the resource server according to the new version number;
the modification module is used for modifying the resource downloading path of the client according to the new version number;
the sending module is used for sending a configuration file to the client according to the operation server corresponding to the new version number switched by the client when the version switching request of the client is received by the updating server, wherein the configuration file comprises a resource downloading path modified according to the new version number; and the client downloads the resource file from the resource server according to the modified resource downloading path.
7. The system of claim 6, wherein the resource download path comprises 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 download path is a version number.
8. The system of claim 7, wherein the modification module modifies a variable download path of the resource download paths to the new version number.
9. The system of claim 7, wherein the deployment module comprises:
the compression submodule is used for compressing the resource file which is manufactured at present into a resource file compression package, and the resource file compression package takes the new version number as a file name;
and the decompression sub-module is used for decompressing the resource file compression packet to a fixed download path of the resource server.
10. The system of claim 6, wherein the determining module comprises:
the comparison submodule is used for comparing the currently manufactured resource file with the resource file of the original version;
the determining submodule is used for determining that the resource file of the original version is not changed when the currently manufactured resource file is the same as the resource file of the original version or the currently manufactured resource file is changed in increment; and when the currently manufactured resource file is changed according to the resource analysis rule, determining the change of the resource file of the original version.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310070313.XA CN104038520B (en) | 2013-03-05 | 2013-03-05 | A kind of multi version distributive resource managing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310070313.XA CN104038520B (en) | 2013-03-05 | 2013-03-05 | A kind of multi version distributive resource managing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104038520A true CN104038520A (en) | 2014-09-10 |
| CN104038520B CN104038520B (en) | 2017-11-10 |
Family
ID=51469109
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310070313.XA Active CN104038520B (en) | 2013-03-05 | 2013-03-05 | A kind of multi version distributive resource managing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104038520B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105049486A (en) * | 2015-06-16 | 2015-11-11 | 腾讯科技（北京）有限公司 | Version management and file pulling control methods for static files, version management and file pulling control devices, and version control system |
| CN105786574A (en) * | 2016-03-17 | 2016-07-20 | 武汉华星光电技术有限公司 | CIM system client version update method and update system based on VDI group |
| CN105915389A (en) * | 2016-06-02 | 2016-08-31 | 苏州乐麟无线信息科技有限公司 | Data configuration and loading method and device |
| CN107276844A (en) * | 2017-06-01 | 2017-10-20 | 郑州云海信息技术有限公司 | It is a kind of that the automatic setting method for logining server system is oriented based on linux operating systems |
| CN107370791A (en) * | 2017-06-23 | 2017-11-21 | 微梦创科网络科技（中国）有限公司 | The method and system of filename in automatic synchronization renewal content distributing network |
| WO2018120436A1 (en) * | 2016-12-26 | 2018-07-05 | 武汉斗鱼网络科技有限公司 | Version control method and system for flash application |
| CN109656610A (en) * | 2018-12-12 | 2019-04-19 | 北京像素软件科技股份有限公司 | The hot update method of online game distributed data and device |
| CN110244975A (en) * | 2018-03-08 | 2019-09-17 | 北京京东尚科信息技术有限公司 | A kind of generation method and device of static resource version number |
| CN113101670A (en) * | 2021-04-15 | 2021-07-13 | 网易（杭州）网络有限公司 | Version switching method and device |
| CN114327667A (en) * | 2020-10-09 | 2022-04-12 | 福建省天奕网络科技有限公司 | Dynamic resource loading method and system |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006110979A1 (en) * | 2005-04-18 | 2006-10-26 | Research In Motion Limited | Implementing data-compatibility-based version scheme |
| CN101090391A (en) * | 2006-06-13 | 2007-12-19 | 上海新纳广告传媒有限公司 | Software automatic updating method based on supertext transmission protocol mode |
| CN101141303A (en) * | 2007-09-24 | 2008-03-12 | 华为技术有限公司 | Client terminal updating method, server, client terminal of network management system |
| CN101183946A (en) * | 2006-12-26 | 2008-05-21 | 腾讯科技（深圳）有限公司 | Method and system of obtaining resource listing of download file |
| CN101795203A (en) * | 2009-02-03 | 2010-08-04 | 华为软件技术有限公司 | Method and device for downloading software upgrading data packet |
| CN101945135A (en) * | 2010-09-20 | 2011-01-12 | 中兴通讯股份有限公司 | Method and system for upgrading widget system |
| CN102053853A (en) * | 2010-12-30 | 2011-05-11 | 北京像素软件科技股份有限公司 | Version updating method of online game |
| CN102065110A (en) * | 2009-11-12 | 2011-05-18 | 钟惠波 | On-line updating method and system for client side software on basis of P2SP (Peer to Server and to Peer) |
| CN102263805A (en) * | 2010-05-25 | 2011-11-30 | 腾讯科技（北京）有限公司 | Dynamic resource downloading method and apparatus thereof |
| CN102347989A (en) * | 2011-10-25 | 2012-02-08 | 百度在线网络技术（北京）有限公司 | Data distribution method and system based on resource description symbols |
-
2013
- 2013-03-05 CN CN201310070313.XA patent/CN104038520B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006110979A1 (en) * | 2005-04-18 | 2006-10-26 | Research In Motion Limited | Implementing data-compatibility-based version scheme |
| CN101090391A (en) * | 2006-06-13 | 2007-12-19 | 上海新纳广告传媒有限公司 | Software automatic updating method based on supertext transmission protocol mode |
| CN101183946A (en) * | 2006-12-26 | 2008-05-21 | 腾讯科技（深圳）有限公司 | Method and system of obtaining resource listing of download file |
| CN101141303A (en) * | 2007-09-24 | 2008-03-12 | 华为技术有限公司 | Client terminal updating method, server, client terminal of network management system |
| CN101795203A (en) * | 2009-02-03 | 2010-08-04 | 华为软件技术有限公司 | Method and device for downloading software upgrading data packet |
| CN102065110A (en) * | 2009-11-12 | 2011-05-18 | 钟惠波 | On-line updating method and system for client side software on basis of P2SP (Peer to Server and to Peer) |
| CN102263805A (en) * | 2010-05-25 | 2011-11-30 | 腾讯科技（北京）有限公司 | Dynamic resource downloading method and apparatus thereof |
| CN101945135A (en) * | 2010-09-20 | 2011-01-12 | 中兴通讯股份有限公司 | Method and system for upgrading widget system |
| CN102053853A (en) * | 2010-12-30 | 2011-05-11 | 北京像素软件科技股份有限公司 | Version updating method of online game |
| CN102347989A (en) * | 2011-10-25 | 2012-02-08 | 百度在线网络技术（北京）有限公司 | Data distribution method and system based on resource description symbols |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105049486A (en) * | 2015-06-16 | 2015-11-11 | 腾讯科技（北京）有限公司 | Version management and file pulling control methods for static files, version management and file pulling control devices, and version control system |
| CN105049486B (en) * | 2015-06-16 | 2019-03-26 | 腾讯科技（北京）有限公司 | Method for edition management, the apparatus and system of static file |
| CN105786574B (en) * | 2016-03-17 | 2019-01-22 | 武汉华星光电技术有限公司 | CIM system client method for updating edition and more new system based on VDI group |
| CN105786574A (en) * | 2016-03-17 | 2016-07-20 | 武汉华星光电技术有限公司 | CIM system client version update method and update system based on VDI group |
| CN105915389A (en) * | 2016-06-02 | 2016-08-31 | 苏州乐麟无线信息科技有限公司 | Data configuration and loading method and device |
| WO2018120436A1 (en) * | 2016-12-26 | 2018-07-05 | 武汉斗鱼网络科技有限公司 | Version control method and system for flash application |
| CN107276844A (en) * | 2017-06-01 | 2017-10-20 | 郑州云海信息技术有限公司 | It is a kind of that the automatic setting method for logining server system is oriented based on linux operating systems |
| CN107370791A (en) * | 2017-06-23 | 2017-11-21 | 微梦创科网络科技（中国）有限公司 | The method and system of filename in automatic synchronization renewal content distributing network |
| CN110244975A (en) * | 2018-03-08 | 2019-09-17 | 北京京东尚科信息技术有限公司 | A kind of generation method and device of static resource version number |
| CN109656610A (en) * | 2018-12-12 | 2019-04-19 | 北京像素软件科技股份有限公司 | The hot update method of online game distributed data and device |
| CN109656610B (en) * | 2018-12-12 | 2022-03-15 | 北京像素软件科技股份有限公司 | Distributed data hot updating method and device for online game |
| CN114327667A (en) * | 2020-10-09 | 2022-04-12 | 福建省天奕网络科技有限公司 | Dynamic resource loading method and system |
| CN114327667B (en) * | 2020-10-09 | 2023-12-22 | 福建省天奕网络科技有限公司 | Dynamic resource loading method and system |
| CN113101670A (en) * | 2021-04-15 | 2021-07-13 | 网易（杭州）网络有限公司 | Version switching method and device |
| CN113101670B (en) * | 2021-04-15 | 2024-04-26 | 网易（杭州）网络有限公司 | Version switching method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104038520B (en) | 2017-11-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104038520B (en) | A kind of multi version distributive resource managing method and system | |
| US11032140B2 (en) | Using a template to update a stack of resources | |
| CN108845816B (en) | Application program updating method, system, computer device and storage medium | |
| EP2815311B1 (en) | Using an application cache to update resources of installed applications | |
| CN106708899B (en) | Automatic point burying method and device | |
| KR101376916B1 (en) | Techniques to perform gradual upgrades | |
| CN104067276B (en) | Client-side minimum is downloaded and the page navigation feature of simulation | |
| US20140007075A1 (en) | Methods for updating applications | |
| US20070143379A1 (en) | Metadata driven deployment of applications | |
| US10069940B2 (en) | Deployment meta-data based applicability targetting | |
| CN102833350A (en) | Processing method and processing device of WebApp updating | |
| JP2014512601A (en) | Tenant data recovery across tenant migration | |
| CN101944032A (en) | Microware updating method, client, server and system | |
| CN110286922A (en) | Using downloading updating method, device, computer equipment and storage medium | |
| CN104052769B (en) | It is a kind of to mobile terminal apply comprising resource updates methods, devices and systems | |
| US8296399B2 (en) | Connecting galleries to dynamic server-hosted content | |
| CN113064685A (en) | H5 page loading method and device | |
| CN113761412A (en) | Application page display method and device, electronic equipment, medium and application system | |
| CN112394932A (en) | Automatic browser webpage skin changing method and device | |
| AU2016101498A4 (en) | Data Interchange System | |
| CN111133415B (en) | Cross-platform custom functions | |
| CN112115056B (en) | Project deployment method and device, server and storage medium | |
| CN111045695A (en) | WebLogic middleware deployment device, method, equipment and medium | |
| EP2680135B1 (en) | Methods for updating applications | |
| CN105808628A (en) | Webpage transcoding method, apparatus and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |