CN110554963B - Application rollback method, device and storage medium - Google Patents
Application rollback method, device and storage medium Download PDFInfo
- Publication number
- CN110554963B CN110554963B CN201910790766.7A CN201910790766A CN110554963B CN 110554963 B CN110554963 B CN 110554963B CN 201910790766 A CN201910790766 A CN 201910790766A CN 110554963 B CN110554963 B CN 110554963B
- Authority
- CN
- China
- Prior art keywords
- target
- version number
- rollback
- unique identifier
- network address
- 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; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application rollback method and device and storage medium are provided, wherein a development client sends an application rollback request to a server, and the server generates a JavaScript resource version number list of a corresponding target application program. The user client sends a request to the server to inquire the server about the version number of the real Native of the currently accessed function module. The server sends a request response to the user client, the user client determines a corresponding JavaScript resource according to the target rollback version number of the real function module currently accessed by the user in the request response, and the currently accessed function module is rendered by using the JavaScript resource. Therefore, the technical scheme provided by the application can effectively reduce the corresponding steps of the rollback operation, further reduce the misoperation and save the rollback time.
Description
Technical Field
The application relates to the technical field of App development, in particular to an application rollback method, an application rollback device and a storage medium.
Background
The development of the mobile application depends on the reactivative (cross-platform mobile application development framework, RN), the reactivative is written by using a JavaScript programming language, and in order to perfect the service performance of the mobile application, the reactivative is continuously updated, and each update of the reactivative corresponds to one JavaScript resource version, or, in other words, each update of the mobile application corresponds to one JavaScript resource version. Because the JavaScript resource has the characteristic of dynamic issuing, correspondingly, the reactivative also has the performance of dynamic updating, so that the updating efficiency of the mobile application can be improved.
In the updating process of the mobile application, the JavaScript resource may issue some versions with bug, and the bug may cause problems of flashing back, blocking, and the like of the mobile application in running, even make the mobile application inaccessible, and affect the user experience. At this time, repair is required for these bugs to bring the mobile application back into normal use. In order not to affect the current use of the user, an application rollback method is generally adopted, namely, firstly, the JavaScript resource used by the mobile application is restored to a used correct version, then the JavaScript resource with the bug is repaired, and after the JavaScript resource is repaired, the mobile application is enabled to use the repaired JavaScript resource. Specifically, in the process of application rollback, the used JavaScript resource with the correct version needs to be repackaged, and is synchronized to the testing environment, the sandbox environment and the online environment one by one to finish online, so as to be used by the mobile application for rollback.
According to the technology, in the process of rolling back the application, a large amount of time is consumed in the process of packaging the used JavaScript resources of the correct version, and meanwhile, the packaged resources need to be online through a triple test environment, so that the online process takes a long time.
Disclosure of Invention
The application rollback method, device and storage medium are provided to solve the problem that the existing application rollback method consumes long time.
In a first aspect, an embodiment of the present application provides an application rollback method, applied to a server, including:
receiving an application rollback request sent by a development client, wherein the application rollback request comprises a unique identifier and a rollback version number of the reactionary of all functional modules of a target application program, and the unique identifier corresponds to the rollback version number;
generating a JavaScript resource version number list of the target application program according to the unique identifier and the rollback version number of the reactive of the functional module, wherein the JavaScript resource version number list comprises the unique identifier and the rollback version number of the reactive of each functional module of the target application program;
receiving a sending request sent by a user client, wherein the sending request comprises a target unique identifier of a functional module which is currently accessed by a user and is received by the user client;
and responding to the issuing request, and sending a target rollback version number corresponding to the target unique identifier to the user client so that the user client uses the JavaScript resource which is determined to correspond to the target rollback version number to render the function module which is currently accessed by the user.
In an implementation manner of the first aspect of the embodiments of the present application, the sending, by the user client, the target rollback version number corresponding to the target unique identifier includes:
acquiring a target rollback version number corresponding to the target unique identifier from a JavaScript resource version number list of the target application program according to the unique identifier matched with the target unique identifier, wherein the target rollback version number is a rollback version number of a reactive of a function module currently accessed by the user;
and sending the target rollback version number to the user client.
In an implementation manner of the first aspect of the embodiment of the present application, after the sending, in response to the issuing request, the target rollback version number corresponding to the target unique identifier to the user client includes:
when the local JavaScript resource corresponding to the target rollback version number does not exist in the user client, receiving a content distribution network address request sent by the user client, wherein the content distribution network address request comprises platform parameters of the user client, a target unique identifier of a reactive function module currently accessed by the user and a target unique identifier and a target rollback version number of the target rollback version number, which do not correspond to the local JavaScript resource;
Generating a content distribution network address request response according to the platform parameters of the user client, the target unique identifier of the non-corresponding local JavaScript resource and the target rollback version number, wherein the content distribution network address request response comprises a target content distribution network address required by the reactionary of a functional module corresponding to the target unique identifier of the non-corresponding local JavaScript resource and the target rollback version number;
and sending the content distribution network address request response to the user client so that the user client can acquire JavaScript resources by using the target content distribution network address.
In an implementation manner of the first aspect of the embodiment of the present application, the generating, according to a platform parameter of the user client, a target unique identifier of the local JavaScript resource without correspondence, and a target rollback version number, the content distribution network address request response includes:
determining a corresponding content distribution network address in a history JavaScript resource version list stored in the server according to the target unique identifier and the target rollback version number of the non-corresponding local JavaScript resource, wherein the history JavaScript resource version list comprises an online unique identifier, an online version number and an online content distribution network address of a reactive of all functional modules of a target application program, and the online content distribution network address corresponds to the online version number;
And determining a target content distribution network address matched with the platform parameters in the content distribution network addresses.
In an implementation manner of the first aspect of the embodiment of the present application, the method further includes:
and after the JavaScript resource version number list is generated, a rollback completion instruction is sent to the development client.
In a second aspect, an embodiment of the present application provides an application rollback method, applied to a user client, where the method includes:
sending a sending request to a server, wherein the sending request comprises a target unique identifier of a functional module which is currently accessed by a user and is received on a user client;
receiving a request response sent by the server, wherein the request response comprises a target rollback version number corresponding to the target unique identifier;
determining corresponding JavaScript resources according to the target rollback version number;
and rendering the function module currently accessed by the user by using the JavaScript resource.
In an implementation manner of the second aspect of the embodiment of the present application, the determining, according to the target rollback version number, a corresponding JavaScript resource includes:
judging whether a standby version number matched with the target rollback version number exists in the version numbers corresponding to the local JavaScript resources;
If yes, the user client determines a corresponding local JavaScript resource according to the standby version number, so that the user client uses the local JavaScript resource to render the function module currently accessed by the user.
In an implementation manner of the second aspect of the embodiments of the present application, the method further includes:
if not, a content distribution network address request is sent to the server, wherein the content distribution network address request comprises platform parameters of the user client, a target unique identifier of a reactive function module currently accessed by the user, and a target unique identifier and a target rollback version number of a non-corresponding local JavaScript resource in the target unique identifier and the target rollback version number of the functional module currently accessed by the user;
and receiving a content distribution network address request response sent by the server, wherein the content distribution network address request response comprises a target content distribution network address required by a real Native of a functional module corresponding to the target rollback version number without the corresponding local JavaScript resource, so that the user client can acquire the JavaScript resource by using the target content distribution network address, and render the functional module currently accessed by the user by using the JavaScript resource.
In an implementation manner of the second aspect of the embodiments of the present application, the method further includes:
and storing the target content distribution network address to a local database.
In a third aspect, an embodiment of the present application provides an application rollback apparatus, applied to a server, where the apparatus includes: a transmitter, a receiver, and a processor;
the transmitter is configured to receive an application rollback request sent by a development client, where the application rollback request includes a unique identifier of reactive of all functional modules of a target application program and a rollback version number, and the unique identifier corresponds to the rollback version number;
the processor is configured to generate a JavaScript resource version number list of the target application according to the unique identifier and the rollback version number of the reactive of the functional module, where the JavaScript resource version number list includes the unique identifier and the rollback version number of the reactive of each functional module of the target application;
the receiver is used for receiving a sending request sent by a user client, wherein the sending request comprises a target unique identifier of a functional module which is currently accessed by a user and is received on the user client;
And the transmitter is further used for responding to the issuing request and transmitting a target rollback version number corresponding to the target unique identifier to the user client so that the user client uses the function module which determines the corresponding JavaScript resource according to the target rollback version number to render the current access of the user.
In one possible implementation manner of the third aspect of the embodiments of the present application,
the processor is specifically configured to obtain, from a JavaScript resource version number list of the target application program, a target rollback version number corresponding to the target unique identifier according to a unique identifier that matches the target unique identifier, where the target rollback version number is a rollback version number of a reactive of a function module currently accessed by the user;
the transmitter is specifically configured to send the target rollback version number to the user client.
In one possible implementation manner of the third aspect of the embodiments of the present application,
the receiver is specifically configured to receive, when a local JavaScript resource corresponding to the target rollback version number does not exist in the user client, a content distribution network address request sent by the user client, where the content distribution network address request includes a platform parameter of the user client, a target unique identifier of a real Native of a function module currently accessed by the user, and a target unique identifier and a target rollback version number of a target rollback version number, where the target unique identifier and the target rollback version number do not correspond to the local JavaScript resource;
The processor is specifically configured to generate a content distribution network address request response according to the platform parameter of the user client, the target unique identifier of the non-corresponding local JavaScript resource, and the target rollback version number, where the content distribution network address request response includes a target content distribution network address required by reactive of a functional module corresponding to the target unique identifier of the non-corresponding local JavaScript resource and the target rollback version number;
the sender is specifically configured to send the content distribution network address request response to the user client, so that the user client obtains JavaScript resources by using the target content distribution network address.
In one possible implementation manner of the third aspect of the embodiments of the present application,
the processor is specifically configured to determine, according to the target unique identifier and the target rollback version number of the non-corresponding local JavaScript resource, a corresponding content distribution network address in a history JavaScript resource version list stored in the server, where the history JavaScript resource version list includes an online unique identifier, an online version number, and an online content distribution network address of a reactive of all functional modules of the target application program, and the online content distribution network address corresponds to the online version number;
And determining a target content distribution network address matched with the platform parameters in the content distribution network addresses.
In one possible implementation manner of the third aspect of the embodiments of the present application,
the transmitter is specifically configured to send a rollback completion instruction to the development client after generating the JavaScript resource version number list.
In a fourth aspect, an embodiment of the present application provides an application rollback apparatus, applied to a user client, where the apparatus includes: a transmitter, a receiver, and a processor;
the sender is configured to send a sending request to a server, where the sending request includes a target unique identifier of a functional module that is currently accessed by a user and received on the user client;
the receiver is configured to receive a response to the issuing request sent by the server, where the response to the issuing request includes a target rollback version number corresponding to the target unique identifier;
the processor is used for determining corresponding JavaScript resources according to the target rollback version number;
and the processor is also used for rendering the function module currently accessed by the user by using the JavaScript resource.
In one possible implementation manner of the fourth aspect of the embodiment of the present application,
The processor is specifically configured to determine whether a standby version number matched with the target rollback version number exists in a version number corresponding to the local JavaScript resource;
if yes, the user client determines a corresponding local JavaScript resource according to the standby version number, so that the user client uses the local JavaScript resource to render the function module currently accessed by the user.
In one possible implementation manner of the fourth aspect of the embodiment of the present application,
the processor is further configured to send a content distribution network address request to the server if not, where the content distribution network address request includes a platform parameter of the user client, a target unique identifier of a reactive function module currently accessed by the user, and a target rollback version number, where there is no target unique identifier of a corresponding local JavaScript resource, and the target rollback version number;
the receiver is further configured to receive a content distribution network address request response sent by the server, where the content distribution network address request response includes a target content distribution network address required by reactive of the function module corresponding to the target rollback version number without the corresponding local JavaScript resource, so that the user client obtains the JavaScript resource by using the target content distribution network address, and renders the function module currently accessed by the user by using the JavaScript resource.
In one possible implementation manner of the fourth aspect of the embodiment of the present application,
the processor is further configured to store the target content delivery network address to a local database.
In a fifth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a server-side application rollback method.
In a sixth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements an application rollback method for a user client.
The embodiment of the application rollback method, device and storage medium, wherein a development client sends an application rollback request to a server, and the server generates a JavaScript resource version number list of a corresponding target application program after receiving the application rollback request, and provides a unique identifier and rollback version number to which the reactionary of all function modules corresponding to the target application program is to be rolled back for a user client. And the user client sends a issuing request to the server so as to inquire the server about the target rollback version number corresponding to the currently accessed functional module reactive. And the server determines a target rollback version number corresponding to the target unique identifier in a JavaScript resource version number list according to the target unique identifier of the currently accessed functional module sent by the user client, and sends a request response to the user client. And the user client determines a local JavaScript resource according to the target rollback version number of the reactive of the currently accessed function module in the issuing request response, and renders the currently accessed function module by using the local JavaScript resource. Therefore, according to the technical scheme provided by the application, for the development client, the application rollback operation can be completed only by sending the application rollback request once, the steps are simple, and the time consumption is low; for the server, the unique identifier and the rollback version number which need to be rolled back can be determined on line according to the unique identifier of the reactive of the functional module of the target application program, and the operations of resource packaging and online restarting of the reactive of each functional module of the target application program are not needed, so that the time wasted in operation is reduced; for the user client, the target rollback version number to be rolled back can be obtained through the target unique identifier of the reactive of the currently accessed functional module, and the currently accessed functional module is rendered through the corresponding local JavaScript resource to complete rollback.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings that are needed in the embodiments will be briefly described below, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 illustrates a schematic diagram of an application rollback system;
FIG. 2 shows a schematic flow chart of an application rollback method;
FIG. 3 illustrates a development client application rollback operation interface;
FIG. 4 illustrates a schematic diagram of a JavaScript resource version number list;
FIG. 5 illustrates a flow chart of a server generating a JavaScript resource version number list;
FIG. 6 illustrates a flow diagram of a server sending a rollback complete instruction to a development client;
FIG. 7 illustrates a flow diagram of a user client determining a local JavaScript resource;
FIG. 8 is a flow chart illustrating a user client requesting a content delivery network address from a server;
FIG. 9 is a schematic flow chart of delivering CDN addresses according to a content delivery network address request by a server;
FIG. 10 is a schematic flow chart of determining CDN addresses by a server;
FIG. 11 illustrates a schematic diagram of a structure of a history JavaScript resource version list;
FIG. 12 shows a schematic diagram of a server-side application rollback apparatus;
fig. 13 shows a schematic structural diagram of an application rollback apparatus of a user client.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Fig. 1 shows a schematic structure of an application rollback system.
As shown in fig. 1, the application rollback system includes a development client, a server and a user client, and fig. 1 shows a communication relationship among the development client, the server and the user client, where the number of development clients, the number of servers and the number of user clients may be multiple, that is, multiple development clients send rollback requests for multiple target application programs at the same time, and multiple servers receiving rollback requests may also generate corresponding JavaScript resource version number lists for different rollback requests. Multiple user clients can send down requests to the server at the same time for a large number of users to normally run mobile applications at the same time.
The development client, the server and the user client provided in the embodiments of the present application may be a PC (personal computer), a data platform, a tablet computer, a mobile phone, and other operation terminals capable of developing and implementing an application rollback function, where the embodiments of the present application only make exemplary names for three terminals, and do not limit the names.
Specifically, fig. 2 shows a schematic flow chart of an application rollback method.
As shown in fig. 2, the development client transmits an application rollback request to the server at S100.
Actual operation as shown in fig. 3, fig. 3 shows a development client application rollback operation interface, and it can be seen that all online reactivatives related information of all functional modules of a target application program is shown on the application rollback operation interface, including a unique identifier of online reactivatives, a version number of the online reactivatives, an online date of the online reactivatives, and the like, and at the same time, positions indicating rollback operations are provided at corresponding positions of the online reactivatives.
Where online reactive refers to reactive that has been applied to, and is being applied to, each functional module in the target application before the specified time node. Wherein the time node is specified before, for example, the moment at which the application rollback request is sent. Specifically, the reactive that has been applied to, and is being applied to, the respective functional modules is described with reference to the following examples. For example, the example target application program includes a reactive nature of the friend-making function module, a reactive nature of the rental car function module, and a reactive nature of the job-finding function module, wherein the reactive nature of the friend-making function module is already on line in three versions, namely, version 1, version 2, and version 3, and the version currently being applied is version 3, and the version already applied to the target application program is version 1 and version 2; the real Native of the taxi function module is already on line with two versions, namely a version 1 and a version 3, and the version which is currently being applied is a version 2, and the version which is already applied to the target application program is a version 1; the inactive native of the work function module is found to be already on-line with one version, version 1, and the version currently being applied is version 1.
The reactivations of the functional modules can be distinguished by using unique identifiers, and each reactivative of the functional module corresponds to one unique identifier. Specifically, the unique identifier of the reactive of the friend-making function module is 1, the unique identifier of the reactive of the renting function module is 2, and the unique identifier of the reactive of the work function module is 3. It should be noted that the unique identification is not limited to a numerical representation, but any symbol with distinguishing effect may be used.
The development client performs rollback operation on the reactive of the functional module with the error or needing to be adjusted according to the actual requirement, and the version of the reactive of the functional module needing to be adjusted is usually the version of the reactive which is newly on line, namely the version of the reactive with the closest on-line date and the designated time node. For example, the developer needs to adjust the reactive of the friend-making functional module with the unique identifier 1 and the version number 3, and determine to roll back the reactive to the online reactive with the unique identifier 1 and the version number 2, and then needs to click the position indicating the rollback operation corresponding to the online reactive with the unique identifier 1 and the version number 2 to complete the rollback operation. Wherein a version number of 2 may be referred to as a rollback version number.
It should be noted that if the version of the reactive currently being applied by the functional module of the target application program can be used normally without modification, the version may be regarded as a rollback version number, for example, the reactive of the rental car functional module uniquely identified as 2 and having a version number of 2 is the version of the reactive currently being applied, and since no modification is required, the version number of 2 may be regarded as a rollback version number directly.
Further, for the reactivative of the functional module without modification, the reactivative and the corresponding online reactivative can be hidden, and the reactivative can be continuously used by default without clicking and rolling operations, so that the times of clicking and rolling operations of developers are reduced, and misoperation and rolling time are reduced.
According to the above example, the development client sends an application rollback request to the server, in which the unique identification of reactive and rollback version numbers of all functional modules of the target application are required to be included.
And S200, after receiving an application rollback request sent by a development client, the server combines the unique identifier of the real Native of the functional module and the rollback version number to generate a JavaScript resource version number list of the target application program.
Fig. 4 illustrates a schematic structure of a JavaScript resource version number list. Therefore, the JavaScript resource version number list only contains the unique identification and the rollback version number of the reactive of all the functional modules of the target application program, the information quantity is reduced, so that the generation time of the JavaScript resource version number list is shorter, and the time required by application rollback can be reduced.
Specifically, fig. 5 illustrates a flowchart of generating a JavaScript resource version number list by a server, as shown in fig. 5, where the flowchart includes:
s201, the server arranges the unique identifiers of the reactivations of the function modules according to the sequence of the unique identifiers of the reactivations of the preset function modules to obtain a unique identifier sequence of a target application program;
s202, the server generates a JavaScript resource version number list of the target application program according to the unique identification sequence of the target application program and the rule corresponding to the rollback version number of the functional module and the unique identification of the functional module.
The server sorts the unique identifiers of the reactive modules of all the functional modules carried in the application rollback request, and may sort the unique identifiers in the order from low to high, as shown in fig. 4. The unique identifiers can be ranked according to the sequence from high to low, or the unique identifiers can be ranked according to a preset priority ranking rule, so that a unique identifier sequence of the target application is obtained.
Since the unique identifier corresponds to the rollback version number, after the ordering of the unique identifiers of the reactive of the functional modules is determined, the ordering of the rollback version numbers of each reactive may be correspondingly determined according to the unique identifier sequence of the target application. And finally, correspondingly combining the unique identifications of all the reactionary with the rollback version numbers to generate a JavaScript resource version number list of the target application program.
Except for the method for generating the JavaScript resource version number list of the target application program disclosed above. The JavaScript resource version number list of the target application program can also be generated by hiding the reactivatives corresponding to versions other than the rollback version numbers of all the functional modules of the target application program and only displaying the reactivatives corresponding to the rollback version numbers.
Further, fig. 6 illustrates a flow diagram of a server sending a rollback complete instruction to a development client.
As shown in fig. 6, the process includes:
s203, the server sends a rollback completion instruction to the development client after generating the JavaScript resource version number list.
After the server generates the JavaScript resource version number list of the target application program, the server is proved to have completed developing the application rollback instruction sent by the client. At this time, the server may send a rollback completion instruction to the development client informing the development client that the application rollback operation has been completed. Further, the development client may change the application rollback operation interface according to the rollback completion instruction, for example, change the position indicating the rollback operation to a state that cannot be clicked, or display the position indicating the rollback operation as a character such as rolled back.
S300, the user client sends a request for issuing to the server.
Since the normal operation of the target application depends on the reactive, the modification of the reactive by the developer may cause the target application to be unavailable, and at this time, if the user client needs to normally use the target application, the reactive being modified needs to be rolled back to the target reactive first, so that the target application can be normally operated.
From the above, when accessing the target application program, the user client first sends a request for issuing to the server, where the request for issuing includes the target unique identifier of the functional module currently accessed by the user and received by the user client. Because the rollback operation performed by the developer at the development client is directed at the real Native of all the functional modules, and a JavaScript resource version number list of the target application program is generated based on the rollback operation. Therefore, the reactivative of the function module currently accessed by the user client can find the corresponding rollback version number in the JavaScript resource version number list of the target application program.
S400, the server sends a request response to the user client.
Specifically, the server determines a target unique identifier of reactive corresponding to a function module identical to the function module currently accessed by the user in a JavaScript resource version number list of the target application program; and the server determines the target rollback version number of the reactive of the function module currently accessed by the user in a JavaScript resource version number list of the target application according to the target unique identifier.
Therefore, the issuing request response comprises a target rollback version number corresponding to the target unique identifier, so that the user client uses JavaScript resources which are determined to be corresponding according to the target rollback version number to render the function module which is currently accessed by the user.
And S500, the user client renders the function module currently accessed by the user by using JavaScript resources corresponding to the target rollback version number.
If the mobile application is to be normally operated, the corresponding function module needs to be rendered by utilizing the corresponding JavaScript resource. Correspondingly, once the reactionary of the currently accessed function module sends rollback and rolls back to the target rollback version number, the currently accessed function module of the user needs to be rendered through the JavaScript resource corresponding to the target rollback version number.
Specifically, fig. 7 illustrates a flowchart of determining JavaScript resources by a user client, as shown in fig. 7, where the flowchart includes:
s511, the user client judges whether a standby version number matched with the target rollback version number exists in the version numbers corresponding to the local JavaScript resources.
And S512, if so, the user client determines a corresponding local JavaScript resource according to the standby version number, so that the user client uses the local JavaScript resource to render the function module currently accessed by the user.
The user client receives a target rollback version number corresponding to the reactive of the function module currently accessed by the user and sent by the server, and firstly, whether a standby version number matched with the target rollback version number exists in the version number corresponding to the local JavaScript resource is required to be determined. For example, the target rollback version number is 2, if in the user client, the version numbers corresponding to the local JavaScript resources that are identical to the reactive unique identifier of the functional module currently accessed by the user are respectively 1, 1.1.1, 1.2.1, 1.3.0, 2, 2.1.1, 2.2.1. Obviously, the target rollback version number belongs to the version number corresponding to the local JavaScript resource, which indicates that the local JavaScript resource corresponding to the target rollback version number exists in the user client. At this time, the version number 2 is determined to be the standby version number, and the user client can render the function module currently accessed by the user by using the local JavaScript resource corresponding to the version number 2, so that the target application program operates normally.
Further, fig. 8 illustrates a flow chart of a user client requesting a content distribution network address from a server, as shown in fig. 8, the flow chart includes:
s521, if not, sending a content distribution network address request to the server, wherein the content distribution network address request comprises platform parameters of the user client, a target unique identifier of a reactive function module currently accessed by the user, and a target rollback version number, wherein the target unique identifier and the target rollback version number do not correspond to local JavaScript resources;
s522, the user client receives a content distribution network address request response sent by the server, wherein the content distribution network address request response comprises a target content distribution network address required by reactive of a function module corresponding to the target rollback version number without the corresponding local JavaScript resource, so that the user client obtains the JavaScript resource by using the target content distribution network address, and renders the function module currently accessed by the user by using the JavaScript resource.
If the version number corresponding to the local JavaScript resource does not have the standby version number matched with the target rollback version number, the fact that the target rollback version number does not have the corresponding local JavaScript resource is indicated, and at the moment, if a functional module currently accessed by a user needs to be rendered, the JavaScript resource corresponding to the target rollback version number needs to be acquired first. The user client may send a content delivery network address (ContentDelivery Network, CDN) request to the server to acquire the corresponding JavaScript resource.
Specifically, fig. 9 shows a schematic flow chart of delivering a CDN address according to a content delivery network address request by a server, as shown in fig. 9, where the flow includes:
s531, when a local JavaScript resource corresponding to the target rollback version number does not exist in the user client, receiving a content distribution network address request sent by the user client, wherein the content distribution network address request comprises platform parameters of the user client, a target unique identifier of a reactive function module currently accessed by the user, and a target unique identifier and a target rollback version number of the target rollback version number, which do not correspond to the local JavaScript resource;
s532, generating a content distribution network address request response according to the platform parameters of the user client, the target unique identifier of the non-corresponding local JavaScript resource and the target rollback version number, wherein the content distribution network address request response comprises a target content distribution network address required by the reactionary of the functional module corresponding to the target unique identifier of the non-corresponding local JavaScript resource and the target rollback version number.
S533, sending the content distribution network address request response to the user client so that the user client can acquire JavaScript resources by using the target content distribution network address.
The server receives a content distribution network address request sent by the user client, and generates a content distribution network address request response according to the carried platform parameters of the user client, such as android, ios and the like, and the target unique identifier and the target rollback version number without corresponding local JavaScript resources.
Specifically, fig. 10 shows a schematic flow chart of determining a CDN address by a server, as shown in fig. 10, where the flow includes:
s5321, the server determines a corresponding content distribution network address in a history JavaScript resource version list stored in the server according to the target unique identifier and the target rollback version number of the non-corresponding local JavaScript resource, wherein the history JavaScript resource version list comprises the online unique identifier, the online version number and the online content distribution network address of the reactive of all the functional modules of the target application program, and the online content distribution network address corresponds to the online version number;
s5322, the server determines a target content distribution network address matched with the platform parameter in the content distribution network addresses.
Parameters corresponding to the online reactivations of all the functional modules of the target application program, such as a unique identifier of the online reactivations, a version number of the online reactivations, and a content distribution network address of the online reactivations, are stored in the server. Fig. 11 illustrates a schematic structural diagram of a historical JavaScript resource version list, where, as shown in fig. 11, the content delivery network address in the historical JavaScript resource version list includes multiple forms, and an applicable CDN address can be determined from the content delivery network address according to platform parameters of the user client. For example, the content delivery network addresses ios-url-1 and android-url-1 may be determined by unique identification 1 and target rollback version number 2. Because the platform parameter of the user client is ios, the target content distribution network address may be determined to be ios-url-1.
The server sends the target content distribution network address to the user client, so that the user client obtains JavaScript resources according to the target content distribution network address, and the JavaScript resources are used for rendering the function module currently accessed by the user.
Further, the user client saves the JavaScript resource obtained according to the target content distribution network address in a local database, so that the subsequent use is convenient.
Fig. 12 shows a schematic structural diagram of a server-side application rollback apparatus, the apparatus comprising: transmitter 100, receiver 200, and processor 300.
A receiver 200, configured to receive an application rollback request sent by a development client, where the application rollback request includes a unique identifier of reactive of all functional modules of a target application program and a rollback version number, and the unique identifier corresponds to the rollback version number;
a processor 300, configured to generate a JavaScript resource version number list of the target application according to the unique identifier and the rollback version number of the reactive native of the functional module, where the JavaScript resource version number list includes the unique identifier and the rollback version number of the reactive of each functional module of the target application;
the receiver 200 is further configured to receive a sending request sent by a user client, where the sending request includes a target unique identifier of a reactive of a function module currently accessed by a user and received on the user client;
and the sender 100 is configured to send a response to the user client, where the response to the request includes a target rollback version number corresponding to the unique identifier that matches the target unique identifier, so that the user client uses a local JavaScript resource determined according to the target rollback version number to render a function module currently accessed by the user.
Optionally, the processor 300 is further configured to arrange the unique identifiers of the reactivations of the function modules according to a sequence of the unique identifiers of the reactivations of the preset function modules, so as to obtain a unique identifier sequence of the target application program; the processor 300 is further configured to generate a JavaScript resource version number list of the target application according to the unique identification sequence of the target application according to a rule corresponding to the rollback version number of the functional module and the unique identification of the functional module.
Optionally, the processor 300 is further configured to determine, in a JavaScript resource version number list of the target application, a target unique identifier of reactive corresponding to a function module that is the same as a function module currently accessed by the user; the processor 300 is further configured to determine, in the JavaScript resource version number list of the target application program, a target rollback version number of the reactive of the function module currently accessed by the user according to the target unique identifier.
Optionally, the receiver 200 is further configured to receive a content distribution network address request sent by the user client, where the content distribution network address request includes a platform parameter of the user client, a target unique identifier of a reactive of a function module currently accessed by the user, and a target unique identifier and a target rollback version number of a target rollback version number that do not have a corresponding local JavaScript resource; the processor 300 is further configured to generate a content distribution network address request response according to the platform parameter of the user client, the target unique identifier of the non-corresponding local JavaScript resource, and the target rollback version number, where the content distribution network address request response includes a target content distribution network address required by a function module corresponding to the target rollback version number of the non-corresponding local JavaScript resource; the sender 100 is further configured to send the content delivery network address request response to the user client.
Optionally, the processor 300 is further configured to determine, according to the target unique identifier and the target rollback version number of the non-corresponding local JavaScript resource, a corresponding content distribution network address in a history JavaScript resource version list stored in the server, where the history JavaScript resource version list includes an online unique identifier, an online version number, and an online content distribution network address of the reactive of all functional modules of the target application program, and the online content distribution network address corresponds to the online version number; the processor 300 is further configured to determine a target content distribution network address matching the platform parameter from among the content distribution network addresses.
Optionally, the sender 100 is further configured to send a rollback complete instruction to the development client after generating the JavaScript resource version number list.
Fig. 13 shows a schematic structural diagram of an application rollback apparatus of a user client, the apparatus comprising: transmitter 600, receiver 700, and processor 800.
The sender 600 is configured to send a request for issuing to a server, where the request for issuing includes a target unique identifier of a reactive function module currently accessed by a user and received on the user client;
The receiver 700 is configured to receive a response to a request for transmission sent by the server, where the response to the request for transmission includes a target rollback version number corresponding to the unique identifier that matches the target unique identifier;
the processor 800 is configured to determine, according to the target rollback version number, a corresponding local JavaScript resource;
the processor 800 is further configured to render a function module currently accessed by the user using the local JavaScript resource.
Optionally, the processor 800 is further configured to determine whether a standby version number matching the target rollback version number exists in the version numbers corresponding to the local JavaScript resources; the processor 800 is further configured to determine, if so, a corresponding local JavaScript resource according to the standby version number.
Optionally, the processor 800 is further configured to send, if not, a content distribution network address request to the server, where the content distribution network address request includes a platform parameter of the user client, a target unique identifier of a reactive of a function module currently accessed by the user, and a target unique identifier and a target rollback version number of a target rollback version number that do not have a corresponding local JavaScript resource; the receiver 700 is further configured to receive a content distribution network address request response sent by the server, where the content distribution network address request response includes a target content distribution network address required by a function module corresponding to the target rollback version number without the corresponding local JavaScript resource.
Optionally, the processor 800 is further configured to save the target content distribution network address to a local database.
The present application also provides a readable storage medium having a computer program stored therein, which when executed by at least one processor of a server-side application rollback apparatus performs the application rollback method according to any of the above embodiments.
The present application also provides a readable storage medium having a computer program stored therein, which when executed by at least one processor of a user client application rollback apparatus performs the application rollback method described in any of the above embodiments.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer-readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that modifications may be made to the technical solutions described in the foregoing embodiments, or equivalents may be substituted for some or all of the technical features thereof, without departing from the spirit of the technical solutions of the embodiments of the invention.
Claims (20)
1. An application rollback method applied to a server, the method comprising:
receiving an application rollback request sent by a development client, wherein the application rollback request comprises a unique identifier and a rollback version number of the reactionary of all functional modules of a target application program, and the unique identifier corresponds to the rollback version number;
generating a JavaScript resource version number list of the target application program according to the unique identifier and the rollback version number of the reactive of the functional module, wherein the JavaScript resource version number list comprises the unique identifier and the rollback version number of the reactive of each functional module of the target application program;
Receiving a sending request sent by a user client, wherein the sending request comprises a target unique identifier of a functional module which is currently accessed by a user and is received by the user client;
and responding to the issuing request, and sending a target rollback version number corresponding to the target unique identifier to the user client so that the user client uses the JavaScript resource which is determined to correspond to the target rollback version number to render the function module which is currently accessed by the user.
2. The method of claim 1, wherein the user client transmitting a target rollback version number corresponding to the target unique identification comprises:
acquiring a target rollback version number corresponding to the target unique identifier from a JavaScript resource version number list of the target application program according to the unique identifier matched with the target unique identifier, wherein the target rollback version number is a rollback version number of a reactive of a function module currently accessed by the user;
and sending the target rollback version number to the user client.
3. The method of claim 1, wherein the sending, in response to the issuing request, the target rollback version number corresponding to the target unique identifier to the user client comprises:
When the local JavaScript resource corresponding to the target rollback version number does not exist in the user client, receiving a content distribution network address request sent by the user client, wherein the content distribution network address request comprises platform parameters of the user client, a target unique identifier of a reactive function module currently accessed by the user and a target unique identifier and a target rollback version number of the target rollback version number, which do not correspond to the local JavaScript resource;
generating a content distribution network address request response according to the platform parameters of the user client, the target unique identifier of the non-corresponding local JavaScript resource and the target rollback version number, wherein the content distribution network address request response comprises a target content distribution network address required by the reactionary of a functional module corresponding to the target unique identifier of the non-corresponding local JavaScript resource and the target rollback version number;
and sending the content distribution network address request response to the user client so that the user client can acquire JavaScript resources by using the target content distribution network address.
4. The method of claim 3, wherein generating the content delivery network address request reply based on the platform parameters of the user client, the target unique identification of the non-corresponding local JavaScript resource, and the target rollback version number comprises:
Determining a corresponding content distribution network address in a history JavaScript resource version list stored in the server according to the target unique identifier and the target rollback version number of the non-corresponding local JavaScript resource, wherein the history JavaScript resource version list comprises an online unique identifier, an online version number and an online content distribution network address of a reactive of all functional modules of a target application program, and the online content distribution network address corresponds to the online version number;
and determining a target content distribution network address matched with the platform parameters in the content distribution network addresses.
5. The method according to any one of claims 1-4, further comprising:
and after the JavaScript resource version number list is generated, a rollback completion instruction is sent to the development client.
6. An application rollback method applied to a user client, the method comprising:
sending a sending request to a server, wherein the sending request comprises a target unique identifier of a functional module which is currently accessed by a user and is received on a user client;
Receiving a request response sent by the server, wherein the request response comprises a target rollback version number corresponding to the target unique identifier;
determining corresponding JavaScript resources according to the target rollback version number;
and rendering the function module currently accessed by the user by using the JavaScript resource.
7. The method of claim 6, wherein determining the corresponding JavaScript resource based on the target rollback version number comprises:
judging whether a standby version number matched with the target rollback version number exists in the version numbers corresponding to the local JavaScript resources;
if yes, the user client determines a corresponding local JavaScript resource according to the standby version number, so that the user client uses the local JavaScript resource to render the function module currently accessed by the user.
8. The method of claim 7, wherein the method further comprises:
if not, a content distribution network address request is sent to the server, wherein the content distribution network address request comprises platform parameters of the user client, a target unique identifier of a reactive function module currently accessed by the user, and a target unique identifier and a target rollback version number of a non-corresponding local JavaScript resource in the target unique identifier and the target rollback version number of the functional module currently accessed by the user;
And receiving a content distribution network address request response sent by the server, wherein the content distribution network address request response comprises a target content distribution network address required by a real Native of a functional module corresponding to the target rollback version number without the corresponding local JavaScript resource, so that the user client can acquire the JavaScript resource by using the target content distribution network address, and render the functional module currently accessed by the user by using the JavaScript resource.
9. The method of claim 8, wherein the method further comprises:
and storing the target content distribution network address to a local database.
10. An application rollback apparatus for use with a server, the apparatus comprising: a transmitter, a receiver, and a processor;
the transmitter is configured to receive an application rollback request sent by a development client, where the application rollback request includes a unique identifier of reactive of all functional modules of a target application program and a rollback version number, and the unique identifier corresponds to the rollback version number;
the processor is configured to generate a JavaScript resource version number list of the target application according to the unique identifier and the rollback version number of the reactive of the functional module, where the JavaScript resource version number list includes the unique identifier and the rollback version number of the reactive of each functional module of the target application;
The receiver is used for receiving a sending request sent by a user client, wherein the sending request comprises a target unique identifier of a functional module which is currently accessed by a user and is received on the user client;
and the transmitter is further used for responding to the issuing request and transmitting a target rollback version number corresponding to the target unique identifier to the user client so that the user client uses the function module which determines the corresponding JavaScript resource according to the target rollback version number to render the current access of the user.
11. The apparatus of claim 10, wherein the device comprises a plurality of sensors,
the processor is specifically configured to obtain, from a JavaScript resource version number list of the target application program, a target rollback version number corresponding to the target unique identifier according to a unique identifier that matches the target unique identifier, where the target rollback version number is a rollback version number of a reactive of a function module currently accessed by the user;
the transmitter is specifically configured to send the target rollback version number to the user client.
12. The apparatus of claim 10, wherein the device comprises a plurality of sensors,
The receiver is specifically configured to receive, when a local JavaScript resource corresponding to the target rollback version number does not exist in the user client, a content distribution network address request sent by the user client, where the content distribution network address request includes a platform parameter of the user client, a target unique identifier of a real Native of a function module currently accessed by the user, and a target unique identifier and a target rollback version number of a target rollback version number, where the target unique identifier and the target rollback version number do not correspond to the local JavaScript resource;
the processor is specifically configured to generate a content distribution network address request response according to the platform parameter of the user client, the target unique identifier of the non-corresponding local JavaScript resource, and the target rollback version number, where the content distribution network address request response includes a target content distribution network address required by reactive of a functional module corresponding to the target unique identifier of the non-corresponding local JavaScript resource and the target rollback version number;
the sender is specifically configured to send the content distribution network address request response to the user client, so that the user client obtains JavaScript resources by using the target content distribution network address.
13. The apparatus of claim 12, wherein the device comprises a plurality of sensors,
the processor is specifically configured to determine, according to the target unique identifier and the target rollback version number of the non-corresponding local JavaScript resource, a corresponding content distribution network address in a history JavaScript resource version list stored in the server, where the history JavaScript resource version list includes an online unique identifier, an online version number, and an online content distribution network address of a reactive of all functional modules of the target application program, and the online content distribution network address corresponds to the online version number;
and determining a target content distribution network address matched with the platform parameters in the content distribution network addresses.
14. The device according to any one of claims 10-13, wherein,
the transmitter is specifically configured to send a rollback completion instruction to the development client after generating the JavaScript resource version number list.
15. An application rollback apparatus for use with a user client, the apparatus comprising: a transmitter, a receiver, and a processor;
the sender is configured to send a sending request to a server, where the sending request includes a target unique identifier of a functional module that is currently accessed by a user and received on the user client;
The receiver is configured to receive a response to the issuing request sent by the server, where the response to the issuing request includes a target rollback version number corresponding to the target unique identifier;
the processor is used for determining corresponding JavaScript resources according to the target rollback version number;
and the processor is also used for rendering the function module currently accessed by the user by using the JavaScript resource.
16. The apparatus of claim 15, wherein the device comprises a plurality of sensors,
the processor is specifically configured to determine whether a standby version number matched with the target rollback version number exists in a version number corresponding to the local JavaScript resource;
if yes, the user client determines a corresponding local JavaScript resource according to the standby version number, so that the user client uses the local JavaScript resource to render the function module currently accessed by the user.
17. The apparatus of claim 16, wherein the device comprises a plurality of sensors,
the processor is further configured to send a content distribution network address request to the server if not, where the content distribution network address request includes a platform parameter of the user client, a target unique identifier of a reactive function module currently accessed by the user, and a target rollback version number, where there is no target unique identifier of a corresponding local JavaScript resource, and the target rollback version number;
The receiver is further configured to receive a content distribution network address request response sent by the server, where the content distribution network address request response includes a target content distribution network address required by reactive of the function module corresponding to the target rollback version number without the corresponding local JavaScript resource, so that the user client obtains the JavaScript resource by using the target content distribution network address, and renders the function module currently accessed by the user by using the JavaScript resource.
18. The apparatus of claim 17, wherein the device comprises a plurality of sensors,
the processor is further configured to store the target content delivery network address to a local database.
19. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the application rollback method of any of claims 1-5.
20. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements the application rollback method of any of claims 6-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910790766.7A CN110554963B (en) | 2019-08-26 | 2019-08-26 | Application rollback method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910790766.7A CN110554963B (en) | 2019-08-26 | 2019-08-26 | Application rollback method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110554963A CN110554963A (en) | 2019-12-10 |
| CN110554963B true CN110554963B (en) | 2023-07-25 |
Family
ID=68738371
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910790766.7A Active CN110554963B (en) | 2019-08-26 | 2019-08-26 | Application rollback method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110554963B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111625262B (en) * | 2020-05-28 | 2023-08-22 | 广东浪潮大数据研究有限公司 | Rollback method, system, equipment and storage medium of workload resource |
| CN113568644A (en) * | 2021-08-06 | 2021-10-29 | 上海中通吉网络技术有限公司 | Updating method of mobile terminal application |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017113060A1 (en) * | 2015-12-28 | 2017-07-06 | 华为技术有限公司 | Website access method and device, and website system |
| EP3529971B1 (en) * | 2016-11-17 | 2022-06-15 | Huawei Technologies Co., Ltd. | Electronic device, software provisioning server and methods thereof |
| CN107729041B (en) * | 2017-07-26 | 2020-10-20 | 深圳壹账通智能科技有限公司 | Application program hot updating method, device, terminal and storage medium |
| CN108881393B (en) * | 2018-05-22 | 2021-03-23 | 北京达佳互联信息技术有限公司 | Data issuing method, device, computer and storage medium |
| CN109445833B (en) * | 2018-11-09 | 2022-02-01 | 苏宁消费金融有限公司 | React-native hot updating method |
-
2019
- 2019-08-26 CN CN201910790766.7A patent/CN110554963B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN110554963A (en) | 2019-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11201929B2 (en) | On-line browsing preference management | |
| CN107864175B (en) | Gray scale release control method, device, equipment and storage medium | |
| CN108595207A (en) | A kind of gray scale dissemination method, regulation engine, system, terminal and storage medium | |
| CN110554963B (en) | Application rollback method, device and storage medium | |
| CN113535267A (en) | Applet page configuration method and device, electronic equipment and storage medium | |
| CN110096295B (en) | Multi-module mobile application thermal updating method and system based on reactivating | |
| CN109922120B (en) | Method and terminal for improving DNS availability | |
| CN113900663B (en) | Data processing method and device | |
| CN114942838A (en) | Data access method, device, equipment and storage medium | |
| CN114490073A (en) | Electronic map operation and maintenance method, electronic map data using method and service system | |
| CN111159988A (en) | Model processing method and device, computer equipment and storage medium | |
| CN113518128A (en) | Cross-platform orchestrated actions | |
| US8655910B1 (en) | Methods and systems for coupling client-side and server-side persistence frameworks | |
| CN112182078A (en) | Method, device, equipment and storage medium for issuing and using electronic product | |
| CN112261072A (en) | Service calling method, device, equipment and storage medium | |
| CN111459737A (en) | Problem positioning method and device, computer equipment and storage medium | |
| CN114285743B (en) | Method, device, electronic equipment and storage medium for updating configuration information | |
| CN111625866B (en) | Authority management method, system, equipment and storage medium | |
| CN110888665B (en) | Method, device, equipment and storage medium for submitting changed content | |
| CN113609145B (en) | Database processing method, device, electronic equipment, storage medium and product | |
| US8887173B2 (en) | Method and system for communicating between computing devices | |
| CN108830441B (en) | Resource query method and device | |
| CN116506165A (en) | Cloud mobile phone identification method and device, electronic equipment and readable storage medium | |
| CN116233051A (en) | Page sharing method, device and equipment for applet and storage medium | |
| CN116186076A (en) | Caching and inquiring method, storage medium and equipment for database inquiring result |
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 |