CN111399895A - Client updating method and device, electronic equipment and computer readable medium - Google Patents
Client updating method and device, electronic equipment and computer readable medium Download PDFInfo
- Publication number
- CN111399895A CN111399895A CN202010285227.0A CN202010285227A CN111399895A CN 111399895 A CN111399895 A CN 111399895A CN 202010285227 A CN202010285227 A CN 202010285227A CN 111399895 A CN111399895 A CN 111399895A
- Authority
- CN
- China
- Prior art keywords
- file
- client
- patch
- updating
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/656—Updates while running
Abstract
The disclosure relates to a client updating method and device, electronic equipment and a computer readable medium, and belongs to the technical field of internet. The method comprises the following steps: the method comprises the steps that patch files and patch configuration files are obtained at a client, wherein the patch configuration files comprise file type information of the client files to be updated; acquiring the size of a client file from the file type information, and judging the updating mode of the client file according to the size of the file; and updating the client file according to the patch file and the updating mode of the client file. At a server side, acquiring a patch file and a patch configuration file in a patch directory, and judging whether the patch configuration file acquired this time is the same as the patch configuration file acquired last time; and if the patch file and the patch configuration file are different, sending the patch file and the patch configuration file acquired at this time to the client so as to update the client. According to the method and the device, the client is updated in different updating modes under different conditions, so that the updating is more flexible and efficient, and the network flow is saved.
Description
Technical Field
The present disclosure relates to the field of internet technologies, and in particular, to an update method for a client, an update apparatus for a client, an electronic device, and a computer-readable medium.
Background
In the process of software development, situations that a software client needs to be updated, such as problem repair, function update and the like, are often encountered. The client update is generally implemented by loading a patch file, and the patch file contains the content to be updated.
However, the existing client updating method usually needs to be restarted after exiting the software to complete the updating through the patch file, and a user needs to wait for the completion of the patch downloading process to enter the software, so that the updating efficiency is low, and the experience of the user in using the software is affected.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure is directed to a method for updating a client, an apparatus for updating a client, an electronic device, and a computer-readable medium, so as to improve the updating efficiency of the client and improve the software using experience of a user.
According to a first aspect of the present disclosure, there is provided an update method of a client, including:
acquiring a patch file and a corresponding patch configuration file from a server side, wherein the patch configuration file comprises file type information of a client file to be updated;
acquiring the file size of the client file from the file type information, and judging the updating mode of the client file according to the file size of the client file;
and updating the client file according to the patch file and the updating mode of the client file.
In an exemplary embodiment of the present disclosure, the determining, according to the file size of the client file, an update mode of the client file includes:
if the file size of the client file is smaller than or equal to a file size threshold value, updating the client file in a file replacement mode;
and if the file size of the client file is larger than the file size threshold, updating the client file in a file repair mode.
In an exemplary embodiment of the present disclosure, the updating the client file according to the patch file and the update mode of the client file includes:
if the client file is updated in a file replacement mode, acquiring a file replacement path in the patch configuration file, wherein the file replacement path is a storage path corresponding to an original file to be replaced in the client file;
and replacing the original file to be replaced in the client file with the patch file according to the file replacement path so as to complete the update of the client file.
In an exemplary embodiment of the present disclosure, the updating the client file according to the patch file and the update mode of the client file includes:
and if the client file is updated in a file repair mode, running the patch file at the client to complete the update of the client file, wherein the patch file is a logic code file for modifying the client file.
According to a second aspect of the present disclosure, there is provided an update method of a client, including:
acquiring a patch file and a corresponding patch configuration file in a patch directory, and judging whether the patch configuration file acquired this time is the same as the patch configuration file acquired last time;
and if the patch configuration file acquired this time is different from the patch configuration file acquired last time, transmitting the patch file acquired this time and the patch configuration file to a client so that the client updates according to the patch file and the patch configuration file.
In an exemplary embodiment of the present disclosure, the acquiring a patch file and a corresponding patch configuration file in a patch directory, and determining whether the patch configuration file acquired this time is the same as the patch configuration file acquired last time includes:
acquiring patch files and corresponding patch configuration files in a patch directory according to a preset time interval;
and judging whether the modification time of the patch configuration file acquired this time is the same as the modification time of the patch configuration file acquired last time.
In an exemplary embodiment of the present disclosure, the sending the patch file and the patch configuration file acquired this time to a client includes:
acquiring a client list corresponding to the server, and judging the online state of each client in the client list;
if the client is in an online state, sending the patch file and the patch configuration file acquired at this time to the client;
and if the client is in an offline state, when the client is changed from the offline state to the online state, sending the patch file and the patch configuration file acquired at this time to the client.
According to a third aspect of the present disclosure, there is provided an update apparatus of a client, including:
the patch file acquisition module is used for acquiring a patch file and a corresponding patch configuration file from a server side, wherein the patch configuration file comprises file type information of a client file to be updated;
the updating mode judging module is used for acquiring the file size of the client file from the file type information and judging the updating mode of the client file according to the file size of the client file;
and the client file updating module is used for updating the client file according to the patch file and the updating mode of the client file.
According to a fourth aspect of the present disclosure, there is provided an update apparatus of a client, including:
the patch file judging module is used for acquiring a patch file and a corresponding patch configuration file in a patch directory and judging whether the patch configuration file acquired this time is the same as the patch configuration file acquired last time;
and the patch file sending module is used for sending the patch file and the patch configuration file acquired this time to the client if the patch configuration file acquired this time is different from the patch configuration file acquired last time, so that the client can update according to the patch file and the patch configuration file.
According to a fifth aspect of the present disclosure, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the client update method of any one of the above via execution of the executable instructions.
According to a sixth aspect of the present disclosure, there is provided a computer readable medium, on which a computer program is stored, which computer program, when executed by a processor, implements the update method of the client described in any one of the above.
The exemplary embodiments of the present disclosure may have the following advantageous effects:
in the client updating method according to the exemplary embodiment of the present disclosure, the server synchronously sends the dynamic patch file to the client, so that the client performs online updating based on the received patch file, and different updating modes can be automatically selected according to client files of different sizes. On one hand, the client can complete the updating on line without logging out and logging in again during updating, and the client does not need to display the process of downloading the patch file, so that the user can not perceive the whole updating process of the client, and the use experience of the user is greatly improved; on the other hand, different updating schemes are used for client files with different sizes, so that the consumption of network flow can be reduced, and the updating process of the client is more flexible and efficient.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
FIG. 1 schematically illustrates a schematic diagram of a client update interface, according to a particular embodiment of the present disclosure;
FIG. 2 shows a flow diagram of an update method applied to a client on a client according to an example embodiment of the present disclosure;
FIG. 3 is a flowchart illustrating a method for determining a client file update according to an exemplary embodiment of the disclosure;
FIG. 4 shows a flowchart of an update by file replacement according to an example embodiment of the present disclosure;
fig. 5 shows a flowchart of an update method applied to a client on a server side according to an example embodiment of the present disclosure;
fig. 6 illustrates a flowchart illustrating a process of determining whether a patch configuration file acquired this time is the same as that acquired last time according to an example embodiment of the present disclosure;
FIG. 7 illustrates a flowchart of sending a patch file according to an example embodiment of the present disclosure;
FIG. 8 shows a block diagram of an update apparatus applied to a client on a client according to an example embodiment of the present disclosure;
FIG. 9 shows a block diagram of an update apparatus applied to a client on a server side according to an example embodiment of the present disclosure;
FIG. 10 illustrates a schematic structural diagram of a computer system suitable for use in implementing an electronic device of an embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
In some related embodiments, the update scheme of the client is that when software is started, a patch server is accessed, the local resource version of the client is compared with the version number on the server, if the local resource version of the client is different from the version number on the server, the client indicates that a new version needs to be updated, the client downloads a patch file needing to be updated according to the version difference and stores the patch file into a local corresponding directory, and the patch file contains content needing to be updated. Taking a game client as an example, a schematic diagram of an update interface is shown in fig. 1, after a user opens a game, an update dialog box 102 of the game client is displayed on a game starting interface 101, and a loading progress bar 103 is displayed below the interface, where relevant information of the current client update, including the size of a patch file, is displayed on the update dialog box 102.
Although the above embodiments can normally update the client to repair the bug (bug) of the client or update the function of the client, in these embodiments, the patch file is usually downloaded by actively requesting the client to be downloaded when the client is started, and this scheme requires the client to quit the restart to trigger and update, and cannot achieve real-time online update, and users have obvious perception in the downloading process of the patch file, and when there are many bugs on the client, if the users frequently quit downloading the patch again, the use experience of the users will be influenced.
In view of the above problems, the present exemplary embodiment provides an update method for a client, which can implement real-time online update of the client and improve update efficiency of the client.
The present exemplary embodiment first provides an update method for a client, which is applied to the client. Referring to fig. 2, the update method of the client may include the following steps:
step S210, a patch file and a corresponding patch configuration file are obtained from a server side, wherein the patch configuration file comprises file type information of a client file to be updated.
The patch file refers to a small program for solving problems issued for problems exposed in the using process of some software systems, and taking game software as an example, the patch file can be used for repairing bugs appearing in the running process of game clients or updating new functions or new playing methods of games. The patch configuration file includes configuration information of the corresponding patch file, including file type information of a client file to be updated of the patch file.
If the server side finds that the content in the patch configuration file is modified, the server side actively pushes the patch file and the patch configuration file to the client side, the client side receives the patch file and the patch configuration file pushed by the server side, codes in the patch file are executed in the current memory environment, the effect of dynamically repairing bugs or updating functions is achieved, and therefore subsequent updating operation is completed. Because the content in the patch file is generally very small, the whole pushing process is not aware of the user and can be completely transparent.
And S220, acquiring the file size of the client file from the file type information, and judging the updating mode of the client file according to the file size of the client file.
In the embodiment of the present invention, different update methods can be adopted for updating client files of different sizes, and by using this method, the consumption of network traffic can be reduced, and the update process of the client is more flexible and efficient. After receiving a patch file and a patch configuration file required by updating from a server, a client acquires the file size of a client file from file type information of the client file to be updated in the patch configuration file, and determines a suitable client updating mode according to the file size of the client file.
And step S230, updating the client file according to the patch file and the updating mode of the client file.
After determining a suitable client updating mode according to the file size of the client file, the client can update according to the patch file and the updating mode of the client file, for example, the client can execute codes in the patch file in the current memory environment to achieve the effect of dynamically repairing bugs or updating functions.
In the client updating method according to the exemplary embodiment of the present disclosure, the server synchronously sends the dynamic patch file to the client, so that the client performs online updating based on the received patch file, and different updating modes can be automatically selected according to client files of different sizes. On one hand, the client can complete the updating on line without logging out and logging in again during updating, and the client does not need to display the process of downloading the patch file, so that the user can not perceive the whole updating process of the client, and the use experience of the user is greatly improved; on the other hand, different updating schemes are used for client files with different sizes, so that the consumption of network flow can be reduced, and the updating process of the client is more flexible and efficient.
The above steps of the present exemplary embodiment will be described in more detail with reference to fig. 3 to 5.
In step S220, as shown in fig. 3, the determining the update mode of the client file according to the file size of the client file may specifically include the following steps:
and S310, if the file size of the client file is smaller than or equal to the file size threshold, updating the client file in a file replacement mode.
And if the file size of the client file is smaller than or equal to the file size threshold, the client file is a small file. For updating of small files, the update mode of file replacement is used in the present exemplary embodiment, that is, only the wrong place of the client file needs to be modified correctly in the patch file, and then the patch file is sent to the client and the corresponding part is replaced.
Step S320, if the file size of the client file is larger than the file size threshold, updating the client file in a file repair mode.
And if the file size of the client file is larger than the file size threshold, the client file is a large file. For updating a large file, in order to save traffic, the exemplary embodiment uses an updating manner of file repair, that is, a section of logic code is executed to repair a place where an error occurs in a file of a client.
If the client file is updated in a file replacement manner, that is, the client file is a small file, in step S230, as shown in fig. 4, the client file is updated according to the patch file and the update manner of the client file, which may specifically include the following steps:
and S410, if the client file is updated in a file replacement mode, acquiring a file replacement path in the patch configuration file, wherein the file replacement path is a storage path corresponding to an original file to be replaced in the client file.
In this exemplary embodiment, in repairing a small file, the patch configuration file further includes a file replacement path to be replaced by the patch file, for example, if the client file to be replaced by the patch file is a certain original module, the file replacement path included in the patch configuration file is a module storage path of the original module.
And S420, replacing the original file to be replaced in the client file with the patch file according to the file replacement path so as to complete the update of the client file.
The file replacement path can enable the client to determine the specific storage path of the part to be modified of the update, and according to the file replacement path, the client can replace the original file to be replaced in the client file with the patch file. The content in the patch file is the content obtained by modifying the wrong part in the client file to be replaced correctly, so that the client file can be repaired and updated by replacing the patch file.
For example, if a certain client file is a small file with only tens of lines of codes, and a certain word has a misspelling, the misspelling word is modified correctly in the patch file, and then the original client file is replaced, so that the client can be updated.
If the client file is updated in a file repair manner, that is, the client file is a large file, in step S230, the client file is updated according to the patch file and the update manner of the client file, and the client file is updated by running the patch file on the client, where the patch file is a logic code file for modifying the client file.
For updating a large file, if the above method of directly replacing an original file is used, a large amount of network traffic is wasted, and therefore, in the present exemplary embodiment, the large file is updated by using a file repair method.
When the client file is a large file, the patch file is a logic code file, and the logic code file is operated at the client to correct the error position in the client file, so that the client is updated. For example, a certain client file is a large file containing thousands of rows of data, wherein one data is wrong, the wrong place in the large file is modified correctly by writing a logic code, and then the logic code file is sent to the client without resending the whole large file, and the client can complete the updating of the client by executing the logic code file to modify the wrong data in the memory space.
The embodiment of the example also provides an updating method of the client, which is applied to the server. Referring to fig. 5, the update method of the client may include the following steps:
step 510, obtaining the patch file and the corresponding patch configuration file in the patch directory, and judging whether the obtained patch configuration file is the same as the last obtained patch configuration file.
In this exemplary embodiment, the server has a special patch directory for storing patch files and patch configuration files to be sent to the client. Generally, one patch file can repair a problem online, and a server side can simultaneously transmit a plurality of patch files to update and repair a plurality of client files.
The server side obtains the patch file and the patch configuration file in the patch directory, and judges whether the patch configuration file obtained this time is the same as the patch configuration file obtained last time, namely whether the patch configuration file is modified, if not, it indicates that no client side file needing to be updated exists temporarily.
And S520, if the patch configuration file acquired this time is different from the patch configuration file acquired last time, transmitting the patch file and the patch configuration file acquired this time to the client so that the client can update according to the patch file and the patch configuration file.
If the patch configuration file acquired this time is different from the patch configuration file acquired last time, the server side actively pushes the patch file and the patch configuration file to the client side, and then the client side executes the corresponding steps of the client side according to the patch file and the patch configuration file so as to complete the updating of the client side file.
In step S510, as shown in fig. 6, acquiring a patch file and a corresponding patch configuration file in a patch directory, and determining whether the patch configuration file acquired this time is the same as the patch configuration file acquired last time, which may specifically include the following steps:
step S610, obtaining the patch files in the patch catalog and the corresponding patch configuration files according to a preset time interval.
And S620, judging whether the modification time of the patch configuration file acquired this time is the same as the modification time of the patch configuration file acquired last time.
In this exemplary embodiment, whether the patch configuration file acquired this time is the same as the patch configuration file acquired last time may be determined by determining whether the modification time of the patch configuration file has changed. For example, the server side acquires the patch file and the corresponding patch configuration file every 1 minute or every 2 minutes, and records the modification time of the patch configuration file at each acquisition, and if the modification time of the patch configuration file acquired this time is different from the modification time of the patch configuration file acquired last time, it indicates that the patch configuration file acquired this time is modified, and the server side sends the patch configuration file to the client side for updating. By setting the acquired preset time interval, the server can dynamically acquire the updating information on line, and the timeliness of the updating of the client is ensured. Whether the patch configuration file is modified or not is judged not only by the modification time, but also by some other methods, which is not limited in this example embodiment.
In step S520, as shown in fig. 7, sending the patch file and the patch configuration file acquired this time to the client, specifically, the following steps may be included:
and S710, acquiring a client list corresponding to the server, and judging the online state of each client in the client list.
After the server side obtains the patch file and the patch configuration file, the server side traverses the corresponding client side list, judges the online state of each client side, and selects different sending modes according to different client side states.
And S720, if the client is in an online state, sending the patch file and the patch configuration file acquired this time to the client.
If the client is in an online state, the server side can directly send the patch file and the patch configuration file acquired this time to the client, so that the client performs online updating.
Step 730, if the client is in the offline state, when the client is changed from the offline state to the online state, the patch file and the patch configuration file acquired this time are sent to the client.
If the client is in an off-line state, when a user logs in the client, the client is changed from the off-line state to an on-line state, and the server sends the patch file and the patch configuration file acquired this time to the client, so that the user can receive the patch file sent by the server every time the user enters the client, and the update of the client is completed.
It should be noted that although the various steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that these steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Furthermore, the disclosure also provides an updating device of the client. Referring to fig. 8, the client update apparatus may include a patch file obtaining module 810, an update mode determining module 820, and a client file updating module 830. Wherein:
the patch file obtaining module 810 may be configured to obtain a patch file and a corresponding patch configuration file from a server, where the patch configuration file includes file type information of a client file to be updated;
the update mode determining module 820 may be configured to obtain a file size of the client file from the file type information, and determine an update mode of the client file according to the file size of the client file;
the client file updating module 830 may be configured to update the client file according to the patch file and the update mode of the client file.
In some exemplary embodiments of the present disclosure, the update mode determination module 820 may include a file replacement update unit and a file repair update unit. Wherein:
the file replacement updating unit may be configured to update the client file in a file replacement manner if the file size of the client file is smaller than or equal to the file size threshold;
the file repair update unit may be configured to update the client file in a file repair manner if the file size of the client file is greater than the file size threshold.
In some exemplary embodiments of the present disclosure, the client file updating module 830 may include a replacement path acquiring unit and a patch file replacing unit. Wherein:
the replacement path obtaining unit may be configured to obtain a file replacement path in the patch configuration file if the client file is updated in a file replacement manner, where the file replacement path is a storage path corresponding to an original file to be replaced in the client file;
the patch file replacing unit may be configured to replace an original file to be replaced in the client file with the patch file according to the file replacement path, so as to complete updating of the client file.
In some exemplary embodiments of the present disclosure, the client file updating module 830 may further include a patch file running unit, and may be configured to run the patch file on the client to complete updating of the client file if the client file is updated in a file repair manner, where the patch file is a logic code file that modifies the client file.
Furthermore, the disclosure also provides an updating device of the client. Referring to fig. 9, the updating apparatus of the client may include a patch file determining module 910 and a patch file transmitting module 920. Wherein:
the patch file determining module 910 may be configured to obtain a patch file and a corresponding patch configuration file in a patch directory, and determine whether the obtained patch configuration file is the same as the patch configuration file obtained last time;
the patch file sending module 920 may be configured to send the patch file and the patch configuration file obtained this time to the client if the patch configuration file obtained this time is different from the patch configuration file obtained last time, so that the client performs updating according to the patch file and the patch configuration file.
In some exemplary embodiments of the present disclosure, the patch file determining module 910 may include a patch file obtaining unit and a modification time determining unit. Wherein:
the patch file acquiring unit may be configured to acquire a patch file and a corresponding patch configuration file in a patch directory according to a preset time interval;
the modification time judgment unit may be configured to judge whether the modification time of the patch configuration file acquired this time is the same as the modification time of the patch configuration file acquired last time.
In some exemplary embodiments of the present disclosure, the patch file transmitting module 920 may include an online status determining unit, an online transmitting unit, and an offline transmitting unit. Wherein:
the online state judging unit may be configured to obtain a client list corresponding to the server, and judge an online state of each client in the client list;
the online sending unit may be configured to send the patch file and the patch configuration file acquired this time to the client if the client is in an online state;
the offline sending unit may be configured to send the patch file and the patch configuration file acquired this time to the client when the client is in an offline state and the client is changed from the offline state to an online state.
The details of each module/unit in the updating apparatus of the client are already described in detail in the corresponding method embodiment section, and are not described herein again.
FIG. 10 illustrates a schematic structural diagram of a computer system suitable for use with the electronic device to implement an embodiment of the invention.
It should be noted that the computer system 1000 of the electronic device shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of the application of the embodiment of the present invention.
As shown in fig. 10, the computer system 1000 includes a Central Processing Unit (CPU)1001 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1002 or a program loaded from a storage section 1008 into a Random Access Memory (RAM) 1003. In the RAM 1003, various programs and data necessary for system operation are also stored. The CPU1001, ROM 1002, and RAM 1003 are connected to each other via a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.
To the I/O interface 1005, AN input section 1006 including a keyboard, a mouse, and the like, AN output section 1007 including a terminal such as a Cathode Ray Tube (CRT), a liquid crystal display (L CD), and the like, a speaker, and the like, a storage section 1008 including a hard disk, and the like, and a communication section 1009 including a network interface card such as a L AN card, a modem, and the like, the communication section 1009 performs communication processing via a network such as the internet, a drive 1010 is also connected to the I/O interface 1005 as necessary, a removable medium 1011 such as a magnetic disk, AN optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 1010 as necessary, so that a computer program read out therefrom is mounted into the storage section 1008 as necessary.
In particular, according to an embodiment of the present invention, the processes described below with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication part 1009 and/or installed from the removable medium 1011. When the computer program is executed by a Central Processing Unit (CPU)1001, various functions defined in the system of the present application are executed.
It should be noted that the computer readable media shown in the present disclosure may be computer readable signal media or computer readable storage media or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer-readable signal medium may include a propagated data signal with computer-readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the method as described in the embodiments below.
It should be noted that although in the above detailed description several modules of the device for action execution are mentioned, this division is not mandatory. Indeed, the features and functionality of two or more of the modules described above may be embodied in one module, in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module described above may be further divided into embodiments by a plurality of modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (11)
1. A client updating method is applied to a client, and is characterized by comprising the following steps:
acquiring a patch file and a corresponding patch configuration file from a server side, wherein the patch configuration file comprises file type information of a client file to be updated;
acquiring the file size of the client file from the file type information, and judging the updating mode of the client file according to the file size of the client file;
and updating the client file according to the patch file and the updating mode of the client file.
2. The method according to claim 1, wherein the determining an update mode of the client file according to the file size of the client file comprises:
if the file size of the client file is smaller than or equal to a file size threshold value, updating the client file in a file replacement mode;
and if the file size of the client file is larger than the file size threshold, updating the client file in a file repair mode.
3. The client update method according to claim 2, wherein updating the client file according to the patch file and the update method of the client file includes:
if the client file is updated in a file replacement mode, acquiring a file replacement path in the patch configuration file, wherein the file replacement path is a storage path corresponding to an original file to be replaced in the client file;
and replacing the original file to be replaced in the client file with the patch file according to the file replacement path so as to complete the update of the client file.
4. The client update method according to claim 2, wherein updating the client file according to the patch file and the update method of the client file includes:
and if the client file is updated in a file repair mode, running the patch file at the client to complete the update of the client file, wherein the patch file is a logic code file for modifying the client file.
5. A client-side updating method is applied to a server side, and is characterized by comprising the following steps:
acquiring a patch file and a corresponding patch configuration file in a patch directory, and judging whether the patch configuration file acquired this time is the same as the patch configuration file acquired last time;
and if the patch configuration file acquired this time is different from the patch configuration file acquired last time, transmitting the patch file acquired this time and the patch configuration file to a client so that the client updates according to the patch file and the patch configuration file.
6. The client updating method according to claim 5, wherein the obtaining a patch file and a corresponding patch configuration file in a patch directory and determining whether the obtained patch configuration file is the same as a patch configuration file obtained last time includes:
acquiring patch files and corresponding patch configuration files in a patch directory according to a preset time interval;
and judging whether the modification time of the patch configuration file acquired this time is the same as the modification time of the patch configuration file acquired last time.
7. The client updating method according to claim 5, wherein the sending the patch file and the patch configuration file acquired this time to the client includes:
acquiring a client list corresponding to the server, and judging the online state of each client in the client list;
if the client is in an online state, sending the patch file and the patch configuration file acquired at this time to the client;
and if the client is in an offline state, when the client is changed from the offline state to the online state, sending the patch file and the patch configuration file acquired at this time to the client.
8. An updating apparatus of a client, comprising:
the patch file acquisition module is used for acquiring a patch file and a corresponding patch configuration file from a server side, wherein the patch configuration file comprises file type information of a client file to be updated;
the updating mode judging module is used for acquiring the file size of the client file from the file type information and judging the updating mode of the client file according to the file size of the client file;
and the client file updating module is used for updating the client file according to the patch file and the updating mode of the client file.
9. An updating apparatus of a client, comprising:
the patch file judging module is used for acquiring a patch file and a corresponding patch configuration file in a patch directory and judging whether the patch configuration file acquired this time is the same as the patch configuration file acquired last time;
and the patch file sending module is used for sending the patch file and the patch configuration file acquired this time to the client if the patch configuration file acquired this time is different from the patch configuration file acquired last time, so that the client can update according to the patch file and the patch configuration file.
10. An electronic device, comprising:
a processor; and
memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the update method of the client as claimed in any one of claims 1 to 7.
11. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out an updating method for a client according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010285227.0A CN111399895A (en) | 2020-04-13 | 2020-04-13 | Client updating method and device, electronic equipment and computer readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010285227.0A CN111399895A (en) | 2020-04-13 | 2020-04-13 | Client updating method and device, electronic equipment and computer readable medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111399895A true CN111399895A (en) | 2020-07-10 |
Family
ID=71431627
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010285227.0A Pending CN111399895A (en) | 2020-04-13 | 2020-04-13 | Client updating method and device, electronic equipment and computer readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111399895A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111858524A (en) * | 2020-07-27 | 2020-10-30 | 北京百川盈孚科技有限公司 | Data synchronization method and device |
| CN111913730A (en) * | 2020-07-15 | 2020-11-10 | 上海莉莉丝科技股份有限公司 | User-insensitive application program internal updating method, user side and program server |
| CN112657196A (en) * | 2020-12-21 | 2021-04-16 | 北京像素软件科技股份有限公司 | Resource updating method and device, computer equipment and readable storage medium |
| CN113779939A (en) * | 2021-09-14 | 2021-12-10 | 成都海光核电技术服务有限公司 | Generation method and use method of document hot patch and document hot patch device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090193407A1 (en) * | 2008-01-29 | 2009-07-30 | Viasat, Inc. | Methods and Systems for Automatic Patch Creation for Client Updates |
| CN104539696A (en) * | 2014-12-26 | 2015-04-22 | 北京像素软件科技股份有限公司 | Client end incremental updating method and system |
| CN105320554A (en) * | 2015-12-11 | 2016-02-10 | 网易（杭州）网络有限公司 | Program updating method as well as client and system for program updating |
| CN107239309A (en) * | 2017-06-06 | 2017-10-10 | 网易（杭州）网络有限公司 | Patch generation method and device, update method, electronic equipment, storage medium |
-
2020
- 2020-04-13 CN CN202010285227.0A patent/CN111399895A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090193407A1 (en) * | 2008-01-29 | 2009-07-30 | Viasat, Inc. | Methods and Systems for Automatic Patch Creation for Client Updates |
| CN104539696A (en) * | 2014-12-26 | 2015-04-22 | 北京像素软件科技股份有限公司 | Client end incremental updating method and system |
| CN105320554A (en) * | 2015-12-11 | 2016-02-10 | 网易（杭州）网络有限公司 | Program updating method as well as client and system for program updating |
| CN107239309A (en) * | 2017-06-06 | 2017-10-10 | 网易（杭州）网络有限公司 | Patch generation method and device, update method, electronic equipment, storage medium |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111913730A (en) * | 2020-07-15 | 2020-11-10 | 上海莉莉丝科技股份有限公司 | User-insensitive application program internal updating method, user side and program server |
| CN111858524A (en) * | 2020-07-27 | 2020-10-30 | 北京百川盈孚科技有限公司 | Data synchronization method and device |
| CN112657196A (en) * | 2020-12-21 | 2021-04-16 | 北京像素软件科技股份有限公司 | Resource updating method and device, computer equipment and readable storage medium |
| CN113779939A (en) * | 2021-09-14 | 2021-12-10 | 成都海光核电技术服务有限公司 | Generation method and use method of document hot patch and document hot patch device |
| CN113779939B (en) * | 2021-09-14 | 2024-02-27 | 成都海光核电技术服务有限公司 | Document hot patch generation method, document hot patch application method and document hot patch Ding Zhuangzhi |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111399895A (en) | Client updating method and device, electronic equipment and computer readable medium | |
| CN106572173B (en) | Configuration information updating method, device and system | |
| CN104317914A (en) | Data acquiring method and device | |
| CN110730090B (en) | Batch updating method, device, medium and electronic equipment for agent terminals in cloud environment | |
| CN110324185B (en) | Hyper-parameter tuning method, device, server, client and medium | |
| CN112631919A (en) | Comparison test method and device, computer equipment and storage medium | |
| CN109299124B (en) | Method and apparatus for updating a model | |
| CN109873731B (en) | Test method, device and system | |
| CN111800511B (en) | Synchronous login state processing method, system, equipment and readable storage medium | |
| CN112738550B (en) | Content data processing method and device, electronic equipment and medium | |
| CN113204425B (en) | Method, device, electronic equipment and storage medium for process management internal thread | |
| CN115033261A (en) | Program updating method, device, equipment and storage medium | |
| CN113377385A (en) | Client automatic deployment method and device | |
| CN111176718A (en) | Script online method and device, storage medium and electronic equipment | |
| CN111324374A (en) | Application program registration method and device based on application performance management system | |
| CN116089187B (en) | GPU test system, electronic equipment and storage medium | |
| CN116028245B (en) | Service message processing method and device based on message middleware | |
| CN110888665B (en) | Method, device, equipment and storage medium for submitting changed content | |
| CN115167769A (en) | Method, device and system for writing data | |
| CN117407011A (en) | Webpage application updating method and device, storage medium and electronic equipment | |
| CN117492788A (en) | Chip program upgrading method, device, electronic equipment and computer readable medium | |
| CN111596966A (en) | Sub-application loading method and device | |
| CN114756336A (en) | Distributed timing task execution method, device, equipment and medium | |
| CN116796098A (en) | Webpage style display method, device, equipment, system and medium | |
| CN113419966A (en) | Pressure measurement method and device based on Jmeter thread |
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 |