CN105049486A - Version management and file pulling control methods for static files, version management and file pulling control devices, and version control system - Google Patents
Version management and file pulling control methods for static files, version management and file pulling control devices, and version control system Download PDFInfo
- Publication number
- CN105049486A CN105049486A CN201510333621.6A CN201510333621A CN105049486A CN 105049486 A CN105049486 A CN 105049486A CN 201510333621 A CN201510333621 A CN 201510333621A CN 105049486 A CN105049486 A CN 105049486A
- Authority
- CN
- China
- Prior art keywords
- file
- static
- version number
- module
- configuration file
- 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
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
Abstract
The invention discloses version management and file pulling control methods for static files, version management and file pulling control devices, and a version control system. The version management method for the static files includes: a version number is marked at each static file in the at least one static file, the static files marked with the version numbers are regarded as to-be-released files; a version configuration file corresponding to at least one to-be-released file is generated; the version configuration file comprises a file name and the information of the version number of the at least one to-be-released file; and the at least one to-be-released file is released in a content distribution network server, and the version configuration file is released in an operation server in a gated launch manner. According to the technical scheme, clear management and control of static file versions can be realized, the chaos of the static file versions is avoided, and rollback, gated launch, and incremental release of the static files can be supported.
Description
Technical field
The application relates to internet arena, and particularly a kind of method for edition management of static file, file pull control method, edition management device, file pull control device and version control system.
Background technology
Browser is at acquisition associated static file, as the js file of javascript scripting language, cascading style list (CascadingStyleSheet, css) file and picture file etc., during generating web page, in order to improve the performance of Web, usual meeting is first from content distributing network (ContentDeliveryNetwork, when CDN) downloading these static files, these static files are carried out buffer memory, and a cache-time is set for it, as long as this cache-time did not lose efficacy, during this webpage of regeneration next time, just without the need to again pulling these static files from CDN, and only need obtain from local cache district, improve networking speed, also save networking flow.
But current problem is: when there being the content of static file to there is renewal, as changed partial code or increase in certain js file a.js, deleting partial code etc., now, if this a.js file of browser rs cache and its cache-time did not lose efficacy, then browser still can call this a.js file of local cache, and the a.js file that again can not pull from CDN after renewal, this certain procedures will cause the confusion of webpage static file version.
In order to address this problem, be currently suggested two kinds of solutions.The first adds a query string below in URL(uniform resource locator) (UniformResourceLocator, URL) to distinguish different versions, such as: http:www.qq.com/a.js? version=123.The second directly changes filename to realize the differentiation of version, such as: http:www.qq.com/a123.js.Implementation in this two schemes is all realized by manual change, easy operate miss; In addition, two kinds of mode not supporting document rollbacks, namely when the redaction issued exists mistake, cannot rollback to version before; In addition, this two schemes does not support gray scale to issue and increment issue yet.
For this reason, those skilled in the art are also finding other solution.
Summary of the invention
In view of this, the method for edition management and the file that provide a kind of static file in the embodiment of the present invention on the one hand pull control method, the edition management device, the file that provide a kind of static file on the other hand pull control device and version control system, in order to realization to the clear management of static file version and control, avoid the confusion of static file version, and can support that the rollback of static file, gray scale issue and increment are issued.
The method for edition management of static file provided by the present invention, comprising:
For each static file at least one static file marks a version number, and will the described static file of version number be marked with as file to be released;
Generate the edition configuration file of at least one file to be released corresponding; Described edition configuration file comprises the respective filename of at least one file to be released described and version number information;
By at least one file distribution to be released described in content delivery network service device, and described edition configuration file is published in Operation Server with gray scale published method, so that when an Operation Server receives the browse request from a browser, corresponding edition configuration file is read according to described browse request, the filename comprise described edition configuration file and version number information are supplied to described browser, corresponding static file can be pulled according to described filename and version number information from described content delivery network service device to make described browser, and perform the static file pulled.
The file of static file provided by the present invention pulls control method, comprising:
Receive the browse request from a browser;
Corresponding edition configuration file is read according to described browse request, the filename comprise described edition configuration file and version number information are supplied to described browser, so that described browser pulls the static file of corresponding each filename and version number information according to described filename and version number information from described content delivery network service device, and perform the static file pulled.
The edition management device of static file provided by the present invention, for a version management server, described device comprises: version number's mark module, edition configuration file generation module, static resource release module and edition configuration file release module; Wherein,
Described version number mark module is used for for each static file at least one static file marks a version number, and will be marked with the described static file of version number as file to be released;
Described edition configuration file generation module is for generating the edition configuration file of at least one file to be released corresponding; Described edition configuration file comprises the respective filename of at least one file to be released described and version number information;
Described static resource release module is used at least one file distribution to be released described in content delivery network service device;
Described edition configuration file release module is used for described edition configuration file to be published in Operation Server with gray scale published method, so that when an Operation Server receives the browse request from a browser, corresponding edition configuration file is read according to described browse request, the filename comprise described edition configuration file and version number information are supplied to described browser, to make described browser can pull corresponding static file according to described filename and version number information from described content delivery network service device, and perform the static file pulled.
The file of static file provided by the present invention pulls control device, and for an Operation Server, described device comprises:
Receiver module, for receiving the browse request from a browser;
Configuration file read module, for reading corresponding edition configuration file according to described browse request, and obtains the filename and version number information that described edition configuration file comprises;
Sending module, for described filename and version number information are supplied to described browser, so that described browser pulls the static file of corresponding each filename and version number information according to described filename and version number information from described content delivery network service device, and perform the static file pulled.
The version control system of static file provided by the present invention, comprising: a version management server, an Operation Server, a content delivery network service device and comprise the terminal of browser; Wherein,
Described version management server comprises the edition management device of above-mentioned browser static file;
The file that described Operation Server comprises above-mentioned browser static file pulls control device.
Visible, in the embodiment of the present invention, by marking a version number for each static file, such as can add a version number after the filename of static file, to the described static file of version number be marked with as file to be released, and generating the edition configuration file of at least one file to be released corresponding, this edition configuration file comprises the respective filename of at least one file to be released described and version number information; Afterwards by least one file distribution to be released described in CDN server, and described edition configuration file to be published in Operation Server with gray scale published method.Afterwards, browser is when sending browse request to Operation Server, Operation Server can read corresponding edition configuration file, and indicate browser from CDN server, pull corresponding static file, thus the clear management achieved static file version and control, avoid the confusion of static file version, and owing to gray scale published method can be adopted to issue to during multiple Operation Server released version configuration file, therefore can support that the gray scale of static file is issued.Again due to the static file that there is version updating only can be configured in edition configuration file, therefore can support that the increment of static file is issued.In addition, the static file due to different editions is simultaneous, and has identical filename, therefore when the redaction issued exists mistake, can rollback to the static file of version before, thus achieve the rollback of static file.
Accompanying drawing explanation
In order to the technical scheme in the clearer explanation embodiment of the present invention, below the accompanying drawing used required in describing embodiment is briefly described, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, to those skilled in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.Wherein,
The structural representation of a kind of implementation environment of Fig. 1 involved by each embodiment of the present invention;
Fig. 2 is the exemplary process diagram of the method for edition management of a kind of static file in the embodiment of the present invention;
Fig. 3 is the schematic flow sheet of a kind of implementation method of step 201 in flow process shown in Fig. 2;
Fig. 4 is the exemplary process diagram that the file of a kind of static file in the embodiment of the present invention pulls control method;
Fig. 5 is the exemplary process diagram of the edition control method of a kind of static file in the embodiment of the present invention;
Fig. 6 is the exemplary block diagram of the edition management device of a kind of static file in the embodiment of the present invention;
Fig. 7 is the structural representation of version number's mark module in Fig. 6 shown device;
Fig. 8 is the exemplary block diagram that the file of a kind of static file in the embodiment of the present invention pulls control device;
Fig. 9 is the structural representation of a kind of server apparatus in the embodiment of the present invention.
Embodiment
For making the object, technical solutions and advantages of the present invention clearly, the present invention is described in more detail by the following examples.
The structural representation of a kind of implementation environment of Fig. 1 involved by each embodiment of the present invention.As shown in Figure 1, this implementation environment comprises version management server 110, Operation Server 120, CDN server 130 and terminal 140.
Wherein, version management server 110, Operation Server 120 and CDN server 130 can be a station server respectively, or the server cluster be made up of some station servers respectively, or are a cloud computing service center respectively.
Run in terminal 140 and have browser, terminal 140 can be mobile phone, iPad, panel computer, pocket computer on knee and desktop computer etc.
Between version management server 110 and Operation Server 120, between version management server 110 and CDN server 130, between Operation Server 120 and terminal 140, and between CDN server 130 and terminal 140, can be connected respectively by wireless network or cable network.
Fig. 2 is the exemplary process diagram of the method for edition management of a kind of static file in the embodiment of the present invention.The method is mainly used in version management server 110.As shown in Figure 2, the method can comprise the steps:
Step 201, for each static file at least one static file marks a version number, and will be marked with the described static file of version number as file to be released.
For the mode of static file mark version number is different from the mode being distinguished version number at present by change filename.Distinguish in the mode of version number by change filename, its filename has not been original filename, namely system no longer will have the file (as a.js) of old file name and have the different editions of file (as a123.js) as identical file of the filename after change, but the two is treated as different files.And the application is in the mode of static file mark version number, do not change the filename of static file.Such as, there is a kind of implementation marking version number to be add a version number on the basis of this filename, and there is blank character, such as " _ " between this filename and version number.If version number is added after filename, then can be obtained the filename of static file by the content before detected symbol " _ ", the version number of static file can be obtained by the content after detected symbol " _ ".So, system can will be marked with the file of the identical file name of different editions number, and such as a_1001.js and a_1002.js, is considered as the different editions of identical file.
Step 202, generates the edition configuration file of at least one file to be released corresponding; Described edition configuration file comprises the respective filename of at least one file to be released described and version number information.
In this step, edition configuration file can comprise filename and the version number information of each static file required in a website.Such as, the edition configuration file of generation can be version.ini.
Step 203, by least one file distribution to be released described in CDN server 130.
In this step, at least one file to be released described can be packaged into a static resource bag, and as compressed package release.tar.gz etc., issue, CDN server 130 can carry out unpacking process afterwards, as decompressed, thus obtains each file to be released.
Step 204, is published to described edition configuration file in Operation Server 120 with gray scale published method.
Afterwards, when an Operation Server 120 receives the browse request from the browser of a terminal 140, corresponding edition configuration file is read according to described browse request, the filename comprise described edition configuration file and version number information are supplied to described browser, to make described browser can pull corresponding static file according to described filename and version number information from described CDN server 130, and perform the static file pulled.
For avoid due to the static file in step 203 do not issue successfully and cause follow-up pull static file according to edition configuration file time there is the situation that file pulls failure, in other execution mode of the present embodiment, can comprise further between step 203 and step 204: publish resource checking procedure, namely the respective filename of at least one file to be released comprised according to described edition configuration file and version number information, corresponding static file is pulled from described CDN server 130, when all static files that described edition configuration file is corresponding all pull successfully, determine that static resource is issued successfully.Now, then perform step 204.This publish resource checking procedure can be performed by version management server 110, also can be completed by other calibration equipment.If the words completed by other calibration equipment, then information interaction can be there is between version management server 110 and this calibration equipment, i.e. first version management server 110 filename that calibration equipment can be indicated to pull comprise with edition configuration file and static file corresponding to version number information, static file can be pulled result and inform to version management server 110 by calibration equipment afterwards, so that version management server 110 determines whether edition configuration file to be published in Operation Server according to this result.
In addition, static file in step 201, it can be the static file completed successively by writing identical file by different developer, also can be the different piece that different developer completes same static file respectively, namely after static subfile, then the static file obtained after each static subfile is merged.If the latter, then before step 201, can comprise further: generate a Piece file mergence configuration file, comprise in this Piece file mergence configuration file and be used to indicate respectively by which Piece file mergence Piece file mergence parameter together; According to the Piece file mergence parameter in described Piece file mergence configuration file, the static subfile of identical type each in dissimilar static subfile is merged into a static file respectively, obtains at least one static file.Such as, in exploitation file, several css subfiles and several js subfiles may be there are, then by after this union operation of execution, the static file after two merging can be obtained, i.e. a css file and a js file.
In order to the volume by low each static file, compression process can also being performed to each static file, for removing space in file, newline and annotation etc., thus obtaining each static file after compressing.
During specific implementation, step 201 can have multiple specific implementation form for the process of static file mark version number, and one has wherein been shown in Fig. 3.As shown in Figure 3, for the method for static file mark version number can comprise the steps:
Step 301, to each static file at least one static file, judges whether the original storing described static file, if do not had, performs step 302; Otherwise, perform step 303.
Step 302, for described static file generates an initial version number.
Step 303, judges that the whether meaningful renewal of original of this static file stored compared by described static file, if had, performs step 204; Otherwise, terminate current process.
Step 304, according to the version number of the described original stored, for described static file generates a new version number.
Such as, for above-mentioned a.js file, the version number generated for described static file can be 1001.
Step 305, utilizes described static file and the version number that generates to upgrade described original and version number thereof.
Step 306, is marked at generated version number in the filename of described static file, and will be marked with the static file of version number as file to be released.
Such as, for above-mentioned a.js file, when for described a.js file mark version number, can the version number 1001 generated for it be added after filename, such as, a_1001.js.
Fig. 4 is the exemplary process diagram that the file of a kind of static file in the embodiment of the present invention pulls control method.The method is mainly used in Operation Server 120.As shown in Figure 4, the method can comprise the steps:
Step 401, receives the browse request of the browser from a terminal.
In this step, this browse request can be the browse request of a corresponding website.
Step 402, reads corresponding edition configuration file according to described browse request, and extracts filename and version number information that described edition configuration file comprises.
In this step, Operation Server, according to the website browsing request of correspondence, can find corresponding edition configuration file, and the filename extracted in this edition configuration file and version number information.
Step 403, is supplied to described browser by described filename and version number information.Afterwards, the browser of described terminal pulls the static file of corresponding each filename and version number information from CDN server according to described filename and version number information, and performs the static file pulled, thus obtains the webpage of described website.
Fig. 5 is the exemplary process diagram of the edition control method of a kind of static file in the embodiment of the present invention.The method is applied in implementation environment shown in Fig. 1.As shown in Figure 5, the method comprises the steps:
Step 501, version management server is that each static file at least one static file marks a version number, and will be marked with the described static file of version number as file to be released.
Step 502, version management server generates the edition configuration file of at least one file to be released corresponding; Described edition configuration file comprises the respective filename of at least one file to be released described and version number information.
Step 503, by least one file distribution to be released described in CDN server.
In this step, at least one file to be released described can be packaged into a static resource bag and issue.
Step 504, is published to described edition configuration file in Operation Server with gray scale published method.
Step 505, Operation Server receives the browse request of the browser of self terminal.
Step 506, Operation Server reads corresponding edition configuration file according to described browse request.
Step 507, the filename that described edition configuration file comprises by Operation Server and version number information are supplied to the browser of described terminal.
Step 508, the browser of terminal sends file acquisition request to described CDN server.Described file acquisition request comprises described filename and version number information.
Step 509, the static file of described for correspondence filename and version number information is sent to the browser of terminal by CDN server.
Step 510, the browser of terminal performs the static file obtained.
Following is apparatus of the present invention embodiment, may be used for performing embodiment of the method corresponding to the present invention.For the details do not disclosed in apparatus of the present invention embodiment, please refer to the description in the inventive method embodiment.
Fig. 6 is the exemplary block diagram of the edition management device of a kind of static file in the embodiment of the present invention.This edition management device can realize becoming the some or all of of the server of version management shown in Fig. 1 110 by software, hardware or both modes of combination.This edition management device can comprise: version number's mark module 601, edition configuration file generation module 602, static resource release module 603 and edition configuration file release module 604.
Wherein, version number's mark module 601 for marking a version number for each static file at least one static file, and will be marked with the described static file of version number as file to be released.
Edition configuration file generation module 602 is for generating the edition configuration file of at least one file to be released corresponding; Described edition configuration file comprises the respective filename of at least one file to be released described and version number information.
Static resource release module 603 for by least one file distribution to be released described in content delivery network service device.
Edition configuration file release module 604 is for being published to described edition configuration file in Operation Server with gray scale published method.Afterwards, when an Operation Server receives the browse request from a browser, corresponding edition configuration file is read according to described browse request, the filename comprise described edition configuration file and version number information are supplied to described browser, to make described browser can pull corresponding static file according to described filename and version number information from described content delivery network service device, and perform the static file pulled.
In one embodiment, this device can comprise further: Piece file mergence configuration file generation module 605 and file combination module 606.
Wherein, Piece file mergence configuration file generation module 605 merges the Piece file mergence configuration file of parameter for generating include file;
The static subfile of identical type each in dissimilar static subfile, for according to the Piece file mergence parameter in described Piece file mergence configuration file, is merged into a static file, obtains at least one static file by file combination module 606 respectively.
In one embodiment, this device can comprise further: compressing file module 607, for going space/annotation compression to each static file, obtains each static file after compressing.
In one embodiment, this device can comprise further: publish resource correction verification module 608, for the respective filename of at least one file to be released of comprising according to described edition configuration file and version number information, corresponding static file is pulled from described content delivery network service device, when all static files that described edition configuration file is corresponding all pull successfully, determine that static resource is issued successfully.Correspondingly, described edition configuration file, for when determining that static resource is issued successfully, is published in Operation Server with gray scale published method by edition configuration file release module 604.
In one embodiment, described version number mark module 601 can as shown in Figure 7, comprise: memory module 701, file content judge module 702, version number's generation module 703, original update module 704 and version number add module 705.
Wherein, memory module 701 is for the version number of the original and described original that store static file.
File update judge module 702, for each static file, judges the original whether storing described static file in described memory module, if do not had, then indicates described version number generation module 703 to be that described static file generates an initial version number; Otherwise, judge that the whether meaningful renewal of described original compared by described static file, if had, then indicate described version number generation module 703 to be that described static file generates a new version number.
Version number's generation module 703 generates an initial version number for the described static file that is designated as according to described file update judge module, or according to the version number of the described original stored in described memory module 701, for described static file generates a new version number.
Original update module 704 upgrades the original of the described static file stored in described memory module and version number thereof for utilizing the version number of described static file and the generation module generation of described version number.
Version number adds module 705 and is marked in the filename of described static file for the version number generated by described version number generation module, and will be marked with the described static file of version number as file to be released.
Fig. 8 is the exemplary block diagram that the file of a kind of static file in the embodiment of the present invention pulls control device.This file pulls control device and can realize becoming the some or all of of Operation Server by software, hardware or both modes of combination.This file pulls control device and can comprise: receiver module 801, configuration file read module 802 and sending module 803.
Wherein, receiver module 801 is for receiving the browse request from a browser.
Configuration file read module 802 for reading corresponding edition configuration file according to described browse request, and obtains the filename and version number information that described edition configuration file comprises.
Sending module 803 is for being supplied to described browser by described filename and version number information, so that described browser pulls the static file of corresponding each filename and version number information according to described filename and version number information from described content delivery network service device, and perform the static file pulled.
In the embodiment of the present invention, a kind of version control system of static file comprises version management server 110 as shown in Figure 1, at least one Operation Server 120, CDN server 130 and comprises the terminal 140 of browser.
Wherein, version management server 110 can comprise the edition management device of the browser static file as described in Fig. 6 to 7; The file that Operation Server 120 comprises browser static file as shown in Figure 8 pulls control device.
Such as, version management server 110 for marking a version number for each static file at least one static file, and will be marked with the described static file of version number as file to be released; Generate the edition configuration file of at least one file to be released corresponding; Described edition configuration file comprises the respective filename of at least one file to be released described and version number information; By at least one file distribution to be released described in CDN server 130, and described edition configuration file is published in each Operation Server 120 with gray scale published method.
Operation Server 120 is for when receiving the browse request from a browser, read corresponding edition configuration file according to described browse request, the filename comprise described edition configuration file and version number information are supplied to the browser of described terminal 140.
The browser of terminal 140 is used for sending file according to described filename and version number information to described CDN server 130 and pulls request, and accepts the static file that described CDN server 130 returns, and performs described static file.Wherein, file pulls request and comprises described filename and version number information.
CDN server 130 pulls request for the file of the browser receiving self terminal 140, and the static file of the filename pulled by described for correspondence file in request and version number information sends to the browser of described terminal 140.
In one embodiment, version management server 110 to each static file at least one static file, can judge whether the original storing described static file, if do not had, then for described static file generates an initial version number; Otherwise, judge that the whether meaningful renewal of original of this static file stored compared by described static file, if had, then according to the version number of the described original stored, for described static file generates a new version number, described static file and the version number that generates is utilized to upgrade described original and version number thereof; Generated version number is marked in the filename of described static file.
In one embodiment, version management server 110 can generate the Piece file mergence configuration file that include file merges parameter further; According to the Piece file mergence parameter in described Piece file mergence configuration file, the static subfile of identical type each in dissimilar static subfile is merged into a static file respectively, obtains at least one static file.
In one embodiment, version management server 110 can go space/annotation compression to each static file further, obtains each static file after compressing.
In one embodiment, the respective filename of at least one file to be released that version management server 110 can comprise according to described edition configuration file further and version number information, corresponding static file is pulled from described content delivery network service device, when all static files that described edition configuration file is corresponding all pull successfully, determine that static resource is issued successfully, and when determining that static resource is issued successfully, described edition configuration file is published in each Operation Server 120 with gray scale published method.
Fig. 9 is the structural representation of a kind of server apparatus in the embodiment of the present invention.As shown in Figure 9, this server apparatus can comprise: processor 901, non-volatile computer readable memory 902, IOC 903, network communication interface 904.These assemblies are communicated by bus 905.
In the present embodiment, in memory 902, store multiple program module, such as, operating system 906, network communication module 907 and application program 908.
The various module (not shown)s that processor 901 can read in the application program in memory 902 are applied and data processing to the various functions performing server apparatus.Processor 901 in the present embodiment can be one, also can be multiple, and it can be CPU, processing unit/module, ASIC, logic module or programmable gate array etc.
IOC 903 has display and input equipment, for completing input, the output and display etc. of related data.
Operating system 906 includes but not limited to: Android operation system, Symbian operating system, Windows operating system, (SuSE) Linux OS etc.
Application program 908 can comprise version management server module, and this version management server module can comprise metadata and the heuritic approach 910 of set of computer-executable instructions 909 that each functional module in Fig. 6 to Fig. 7 shown device formed and correspondence.These set of computer-executable instructions can be performed by described processor 901 and complete the function of method shown in Fig. 2 to Fig. 3 or Fig. 6 to Fig. 7 shown device.Or, application program 908 can comprise file and pull Control Server module, and this file pulls metadata and the heuritic approach 910 that Control Server module can comprise set of computer-executable instructions 909 that each functional module in Fig. 8 shown device formed and correspondence.These set of computer-executable instructions can be performed by described processor 901 and complete the function of method shown in Fig. 4 or Fig. 8 shown device.
In the present embodiment, network communication interface 904 has matched with network communication module 906 transmitting-receiving of the various network signal of server apparatus, comprises and network data exchange etc. between other server or terminal.
In addition, each embodiment of the present invention can be realized by the data processor performed as computer by data processing equipment.Obviously, data processor constitutes the present invention.In addition, program is read out storage medium or memory device (as hard disk and or internal memory) the middle execution by program being installed or copied to data processing equipment by direct by the data processor be usually stored in a storage medium.Therefore, such storage medium also constitutes the present invention.Storage medium can use the recording mode of any type, such as paper storage medium (as paper tape etc.), magnetic storage medium (as floppy disk, hard disk, flash memory etc.), optical storage media (as CD-ROM etc.), magnetic-optical storage medium (as MO etc.) etc.
Therefore present invention also offers a kind of storage medium, wherein store data processor, this data processor is for performing any one embodiment of said method of the present invention.
The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, within the spirit and principles in the present invention all, any amendment made, equivalent replacement, improvement etc., all should be included within the scope of protection of the invention.
Claims (13)
1. a method for edition management for static file, is characterized in that, comprising:
For each static file at least one static file marks a version number, and will the described static file of version number be marked with as file to be released;
Generate the edition configuration file of at least one file to be released corresponding; Described edition configuration file comprises the respective filename of at least one file to be released described and version number information;
By at least one file distribution to be released described in content delivery network service device, and described edition configuration file is published in Operation Server with gray scale published method, so that when an Operation Server receives the browse request from a browser, corresponding edition configuration file is read according to described browse request, the filename comprise described edition configuration file and version number information are supplied to described browser, corresponding static file can be pulled according to described filename and version number information from described content delivery network service device to make described browser, and perform the static file pulled.
2. method according to claim 1, is characterized in that, describedly comprises for each static file at least one static file marks a version number:
To each static file at least one static file, judge whether the original storing described static file, if do not had, then for described static file generates an initial version number; Otherwise, judge that the whether meaningful renewal of original of this static file stored compared by described static file, if had, then according to the version number of the described original stored, for described static file generates a new version number, described static file and the version number that generates is utilized to upgrade described original and version number thereof; Generated version number is marked in the filename of described static file.
3. method according to claim 1, is characterized in that, the method comprises further:
Generate the Piece file mergence configuration file that include file merges parameter;
According to the Piece file mergence parameter in described Piece file mergence configuration file, the static subfile of identical type each in dissimilar static subfile is merged into a static file respectively, obtains at least one static file.
4. method according to claim 3, is characterized in that, the method comprises further: go space/annotation compression to each static file, obtain each static file after compressing.
5. method according to claim 1, is characterized in that, described edition configuration file is published in Operation Server with gray scale published method before, comprise further:
The respective filename of at least one file to be released comprised according to described edition configuration file and version number information, corresponding static file is pulled from described content delivery network service device, when all static files that described edition configuration file is corresponding all pull successfully, determine that static resource is issued successfully.
6. the file of static file pulls a control method, it is characterized in that, comprising:
Receive the browse request from a browser;
Corresponding edition configuration file is read according to described browse request, the filename comprise described edition configuration file and version number information are supplied to described browser, so that described browser pulls the static file of corresponding each filename and version number information according to described filename and version number information from described content delivery network service device, and perform the static file pulled.
7. an edition management device for static file, is characterized in that, for a version management server, described device comprises: version number's mark module, edition configuration file generation module, static resource release module and edition configuration file release module; Wherein,
Described version number mark module is used for for each static file at least one static file marks a version number, and will be marked with the described static file of version number as file to be released;
Described edition configuration file generation module is for generating the edition configuration file of at least one file to be released corresponding; Described edition configuration file comprises the respective filename of at least one file to be released described and version number information;
Described static resource release module is used at least one file distribution to be released described in content delivery network service device;
Described edition configuration file release module is used for described edition configuration file to be published in Operation Server with gray scale published method, so that when an Operation Server receives the browse request from a browser, corresponding edition configuration file is read according to described browse request, the filename comprise described edition configuration file and version number information are supplied to described browser, to make described browser can pull corresponding static file according to described filename and version number information from described content delivery network service device, and perform the static file pulled.
8. device according to claim 7, is characterized in that, described version number mark module comprises: memory module, file content judge module, version number's generation module, original update module and version number add module; Wherein,
Described memory module is for the version number of the original and described original that store static file;
Described file update judge module is used for each static file, judges the original whether storing described static file in described memory module, if do not had, then indicates described version number generation module to be that described static file generates an initial version number; Otherwise, judge that the whether meaningful renewal of described original compared by described static file, if had, then indicate described version number generation module to be that described static file generates a new version number;
Described version number generation module is used for generating an initial version number according to the described static file that is designated as of described file update judge module, or according to the version number of the described original stored in described memory module, for described static file generates a new version number;
Described original update module upgrades the original of the described static file stored in described memory module and version number thereof for utilizing the version number of described static file and the generation module generation of described version number;
Described version number adds module and is marked in the filename of described static file for the version number generated by described version number generation module, and will be marked with the described static file of version number as file to be released.
9. device according to claim 8, is characterized in that, this device comprises further:
Piece file mergence configuration file generation module, merges the Piece file mergence configuration file of parameter for generating include file;
File combination module, for according to the Piece file mergence parameter in described Piece file mergence configuration file, is merged into a static file respectively by the static subfile of identical type each in dissimilar static subfile, obtains at least one static file.
10. device according to claim 9, is characterized in that, this device comprises further:
Compressing file module, for going space/annotation compression to each static file, obtains each static file after compressing.
11. devices according to claim 7, is characterized in that, this device comprises further:
Publish resource correction verification module, for the respective filename of at least one file to be released of comprising according to described edition configuration file and version number information, corresponding static file is pulled from described content delivery network service device, when all static files that described edition configuration file is corresponding all pull successfully, determine that static resource is issued successfully;
Described edition configuration file release module is used for when determining that static resource is issued successfully, is published in Operation Server by described edition configuration file with gray scale published method.
The file of 12. 1 kinds of static files pulls control device, it is characterized in that, for an Operation Server, described device comprises:
Receiver module, for receiving the browse request from a browser;
Configuration file read module, for reading corresponding edition configuration file according to described browse request, and obtains the filename and version number information that described edition configuration file comprises;
Sending module, for described filename and version number information are supplied to described browser, so that described browser pulls the static file of corresponding each filename and version number information according to described filename and version number information from described content delivery network service device, and perform the static file pulled.
The version control system of 13. 1 kinds of static files, is characterized in that, comprising: a version management server, an Operation Server, a content delivery network service device and comprise the terminal of browser; Wherein,
Described version management server comprises the edition management device of the browser static file according to any one of claim 7 to 11;
The file that described Operation Server comprises browser static file as claimed in claim 12 pulls control device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510333621.6A CN105049486B (en) | 2015-06-16 | 2015-06-16 | Method for edition management, the apparatus and system of static file |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510333621.6A CN105049486B (en) | 2015-06-16 | 2015-06-16 | Method for edition management, the apparatus and system of static file |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105049486A true CN105049486A (en) | 2015-11-11 |
| CN105049486B CN105049486B (en) | 2019-03-26 |
Family
ID=54455689
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510333621.6A Active CN105049486B (en) | 2015-06-16 | 2015-06-16 | Method for edition management, the apparatus and system of static file |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105049486B (en) |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105354037A (en) * | 2015-11-30 | 2016-02-24 | 用友优普信息技术有限公司 | Modularized software developing method and software developing device |
| CN106445488A (en) * | 2016-07-01 | 2017-02-22 | 厦门易名科技股份有限公司 | Code release and backspacing methods |
| CN106713460A (en) * | 2016-12-26 | 2017-05-24 | 武汉斗鱼网络科技有限公司 | Version control method and system for flash application |
| CN106843935A (en) * | 2016-12-29 | 2017-06-13 | 广州华多网络科技有限公司 | A kind of method and system for automatically updating static file version number |
| CN106959872A (en) * | 2017-03-16 | 2017-07-18 | 微梦创科网络科技（中国）有限公司 | Using loading method and device |
| CN107102992A (en) * | 2016-02-19 | 2017-08-29 | 北大方正集团有限公司 | A kind of static dissemination method of new media and device |
| CN107229655A (en) * | 2016-03-25 | 2017-10-03 | 北京京东尚科信息技术有限公司 | The update method of page static file, apparatus and system |
| CN107241451A (en) * | 2017-08-04 | 2017-10-10 | 网宿科技股份有限公司 | Interference method, apparatus and system are distorted based on content distributing network |
| CN107343031A (en) * | 2017-06-21 | 2017-11-10 | 福建中金在线信息科技有限公司 | A kind of method, apparatus for automatically updating file, electronic equipment and storage medium |
| CN107357890A (en) * | 2017-07-12 | 2017-11-17 | 腾讯科技（深圳）有限公司 | A kind of web page files processing method, apparatus and system and storage device |
| CN107370791A (en) * | 2017-06-23 | 2017-11-21 | 微梦创科网络科技（中国）有限公司 | The method and system of filename in automatic synchronization renewal content distributing network |
| CN107465707A (en) * | 2016-06-03 | 2017-12-12 | 阿里巴巴集团控股有限公司 | A kind of content refresh method and device of content distributing network |
| CN107678936A (en) * | 2017-06-25 | 2018-02-09 | 平安科技（深圳）有限公司 | The advance checking method of operation system, server and computer-readable recording medium |
| CN107704465A (en) * | 2016-08-08 | 2018-02-16 | 腾讯科技（深圳）有限公司 | Static resource update method and static resource management system |
| CN108052334A (en) * | 2017-12-22 | 2018-05-18 | 平安养老保险股份有限公司 | Method for page jump, device, computer equipment and storage medium |
| CN108153663A (en) * | 2016-12-02 | 2018-06-12 | 阿里巴巴集团控股有限公司 | Page data processing method and device |
| CN109002557A (en) * | 2018-08-15 | 2018-12-14 | 深圳点猫科技有限公司 | Method, electronic equipment based on browser rs cache mechanism optimization webpage loading velocity |
| CN109358895A (en) * | 2017-12-28 | 2019-02-19 | 广州Tcl智能家居科技有限公司 | A kind of dispositions method of HXML, storage medium and application server |
| CN109542988A (en) * | 2018-10-19 | 2019-03-29 | 深圳点猫科技有限公司 | A kind of update method and electronic equipment of big data |
| CN110399341A (en) * | 2019-07-06 | 2019-11-01 | 深圳市山水原创动漫文化有限公司 | A kind of method and its system animation reference paper storage and called |
| CN110809036A (en) * | 2019-10-25 | 2020-02-18 | 无线生活(北京)信息技术有限公司 | Resource updating method and device |
| CN111338824A (en) * | 2020-02-27 | 2020-06-26 | 中国联合网络通信集团有限公司 | Gray scale distribution method and device, electronic equipment and storage medium |
| CN112541147A (en) * | 2019-09-23 | 2021-03-23 | 北京轻享科技有限公司 | Content publishing management method and system |
| CN113377400A (en) * | 2021-06-16 | 2021-09-10 | 广州博冠信息科技有限公司 | Software upgrading method and device, storage medium and electronic equipment |
| TWI757733B (en) * | 2020-05-05 | 2022-03-11 | 華碩電腦股份有限公司 | Network data collection method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102109989A (en) * | 2009-12-29 | 2011-06-29 | 阿里巴巴集团控股有限公司 | Method, device and system for controlling browser cache |
| CN102480397A (en) * | 2010-11-26 | 2012-05-30 | 金蝶软件（中国）有限公司 | Method and equipment for accessing internet pages |
| CN104038520A (en) * | 2013-03-05 | 2014-09-10 | 北京畅游天下网络技术有限公司 | Multi-version distributed resource management method and multi-version distributed resource management system |
| CN104462469A (en) * | 2014-12-17 | 2015-03-25 | 小米科技有限责任公司 | Updating method and updating device for website static files |
-
2015
- 2015-06-16 CN CN201510333621.6A patent/CN105049486B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102109989A (en) * | 2009-12-29 | 2011-06-29 | 阿里巴巴集团控股有限公司 | Method, device and system for controlling browser cache |
| CN102480397A (en) * | 2010-11-26 | 2012-05-30 | 金蝶软件（中国）有限公司 | Method and equipment for accessing internet pages |
| CN104038520A (en) * | 2013-03-05 | 2014-09-10 | 北京畅游天下网络技术有限公司 | Multi-version distributed resource management method and multi-version distributed resource management system |
| CN104462469A (en) * | 2014-12-17 | 2015-03-25 | 小米科技有限责任公司 | Updating method and updating device for website static files |
Cited By (36)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105354037B (en) * | 2015-11-30 | 2019-04-16 | 用友优普信息技术有限公司 | Modular software development methodology and software development apparatus |
| CN105354037A (en) * | 2015-11-30 | 2016-02-24 | 用友优普信息技术有限公司 | Modularized software developing method and software developing device |
| CN107102992A (en) * | 2016-02-19 | 2017-08-29 | 北大方正集团有限公司 | A kind of static dissemination method of new media and device |
| CN107229655B (en) * | 2016-03-25 | 2021-05-25 | 北京京东尚科信息技术有限公司 | Updating method, device and system of page static file |
| CN107229655A (en) * | 2016-03-25 | 2017-10-03 | 北京京东尚科信息技术有限公司 | The update method of page static file, apparatus and system |
| CN107465707A (en) * | 2016-06-03 | 2017-12-12 | 阿里巴巴集团控股有限公司 | A kind of content refresh method and device of content distributing network |
| CN107465707B (en) * | 2016-06-03 | 2021-02-02 | 阿里巴巴集团控股有限公司 | Content refreshing method and device for content distribution network |
| CN106445488A (en) * | 2016-07-01 | 2017-02-22 | 厦门易名科技股份有限公司 | Code release and backspacing methods |
| CN107704465B (en) * | 2016-08-08 | 2021-11-16 | 腾讯科技（深圳）有限公司 | Static resource updating method and static resource management system |
| CN107704465A (en) * | 2016-08-08 | 2018-02-16 | 腾讯科技（深圳）有限公司 | Static resource update method and static resource management system |
| CN108153663A (en) * | 2016-12-02 | 2018-06-12 | 阿里巴巴集团控股有限公司 | Page data processing method and device |
| CN108153663B (en) * | 2016-12-02 | 2022-02-18 | 阿里巴巴集团控股有限公司 | Page data processing method and device |
| WO2018120436A1 (en) * | 2016-12-26 | 2018-07-05 | 武汉斗鱼网络科技有限公司 | Version control method and system for flash application |
| CN106713460A (en) * | 2016-12-26 | 2017-05-24 | 武汉斗鱼网络科技有限公司 | Version control method and system for flash application |
| CN106713460B (en) * | 2016-12-26 | 2019-12-10 | 武汉斗鱼网络科技有限公司 | Version control method and system for flash application |
| CN106843935A (en) * | 2016-12-29 | 2017-06-13 | 广州华多网络科技有限公司 | A kind of method and system for automatically updating static file version number |
| CN106959872A (en) * | 2017-03-16 | 2017-07-18 | 微梦创科网络科技（中国）有限公司 | Using loading method and device |
| CN107343031A (en) * | 2017-06-21 | 2017-11-10 | 福建中金在线信息科技有限公司 | A kind of method, apparatus for automatically updating file, electronic equipment and storage medium |
| CN107370791A (en) * | 2017-06-23 | 2017-11-21 | 微梦创科网络科技（中国）有限公司 | The method and system of filename in automatic synchronization renewal content distributing network |
| CN107678936A (en) * | 2017-06-25 | 2018-02-09 | 平安科技（深圳）有限公司 | The advance checking method of operation system, server and computer-readable recording medium |
| WO2019000963A1 (en) * | 2017-06-25 | 2019-01-03 | 平安科技（深圳）有限公司 | Pre-inspection method for service system, server, and computer readable storage medium |
| CN107357890A (en) * | 2017-07-12 | 2017-11-17 | 腾讯科技（深圳）有限公司 | A kind of web page files processing method, apparatus and system and storage device |
| CN107357890B (en) * | 2017-07-12 | 2023-03-24 | 腾讯科技（深圳）有限公司 | Webpage file processing method, device and system and storage equipment |
| CN107241451A (en) * | 2017-08-04 | 2017-10-10 | 网宿科技股份有限公司 | Interference method, apparatus and system are distorted based on content distributing network |
| CN108052334A (en) * | 2017-12-22 | 2018-05-18 | 平安养老保险股份有限公司 | Method for page jump, device, computer equipment and storage medium |
| CN109358895A (en) * | 2017-12-28 | 2019-02-19 | 广州Tcl智能家居科技有限公司 | A kind of dispositions method of HXML, storage medium and application server |
| CN109002557A (en) * | 2018-08-15 | 2018-12-14 | 深圳点猫科技有限公司 | Method, electronic equipment based on browser rs cache mechanism optimization webpage loading velocity |
| CN109542988A (en) * | 2018-10-19 | 2019-03-29 | 深圳点猫科技有限公司 | A kind of update method and electronic equipment of big data |
| CN110399341A (en) * | 2019-07-06 | 2019-11-01 | 深圳市山水原创动漫文化有限公司 | A kind of method and its system animation reference paper storage and called |
| CN110399341B (en) * | 2019-07-06 | 2022-12-06 | 深圳市山水原创动漫文化有限公司 | Method and system for storing and calling animation reference file |
| CN112541147A (en) * | 2019-09-23 | 2021-03-23 | 北京轻享科技有限公司 | Content publishing management method and system |
| CN110809036A (en) * | 2019-10-25 | 2020-02-18 | 无线生活(北京)信息技术有限公司 | Resource updating method and device |
| CN111338824A (en) * | 2020-02-27 | 2020-06-26 | 中国联合网络通信集团有限公司 | Gray scale distribution method and device, electronic equipment and storage medium |
| CN111338824B (en) * | 2020-02-27 | 2023-08-15 | 中国联合网络通信集团有限公司 | Gray release method and device, electronic equipment and storage medium |
| TWI757733B (en) * | 2020-05-05 | 2022-03-11 | 華碩電腦股份有限公司 | Network data collection method |
| CN113377400A (en) * | 2021-06-16 | 2021-09-10 | 广州博冠信息科技有限公司 | Software upgrading method and device, storage medium and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105049486B (en) | 2019-03-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105049486A (en) | Version management and file pulling control methods for static files, version management and file pulling control devices, and version control system | |
| CN107870728B (en) | Method and apparatus for moving data | |
| US10474632B2 (en) | Segmented hashing for secure data modification | |
| KR102042723B1 (en) | Methods for updating applications | |
| US9569400B2 (en) | RDMA-optimized high-performance distributed cache | |
| CN108228818A (en) | Web page resources loading method and device, electronic equipment and storage medium | |
| US20200412644A1 (en) | Content based routing method and apparatus | |
| CN104182294A (en) | Method and device for backing up and recovering file | |
| US7376650B1 (en) | Method and system for redirecting a request using redirection patterns | |
| CN106817388B (en) | Method and device for acquiring data by virtual machine and host machine and system for accessing data | |
| CN106921682A (en) | File uploading method and device | |
| CN111459511A (en) | Application program downloading method and device and electronic equipment | |
| CN108268609A (en) | A kind of foundation of file path, access method and device | |
| CN105740330A (en) | Data paging display method and apparatus | |
| CN105160018A (en) | Method, device and system for image copy/paste | |
| CN112395253A (en) | Index file generation method, terminal device, electronic device and medium | |
| CN111724133A (en) | Method and device for creating project | |
| CN110119386B (en) | Data processing method, data processing apparatus, medium, and computing device | |
| CN111107133A (en) | Generation method of difference packet, data updating method, device and storage medium | |
| US20190012159A1 (en) | Systems and methods for uninstalling or upgrading software if package cache is removed or corrupted | |
| CN106156291A (en) | The caching method of static resource and system thereof based on Localstroage | |
| US11138287B1 (en) | System for reducing size of transmitted content | |
| CN106569841B (en) | File loading method and device | |
| CN113761412A (en) | Application page display method and device, electronic equipment, medium and application system | |
| CN115150392B (en) | Remote file copying method, system, computing equipment and storage medium |
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 |