CN105224344A - A kind of software upgrading file configuration method realized based on XML - Google Patents
A kind of software upgrading file configuration method realized based on XML Download PDFInfo
- Publication number
- CN105224344A CN105224344A CN201410228629.1A CN201410228629A CN105224344A CN 105224344 A CN105224344 A CN 105224344A CN 201410228629 A CN201410228629 A CN 201410228629A CN 105224344 A CN105224344 A CN 105224344A
- Authority
- CN
- China
- Prior art keywords
- file
- xml
- configuration file
- xml configuration
- server end
- 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.)
- Pending
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The present invention discloses a kind of software upgrading file configuration method realized based on XML, especially relates to a kind of method using XML configuration file to manage the upgrade file version information that server end is disposed.The method refers at server end by an XML configuration file, dispose each upgrade file version number to server end to manage, client before upgrading, Download Server end XML configuration file, and upgraded with local last time the XML configuration file obtained and contrast, if the version number in XML configuration file is greater than the version number in local XML configuration file, then download this file, and the file downloaded is replaced local original file, thus realize the increment upgrading of upgrade file.
Description
Technical field
The present invention relates to a kind of software upgrading file configuration method realized based on XML, especially relate to a kind of method using XML configuration file to manage the upgrade file version information that server end is disposed, belong to electronic information technical field.
Background technology
The present invention relates to a kind of software upgrading file configuration method realized based on XML, so-called software upgrading file configuration method refers at server end by an XML configuration file, dispose each upgrade file version number to server end to manage, client before upgrading, communicate by carrying out Socket with server end, Download Server end XML configuration file, and upgraded with local last time the XML configuration file obtained and contrast, if the version number in XML configuration file is greater than the version number in local XML configuration file, then download this file, and the file downloaded is replaced local original file, thus realize the increment upgrading of upgrade file.
At present, web application based on client end/server end framework mostly possesses online upgrading function, that issues along with application program redaction increases, the client application of a lot of user installation is not upgraded in time, the application program in using is caused to be in different intermediate releases, and each redaction can relate to the amendment of multiple file, the mode how allowing the user being in different editions be upgraded by increment is upgraded to latest edition, and can to the upgrade file unified plan of server end, it is all the problem of the headache in Network application and development field all the time.
The upgrading scheme of current use is mostly do a large and complete AKU, comprise the file related in all up-to-date web applications, but this upgrading mode can make the redundancy of each version increase, update time is longer, therefore, for a kind of can unified plan, increment upgrading software upgrading file configuration method propose requirement.
Summary of the invention
For the deficiency of original technical scheme, and in conjunction with the advantage of XML file, the software upgrading file configuration method realized based on XML provided by the invention, it is characterized in that, comprise: dispose the file of new edition amendment at server end by the software application bibliographic structure identical with client, and according to the XML configuration file structure designed by invention, amendment is corresponding operation note file wherein.
The complete escalation process of client that the present invention realizes is as follows:
The first step: client sends software upgrading request;
Second step: server end sends XML upgrading configuration, and client receives;
3rd: client contrasts receiving XML file and upgrading the rear XML upgrading configuration stored last time;
4th: first compare the total version number in XML upgrading configuration, if the total version number in this XML file obtained of total version number and server end in local XML file is identical, then stop subsequent operation and renewal;
5th: the same file version number successively in more local XML file in the version number of each file and this XML file obtained of server end, if difference, ask to download corresponding document, and cover local file;
6th step: the XML upgrading configuration obtained is covered local upgrading configuration.
Here several key character is had:
Feature one: the XML upgrading configuration that server end is disposed is identical with the XML file structure that this locality stores
After upgrading completes, the XML upgrading configuration of up-to-date acquisition can be covered the XML file of local storage by client, the comparison that the local XML file stored will be used as when upgrading next time;
Feature two: increment is upgraded
In whole escalation process, whether the total version number first detected in XML upgrading configuration is identical, determined whether that redaction is issued.When confirming that total version number is different, compare the file and version number that store in XML upgrading configuration successively, because local XML file upgraded rear acquisition last time, when sending out respective file and having version number to change, then can confirm which file needs to upgrade, thus achieve increment upgrading;
Feature three: for different intermediate releases unified plan
The XML upgrading configuration of disposing at server end has uniqueness, each issue redaction only needs the file operation record of this upgrading variation to be updated in XML upgrading configuration, and all clients being in different intermediate releases all can realize increment upgrading according to this XML upgrading configuration.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, specific embodiments of the present invention are further described in detail, wherein:
Fig. 1 is the XML upgrading configuration structural representation of design of the present invention;
Fig. 2 is server end upgrade file structure category schematic diagram of the present invention;
Fig. 3 is complete escalation process schematic flow sheet of the present invention.
Embodiment
Below in conjunction with drawings and Examples, the technical solution of the present invention is further explained, but following content is not intended to limit the scope of the invention.
As shown in Figure 1, be the XML upgrading configuration structural representation of design of the present invention, be described as follows:
Version node Shi Zong version number under software node under config node, is revised as up-to-date version number when new version file is disposed in each upgrading;
Node under root node under config node is filename and the latest edition number of the upgrade file of all deployment, new version file is disposed in each upgrading, if there is the node of this file, only upgrading the version number that this node preserves has been latest edition number, if there is not the node of this file, newly-increased node, the name attribute of node preserves filename, and node content is latest edition number; If the upgrade file disposed is stored in sub-directory, then directory node is used to represent catalogue, name property store pathname.
The escalation process that the present invention is above-mentioned:
Client and server is set up Socket and is connected, and sends software upgrading request;
Server end receives software upgrading request, and send the XML upgrading configuration that server end stores, client receives;
Client reads the XML upgrading configuration of XML upgrading configuration and this locality received, and compares; Whether the total version number compared in the XML upgrading configuration of server end is greater than total version number that local XML upgrading configuration stores, if identical, illustrate and does not upgrade, do not perform subsequent operation, exit upgrading.
Client reads the file node under the root node under the config node in the XML upgrading configuration of server end successively, if there is not the file node of same file name in the XML upgrading configuration of this locality, or fileversion number is greater than local file version number, then illustrate that the file that file node is corresponding has redaction.
Client-requested server end downloads the file of redaction, carries out local file replacement.
All Files is downloaded and has been replaced, and the XML upgrading configuration of the server end this upgrading downloaded replaces local XML upgrading configuration.
Claims (5)
1., based on the software upgrading file configuration method that XML realizes, it is characterized in that being managed by the version number of an XML configuration file to all upgrade files that server end is disposed at server end; Client communicates by carrying out Socket with server, obtains the XML configuration file of server end, and upgrades with local last time the XML configuration file obtained and contrast; If there is fileversion number to be greater than response file version number in local XML configuration file in the XML configuration file of server end, then download this file, and the file downloaded is replaced local original file, realize document upgrading.
2. according to claim 1ly to be managed by the version number of an XML configuration file to all upgrade files that server end is disposed, it is characterized in that use file, and store the latest edition number of the upgrade file of all deployment according to the form of XML extend markup language.
3. in XML configuration file according to claim 2, store the latest edition number of upgrade file, it is characterized in that the situation that actual upgrade is disposed is different, each upgrading is disposed and only may be revised the version number of partial document to up-to-date, finally can cause the All Files version number possibility difference stored in XML configuration file, but ensure it is latest edition number.
4. client according to claim 1 will obtain the XML configuration file of server end, and upgraded with local last time the XML configuration file obtained and contrast, it is characterized in that client determines whether the XML configuration file needing upgrading, which file needs renewal only needs an acquisition server end.
5. according to claim 4ly the XML configuration file obtaining server end was upgraded with local last time the XML configuration file obtained contrast, it is characterized in that server end is consistent with the XML configuration file form of this locality.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201410228629.1A CN105224344A (en) | 2014-05-28 | 2014-05-28 | A kind of software upgrading file configuration method realized based on XML |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201410228629.1A CN105224344A (en) | 2014-05-28 | 2014-05-28 | A kind of software upgrading file configuration method realized based on XML |
Publications (1)
Publication Number | Publication Date |
---|---|
CN105224344A true CN105224344A (en) | 2016-01-06 |
Family
ID=54993340
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201410228629.1A Pending CN105224344A (en) | 2014-05-28 | 2014-05-28 | A kind of software upgrading file configuration method realized based on XML |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN105224344A (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106371881A (en) * | 2016-09-08 | 2017-02-01 | 武汉斗鱼网络科技有限公司 | Method and system for updating program versions in servers |
CN106371856A (en) * | 2016-11-08 | 2017-02-01 | 深圳天珑无线科技有限公司 | Menu statistical method and user terminal and application backstage terminal |
WO2017124976A1 (en) * | 2016-01-22 | 2017-07-27 | 阿里巴巴集团控股有限公司 | Method and device for acquiring application resource |
CN107341025A (en) * | 2016-05-03 | 2017-11-10 | 北京京东尚科信息技术有限公司 | Using update method and device |
CN107423078A (en) * | 2017-02-28 | 2017-12-01 | 福建中金在线信息科技有限公司 | A kind of Oftware updating method and device |
CN107643920A (en) * | 2016-07-20 | 2018-01-30 | 平安科技(深圳)有限公司 | Application software update method and device |
CN107678766A (en) * | 2017-10-20 | 2018-02-09 | 国云科技股份有限公司 | A kind of promotion and demotion method of CONFIG.SYS |
CN108989074A (en) * | 2017-06-05 | 2018-12-11 | 北大方正集团有限公司 | Programme upgrade method and program upgrade apparatus |
WO2019095387A1 (en) * | 2017-11-16 | 2019-05-23 | 青岛海信电器股份有限公司 | Remotely-assisted automatic upgrading method and device |
CN114090048A (en) * | 2021-11-27 | 2022-02-25 | 深圳市元征科技股份有限公司 | Software upgrading method and device |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101436141A (en) * | 2008-11-21 | 2009-05-20 | 深圳创维数字技术股份有限公司 | Firmware upgrading and encapsulating method and device based on digital signing |
CN102056025A (en) * | 2009-10-30 | 2011-05-11 | 深圳Tcl新技术有限公司 | Method for upgrading IPTV module |
CN103064699A (en) * | 2012-11-28 | 2013-04-24 | 镇江为天下信息服务有限公司 | Method for quickly updating files in software upgrading process |
-
2014
- 2014-05-28 CN CN201410228629.1A patent/CN105224344A/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101436141A (en) * | 2008-11-21 | 2009-05-20 | 深圳创维数字技术股份有限公司 | Firmware upgrading and encapsulating method and device based on digital signing |
CN102056025A (en) * | 2009-10-30 | 2011-05-11 | 深圳Tcl新技术有限公司 | Method for upgrading IPTV module |
CN103064699A (en) * | 2012-11-28 | 2013-04-24 | 镇江为天下信息服务有限公司 | Method for quickly updating files in software upgrading process |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017124976A1 (en) * | 2016-01-22 | 2017-07-27 | 阿里巴巴集团控股有限公司 | Method and device for acquiring application resource |
CN107341025A (en) * | 2016-05-03 | 2017-11-10 | 北京京东尚科信息技术有限公司 | Using update method and device |
CN107341025B (en) * | 2016-05-03 | 2021-09-03 | 北京京东尚科信息技术有限公司 | Application updating method and device |
CN107643920A (en) * | 2016-07-20 | 2018-01-30 | 平安科技(深圳)有限公司 | Application software update method and device |
CN106371881A (en) * | 2016-09-08 | 2017-02-01 | 武汉斗鱼网络科技有限公司 | Method and system for updating program versions in servers |
CN106371881B (en) * | 2016-09-08 | 2020-01-03 | 武汉斗鱼网络科技有限公司 | Method and system for updating program version in server |
CN106371856A (en) * | 2016-11-08 | 2017-02-01 | 深圳天珑无线科技有限公司 | Menu statistical method and user terminal and application backstage terminal |
CN107423078A (en) * | 2017-02-28 | 2017-12-01 | 福建中金在线信息科技有限公司 | A kind of Oftware updating method and device |
CN108989074A (en) * | 2017-06-05 | 2018-12-11 | 北大方正集团有限公司 | Programme upgrade method and program upgrade apparatus |
CN107678766A (en) * | 2017-10-20 | 2018-02-09 | 国云科技股份有限公司 | A kind of promotion and demotion method of CONFIG.SYS |
WO2019095387A1 (en) * | 2017-11-16 | 2019-05-23 | 青岛海信电器股份有限公司 | Remotely-assisted automatic upgrading method and device |
CN114090048A (en) * | 2021-11-27 | 2022-02-25 | 深圳市元征科技股份有限公司 | Software upgrading method and device |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN105224344A (en) | A kind of software upgrading file configuration method realized based on XML | |
US10212563B2 (en) | Updating web resources | |
CN103701856A (en) | Method for defining and acquiring upgrade package of terminal equipment | |
CN104683303B (en) | APP management methods | |
US9274783B2 (en) | Dynamic delivery and integration of static content into cloud | |
CN102081536A (en) | Method for updating increment, and server | |
CN106406943A (en) | Customized upgrading method and system for clients of different versions | |
CN102195804A (en) | Automatic updating method of software and system thereof | |
CN103167041A (en) | System and method for supporting cloud environment application cluster automation deployment | |
CN102833101B (en) | Software upgrading method and equipment of distributed network system | |
CN104765816B (en) | Browser upgrading method and device and electronic equipment | |
WO2011069730A1 (en) | A method and system for managing configurations of system management agents in a distributed environment | |
CN107025108B (en) | Exporting hierarchical data from a Source Code Management (SCM) system to a Product Lifecycle Management (PLM) system | |
CN101140589A (en) | Reminding device and method used for download system | |
CN103544030A (en) | Software upgrading method, software upgrading system and intelligent terminal | |
CN110389766A (en) | HBase container cluster dispositions method, system, equipment and computer readable storage medium | |
CN104699511A (en) | Plug-in upgrading method and plug-in upgrading device | |
CN103051689A (en) | Program updating downloading method and device | |
CN103049283A (en) | Automatic updating method for setting version numbers for every software file | |
CN107038519A (en) | Production Lifecycle Management(PLM)System and Source code management(SCM)Bi-directional data between system is synchronous | |
CN103176826A (en) | Method for freely configuring terminal equipment default language and terminal default language configuration system | |
CN103019795A (en) | Method and system for upgrading software basic data | |
CN110597764B (en) | File downloading and version management method and device | |
CN105912641A (en) | Icon update method and apparatus of Native Apps | |
CN102541593A (en) | Rapid comparison method of versions of remote files |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
WD01 | Invention patent application deemed withdrawn after publication | ||
WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20160106 |