CN111176676B - Automatic upgrading method and system for single file application program - Google Patents
Automatic upgrading method and system for single file application program Download PDFInfo
- Publication number
- CN111176676B CN111176676B CN201911301640.5A CN201911301640A CN111176676B CN 111176676 B CN111176676 B CN 111176676B CN 201911301640 A CN201911301640 A CN 201911301640A CN 111176676 B CN111176676 B CN 111176676B
- Authority
- CN
- China
- Prior art keywords
- file
- application program
- upgrade
- named
- upgrade 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a system for automatically upgrading a single file application program, wherein the method comprises the following steps: entering a current application process to obtain current application process information, wherein the application process information comprises a corresponding cloud download address and the file size of a current application program; detecting whether an application program named as an upgrade file exists under the address according to the cloud download address; if the upgrade file application program exists, acquiring the file size of the upgrade file application program, comparing the file size with the file size of the current application program, and confirming whether the file size is consistent; if the file sizes are inconsistent, downloading the upgrade file application program; replacing the current application program with the upgrade file application program to finish upgrading; the method and the system do not need to configure background data and do not depend on the support of a background service interface, so that the problem that the background service is down and cannot be updated is avoided, and the workload of operation and maintenance is reduced.
Description
Technical Field
The invention relates to the technical field of information, in particular to an automatic upgrading method and system for a single file application program.
Background
In order to facilitate the use and redevelopment of the integrated service system, a common single file application is a common implementation means. When the client starts the single file application program, the client can interact parameters with the single file application program, can also independently operate, does not need decompression or installation, and is convenient to propagate.
To ensure maintainability, single file applications also need to support automatic upgrades. However, the conventional upgrading method cannot be directly applied, because the single file application program has no independent upgrading program except the self file, and the problem of file occupation exists during upgrading. And the traditional upgrading program generally needs to additionally develop a matched background service interface, so that the development workload is large.
Disclosure of Invention
In order to solve the problems of additional development and large workload of single file application program upgrading in the background technology, the invention provides a method and a system for automatically upgrading a single file application program. The method for automatically upgrading the single file application program comprises the following steps:
entering a current application process to obtain current application process information, wherein the application process information comprises a corresponding cloud download address and the file size of a current application program;
detecting whether an application program named as an upgrade file exists under the address according to the cloud download address;
if the upgrade file application program exists, acquiring the file size of the upgrade file application program, comparing the file size with the file size of the current application program, and confirming whether the file size is consistent;
if the file sizes are inconsistent, downloading the upgrade file application program;
and replacing the current application program with the upgrade file application program to finish upgrading.
Furthermore, if no application program named as an upgrade file exists under the cloud download address, the application is directly operated without upgrading.
Further, the upgrade file application program is downloaded in a preset downloading mode; the preset downloading mode comprises a breakpoint continuous mode and a distributed downloading mode.
Further, the replacing the current application program with the upgrade file application program includes:
starting the process of the upgrade file application program through the current application process;
copying the upgrade file application program process to cover the current application program process, and restarting the current application program process;
and deleting the upgrade file application program.
Further, after entering the current application process, the method further includes:
confirming the name of the current application entering;
if the current application process is named as an upgrade file, detecting whether a corresponding application program named as an original file exists locally;
if so, replacing the application program named as the original file by the application program named as the upgrade file, mutually transferring parameters between the upgrade file application program process and the current application program process, and deleting redundant corresponding application programs;
if not, the application program named as the upgrade file is directly named as the original file.
Further, before entering the current application process, the method further includes:
generating a single file application program named as an upgrade file according to a preset rule;
comparing the single file application program named as the upgrade file with the file size of the current application program, and confirming whether the file size is consistent;
if the file sizes are consistent, adding redundant codes to the single file application program named as the upgrade file, so that the file sizes are inconsistent.
Further, the generating the preset rule of the single file application program includes:
directly compiling to obtain a single executable file as a single file application program; or (b)
And merging the executable file, the dynamic link library, the configuration file and the resource file through a file merging tool to obtain a single executable file as a single file application program.
The system for automatically upgrading the single file application program comprises the following components:
the application process running unit is used for entering a current application process to obtain current application process information, wherein the application process information comprises a corresponding cloud download address and the file size of a current application program;
the file size comparison unit is used for detecting whether an application program named as an upgrade file exists at the address according to the cloud download address; if the upgrade file application program exists, the file size comparison unit acquires the file size of the upgrade file application program, compares the file size with the file size of the current application program, and confirms whether the file sizes are consistent;
the downloading unit is used for downloading the upgrade file application program when the file sizes are inconsistent compared by the file size comparison unit;
and the replacing unit is used for replacing the current application program by using the upgrade file application program to finish upgrading.
Furthermore, if the file size comparison unit detects that an application program named as an upgrade file does not exist at the cloud download address, the application is directly operated without upgrading.
Further, the downloading unit is used for downloading the upgrade file application program in a preset downloading mode; the preset downloading mode comprises a breakpoint continuous mode and a distributed downloading mode.
Further, the replacing unit is used for starting the process of the upgrade file application program through the current application process;
the replacing unit is used for copying the upgrade file application program process to cover the current application program process, restarting the current application program process and deleting the upgrade file application program.
Further, the application process running unit confirms the naming of the current application; if the current application process is named as an upgrade file, detecting whether a corresponding application program named as an original file exists locally;
if so, the replacing unit replaces the application program named as the original file with the application program named as the upgrading file, mutually transmits parameters between the upgrading file application program process and the current application program process, and deletes redundant corresponding application programs;
if not, the replacing unit directly names the application program named as the upgrade file as an original file.
Further, the system also comprises an upgrade file generation unit;
the upgrade file generation unit generates a single file application program named as an upgrade file according to a preset rule;
the upgrade file generation unit compares the single file application program named as the upgrade file with the file size of the current application program to confirm whether the file sizes are consistent;
if the file sizes are consistent, the upgrade file generation unit adds redundancy codes to the single file application program named as the upgrade file, so that the file sizes are inconsistent.
Further, the generating the preset rule of the single file application program includes:
directly compiling to obtain a single executable file as a single file application program; or (b)
And merging the executable file, the dynamic link library, the configuration file and the resource file through a file merging tool to obtain a single executable file as a single file application program.
The beneficial effects of the invention are as follows: according to the technical scheme, the method and the system for automatically upgrading the single file application program are provided, whether the single file application program needs to be upgraded is judged by comparing the sizes of the cloud and the local files, and the automatic upgrading without background service is realized by downloading and replacing the local files through the cloud files. The method and the system do not need to configure background data and do not depend on the support of a background service interface, so that the problem that the background service is down and cannot be updated is avoided, and the workload of operation and maintenance is reduced; the method and the system have simple and efficient program, support the parameter transfer function, ensure that the parameters are not lost, and provide support for normal operation of the service.
Drawings
Exemplary embodiments of the present invention may be more completely understood in consideration of the following drawings:
FIG. 1 is a flowchart of a method for automatically upgrading a single file application according to an embodiment of the present invention;
FIG. 2 is a block diagram of an automatic upgrade system for single file applications according to an embodiment of the present invention.
Detailed Description
The exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, however, the present invention may be embodied in many different forms and is not limited to the examples described herein, which are provided to fully and completely disclose the present invention and fully convey the scope of the invention to those skilled in the art. The terminology used in the exemplary embodiments illustrated in the accompanying drawings is not intended to be limiting of the invention. In the drawings, like elements/components are referred to by like reference numerals.
Unless otherwise indicated, terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. In addition, it will be understood that terms defined in commonly used dictionaries should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense.
FIG. 1 is a flowchart of a method for automatically upgrading a single file application according to an embodiment of the present invention; as shown in fig. 1, the method includes:
step 110, entering a current application process, and obtaining current application process information, wherein the application process information comprises a corresponding cloud download address and the file size of a current application program;
the automatic upgrading method is a method for judging whether the application program needs to be automatically upgraded when entering a single file application program, and the starting speed of the application program is not influenced when judging that the application program does not need to be upgraded because the method is simple to operate;
when entering the current application process, the obtained cloud download address is a storage address which is pre-agreed and stores the corresponding upgrade file of the application program, and the obtained cloud download address may be different for different environments where the current application program is located, such as a test environment or a formal environment.
Step 120, detecting whether an application program named as an upgrade file exists under the address according to the cloud download address;
if the fact that the application program named as the upgrade file does not exist under the cloud download address is detected, the application is directly operated without upgrading. Only whether an application program exists or not is detected, so that the starting speed of the application program is not affected by the operation in the case that no application program directly runs.
Step 130, if an upgrade file application program exists, acquiring the file size of the upgrade file application program, comparing the file size with the file size of the current application program, and confirming whether the file sizes are consistent;
in this embodiment, whether the file is an application program to be upgraded is determined by the file name and the size of the file; the application program stored in the cloud for upgrading is named as an upgrading file, and after the upgrading is locally completed through replacement of the upgrading file, the naming of the application program needs to be modified into an original file, which is not called as the upgrading file. If the local original file is actually updated and the local original file is the same as the cloud upgrade file, the file sizes of the local original file and the cloud upgrade file are compared to determine whether the local original file and the cloud upgrade file are the same (the upgrade file is different in the original file size through a preset method during generation, and the upgrade file is described in detail later), if the file sizes are the same, the upgrade is completed, and the upgrade file is not required to be downloaded.
Step 140, if the file sizes are inconsistent, downloading the upgrade file application program;
the upgrade file application program is downloaded in a preset downloading mode; the preset downloading mode comprises a breakpoint continuous mode and a distributed downloading mode.
And step 150, replacing the current application program by using the upgrade file application program to finish upgrading.
And replacing the current application program by the application program of the upgrade file, and when the current application program is replaced, starting the application program processes corresponding to the two files, transmitting parameters and ensuring that the parameters are not lost. Specific:
starting the process of the upgrade file application program through the current application process;
copying the upgrade file application program process to cover the current application program process, and restarting the current application program process;
and deleting the upgrade file application program. Before this step of deletion is performed, there is an original file application program and an upgrade file application program locally, where the original file application program is obtained by overlaying the upgrade file application program, that is, the two file application programs are almost identical (the original file application program at this time may be summarized with more transfer parameters), so that it is equivalent to having completed the upgrade, and the upgrade file application program at this time is useless, so that the upgrade file application program is deleted.
Further, after entering the current application process, the method further includes:
confirming the name of the current application entering;
if the current application process is named as an upgrade file, detecting whether a corresponding application program named as an original file exists locally;
if so, replacing the application program named as the original file by the application program named as the upgrade file, mutually transferring parameters between the upgrade file application program process and the current application program process, and deleting redundant corresponding application programs;
if not, the application program named as the upgrade file is directly named as the original file.
Further, before entering the current application process, the method further comprises the step of generating an upgrade file application program:
generating a single file application program named as an upgrade file according to a preset rule;
comparing the single file application program named as the upgrade file with the file size of the current application program, and confirming whether the file size is consistent;
if the file sizes are consistent, adding redundant codes to the single file application program named as the upgrade file, so that the file sizes are inconsistent.
The preset rule for generating the single file application program comprises the following steps:
directly compiling to obtain a single executable file as a single file application program; or (b)
And merging the executable file, the dynamic link library, the configuration file and the resource file through a file merging tool to obtain a single executable file as a single file application program.
FIG. 2 is a block diagram of an automatic upgrade system for single file applications according to an embodiment of the present invention. As shown in fig. 2, the system shown includes:
the application process running unit 210 is configured to enter a current application process, and obtain current application process information, where the application process information includes a corresponding cloud download address and a file size of the current application program;
the file size comparison unit 220 is configured to detect whether an application program named as an upgrade file exists at the address according to the cloud download address by the file size comparison unit 220; if an upgrade file application program exists, the file size comparison unit 220 obtains the file size of the upgrade file application program, compares the file size with the file size of the current application program, and confirms whether the file sizes are consistent;
further, if the file size comparison unit 220 detects that there is no application program named as an upgrade file at the cloud download address, the application is directly run without upgrading.
A downloading unit 230, where the downloading unit 230 is configured to download the upgrade file application program when the file size comparing unit 220 compares the file sizes to be inconsistent;
further, the downloading unit 230 is configured to download the upgrade file application program in a preset downloading manner; the preset downloading mode comprises a breakpoint continuous mode and a distributed downloading mode.
And a replacing unit 240, where the replacing unit 240 is configured to replace the current application program with the upgrade file application program, so as to complete the upgrade.
Further, the replacing unit 240 is configured to start a process of the upgrade file application program through the current application process;
the replacing unit 240 is configured to copy the upgrade file application program process to cover the current application program process, restart the current application program process, and delete the upgrade file application program.
Further, the application process running unit 210 confirms the naming of the current application entered; if the current application process is named as an upgrade file, detecting whether a corresponding application program named as an original file exists locally;
if so, the replacing unit 240 replaces the application program named as the upgrade file with the application program named as the original file, and mutually transfers parameters between the upgrade file application program process and the current application program process, and deletes redundant corresponding application programs;
if not, the replacing unit 240 directly names the application named as the upgrade file as the original file.
Further, the system also comprises an upgrade file generation unit;
the upgrade file generation unit generates a single file application program named as an upgrade file according to a preset rule;
the upgrade file generation unit compares the single file application program named as the upgrade file with the file size of the current application program to confirm whether the file sizes are consistent;
if the file sizes are consistent, the upgrade file generation unit adds redundancy codes to the single file application program named as the upgrade file, so that the file sizes are inconsistent.
Further, the generating the preset rule of the single file application program includes:
directly compiling to obtain a single executable file as a single file application program; or (b)
And merging the executable file, the dynamic link library, the configuration file and the resource file through a file merging tool to obtain a single executable file as a single file application program.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the disclosure may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise. Reference to step numbers in this specification is used solely to distinguish between steps and is not intended to limit the time or logical relationship between steps, including the various possible conditions unless the context clearly indicates otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the disclosure and form different embodiments. For example, any of the embodiments claimed in the claims may be used in any combination.
Various component embodiments of the present disclosure may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. The present disclosure may also be implemented as an apparatus or system program (e.g., a computer program and a computer program product) for performing a portion or all of the methods described herein. Such a program embodying the present disclosure may be stored on a computer readable medium, or may have the form of one or more signals. Such signals may be downloaded from an internet website, provided on a carrier signal, or provided in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the disclosure, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The disclosure may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware.
The foregoing is merely a specific embodiment of the disclosure, and it should be noted that it will be apparent to those skilled in the art that several improvements, modifications, and variations can be made without departing from the spirit of the disclosure, and these improvements, modifications, and variations are to be considered within the scope of the present application.
Claims (12)
1. An automatic upgrade method for a single file application program, the method comprising:
entering a current application process to obtain current application process information, wherein the application process information comprises a corresponding cloud download address and the file size of a current application program;
detecting whether an application program named as an upgrade file exists under the address according to the cloud download address;
if the upgrade file application program exists, acquiring the file size of the upgrade file application program, comparing the file size with the file size of the current application program, and confirming whether the file size is consistent;
if the file sizes are inconsistent, downloading the upgrade file application program;
replacing the current application program with the upgrade file application program to finish upgrading; wherein said replacing the current application with the upgrade file application program comprises:
starting the process of the upgrade file application program through the current application process;
copying the upgrade file application program process to cover the current application program process, mutually transmitting parameters between the upgrade file application program process and the current application program process, and restarting the current application program process;
and deleting the upgrade file application program.
2. The method according to claim 1, characterized in that:
if the fact that the application program named as the upgrade file does not exist under the cloud download address is detected, the application is directly operated without upgrading.
3. The method according to claim 1, characterized in that: the upgrade file application program is downloaded in a preset downloading mode; the preset downloading mode comprises a breakpoint continuous mode and a distributed downloading mode.
4. The method of claim 1, wherein after entering the current application process, the method further comprises:
confirming the name of the current application entering;
if the current application process is named as an upgrade file, detecting whether a corresponding application program named as an original file exists locally;
if so, replacing the application program named as the original file by the application program named as the upgrade file, and deleting redundant corresponding application programs;
if not, the application program named as the upgrade file is directly named as the original file.
5. The method according to claim 1, characterized in that: before entering the current application process, the method further comprises:
generating a single file application program named as an upgrade file according to a preset rule;
comparing the single file application program named as the upgrade file with the file size of the current application program, and confirming whether the file size is consistent;
if the file sizes are consistent, adding redundant codes to the single file application program named as the upgrade file, so that the file sizes are inconsistent.
6. The method of claim 5, wherein generating the preset rule of the single file application named upgrade file comprises:
directly compiling to obtain a single executable file as a single file application program; or (b)
And merging the executable file, the dynamic link library, the configuration file and the resource file through a file merging tool to obtain a single executable file as a single file application program.
7. An automatic upgrade system for single file applications, said system comprising:
the application process running unit is used for entering a current application process to obtain current application process information, wherein the application process information comprises a corresponding cloud download address and the file size of a current application program;
the file size comparison unit is used for detecting whether an application program named as an upgrade file exists at the address according to the cloud download address; if the upgrade file application program exists, the file size comparison unit acquires the file size of the upgrade file application program, compares the file size with the file size of the current application program, and confirms whether the file sizes are consistent;
the downloading unit is used for downloading the upgrade file application program when the file sizes are inconsistent compared by the file size comparison unit;
the replacing unit is used for replacing the current application program by using the upgrading file application program to finish upgrading; the replacing unit is used for starting the process of the upgrade file application program through the current application process;
the replacing unit is used for copying the upgrade file application program process to cover the current application program process, mutually transmitting parameters between the upgrade file application program process and the current application program process, restarting the current application program process, and deleting the upgrade file application program.
8. The system according to claim 7, wherein: if the file size comparison unit detects that the application program named as the upgrade file does not exist at the cloud download address, the application is directly operated without upgrading.
9. The system according to claim 7, wherein: the downloading unit is used for downloading the upgrade file application program in a preset downloading mode; the preset downloading mode comprises a breakpoint continuous mode and a distributed downloading mode.
10. The system according to claim 7, wherein:
the application process running unit confirms the naming of the current application; if the current application process is named as an upgrade file, detecting whether a corresponding application program named as an original file exists locally; if so, the replacing unit replaces the application program named as the original file with the application program named as the upgrade file, and deletes redundant corresponding application programs;
if not, the replacing unit directly names the application program named as the upgrade file as an original file.
11. The system according to claim 7, wherein: the system also comprises an upgrade file generation unit;
the upgrade file generation unit generates a single file application program named as an upgrade file according to a preset rule;
the upgrade file generation unit compares the single file application program named as the upgrade file with the file size of the current application program to confirm whether the file sizes are consistent;
if the file sizes are consistent, the upgrade file generation unit adds redundancy codes to the single file application program named as the upgrade file, so that the file sizes are inconsistent.
12. The system according to claim 11, wherein: the preset rule for generating the single file application program named as the upgrade file comprises the following steps:
directly compiling to obtain a single executable file as a single file application program; or (b)
And merging the executable file, the dynamic link library, the configuration file and the resource file through a file merging tool to obtain a single executable file as a single file application program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911301640.5A CN111176676B (en) | 2019-12-17 | 2019-12-17 | Automatic upgrading method and system for single file application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911301640.5A CN111176676B (en) | 2019-12-17 | 2019-12-17 | Automatic upgrading method and system for single file application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111176676A CN111176676A (en) | 2020-05-19 |
| CN111176676B true CN111176676B (en) | 2024-02-02 |
Family
ID=70657324
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911301640.5A Active CN111176676B (en) | 2019-12-17 | 2019-12-17 | Automatic upgrading method and system for single file application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111176676B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4954941A (en) * | 1988-08-31 | 1990-09-04 | Bell Communications Research, Inc. | Method and apparatus for program updating |
| CN1132372A (en) * | 1994-12-14 | 1996-10-02 | 美国电报电话公司 | Efficient and secure update of software and data |
| US6074434A (en) * | 1996-06-07 | 2000-06-13 | International Business Machines Corporation | Selection of code updates, data updates or new data for client |
| US6684396B1 (en) * | 2000-02-16 | 2004-01-27 | Data Connection Limited | Method for upgrading running software processes without compromising fault-tolerance |
| CN106775806A (en) * | 2016-11-18 | 2017-05-31 | 国云科技股份有限公司 | A method for upgrading private cloud applications |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020073410A1 (en) * | 2000-12-13 | 2002-06-13 | Arne Lundback | Replacing software at a telecommunications platform |
| CN100464522C (en) * | 2007-05-17 | 2009-02-25 | 华为技术有限公司 | A process upgrade method and process upgrade system |
| US9244673B2 (en) * | 2012-06-08 | 2016-01-26 | Apple Inc. | System and method for updating application archive files |
-
2019
- 2019-12-17 CN CN201911301640.5A patent/CN111176676B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4954941A (en) * | 1988-08-31 | 1990-09-04 | Bell Communications Research, Inc. | Method and apparatus for program updating |
| CN1132372A (en) * | 1994-12-14 | 1996-10-02 | 美国电报电话公司 | Efficient and secure update of software and data |
| US6074434A (en) * | 1996-06-07 | 2000-06-13 | International Business Machines Corporation | Selection of code updates, data updates or new data for client |
| US6684396B1 (en) * | 2000-02-16 | 2004-01-27 | Data Connection Limited | Method for upgrading running software processes without compromising fault-tolerance |
| CN106775806A (en) * | 2016-11-18 | 2017-05-31 | 国云科技股份有限公司 | A method for upgrading private cloud applications |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111176676A (en) | 2020-05-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7934210B1 (en) | System and method for updating one or more programs and their environment | |
| US10979292B2 (en) | Adaptive deployment of applications for mobile devices | |
| US8578371B2 (en) | Software distribution method and system with automatic prerequisite installation | |
| US7937697B2 (en) | Method, system and computer program for distributing software patches | |
| US8065672B2 (en) | Simplifying rollback to prior versions of patches used to fix errors in pre-installed software | |
| KR100952251B1 (en) | A method of updating a software product by a service package, a computer-implemented method, a computer readable storage medium, and a service package | |
| US7975264B2 (en) | Deploying patches in batch mode to fix errors in pre-installed software | |
| US8291402B2 (en) | Using system fingerprints to accelerate package dependency resolution | |
| US20030023770A1 (en) | Automated software driver installation | |
| US9043781B2 (en) | Algorithm for automated enterprise deployments | |
| US8312446B2 (en) | Dependency management when upgrading application components | |
| CN102541596A (en) | Operating system upgrading method and device | |
| US20090210871A1 (en) | System and method for software application migration | |
| WO2008069431A1 (en) | Download server and method for installing and updating application program using partitioning of shared library | |
| US11301227B2 (en) | Server apparatus, information processing apparatus, and control method for installing application | |
| CN112416379B (en) | Application program installation method and device, computing equipment and readable storage medium | |
| US7966612B2 (en) | Method, system and computer program for installing shared software components | |
| US20080178173A1 (en) | Enhanced Flexibility in Deployment of Patches to Fix Errors in Pre-installed Software | |
| CN111240892A (en) | Data backup method and device | |
| US11650743B2 (en) | Updating storage drive firmware | |
| CN113377400A (en) | Software upgrading method and device, storage medium and electronic equipment | |
| CN112286543A (en) | Application service deployment method and device | |
| EP3333702A1 (en) | System and method for automatic redeployment of applications in an integrated development environment | |
| CN113721940B (en) | Software deployment method, device, electronic device and storage medium | |
| CN111176676B (en) | Automatic upgrading method and system for single file application program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |