CN110688102B - Method, system, device and storage medium for capturing execution result of asynchronous interface - Google Patents
Method, system, device and storage medium for capturing execution result of asynchronous interface Download PDFInfo
- Publication number
- CN110688102B CN110688102B CN201910931252.9A CN201910931252A CN110688102B CN 110688102 B CN110688102 B CN 110688102B CN 201910931252 A CN201910931252 A CN 201910931252A CN 110688102 B CN110688102 B CN 110688102B
- Authority
- CN
- China
- Prior art keywords
- resource
- asynchronous interface
- execution result
- information
- execution
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
-
- 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
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The application discloses a method, a system, a device and a computer readable storage medium for capturing an execution result of an asynchronous interface, wherein after the asynchronous interface is configured, a resource monitoring thread for monitoring a resource state is created, the resource monitoring thread locks a controlled resource by using ID information of the resource controlled by the asynchronous interface, monitors the running state of the resource, judges the execution result of the resource after reaching a steady state, finally obtains the execution result of the resource, generates prompt information for informing a user of the execution result, and feeds back the execution result of the resource to the user in time after the resource reaches the steady state, so that the user can quickly sense the execution effect of the asynchronous interface and the change condition of the operated resource, the user can make correct decisions and designs quickly, and the development efficiency and the use experience are improved.
Description
Technical Field
The present invention relates to the field of cloud platform management, and in particular, to a method, a system, an apparatus, and a computer-readable storage medium for capturing an execution result of an asynchronous interface.
Background
OpenStack4j is an OpenStack open source class library developed based on Java, and provides Java APIs for accessing and managing OpenStack. Developers can use OpenStack4j for OpenStack Java client application development or service extensions. Most of the interfaces in OpenStack4j are used by developers in the form of asynchronous interfaces because they involve complex business operations such as OpenStack resource addition, deletion, and change, and have long response time. However, it is often difficult for developers to timely notify the final execution result of the asynchronous interface, which affects the efficiency and quality of development.
Therefore, a method for capturing the execution result of the asynchronous interface is needed, which can quickly sense the execution effect of the asynchronous interface and the change condition of the operated resource, facilitate the user to quickly make a correct decision and design, and improve the development efficiency and the use experience.
Disclosure of Invention
In view of this, the present invention provides a method, a system, an apparatus, and a computer readable storage medium for capturing an execution result of an asynchronous interface, which can quickly sense an execution effect of the asynchronous interface and a change condition of an operated resource, so that a user can quickly make a correct decision and design, and development efficiency and use experience are improved. The specific scheme is as follows:
a method of capturing results of asynchronous interface execution, comprising:
the method comprises the steps that a resource operation interface driving software is utilized in advance to package and adapt input parameters of an asynchronous interface;
recording ID information of the resources operated by the asynchronous interface;
creating a resource monitoring thread, and monitoring the running state of the resource by using the resource monitoring thread and the ID information;
judging an execution result of the resource after the resource reaches a steady state by using the resource monitoring thread;
and generating prompt information for informing the user of the execution result by using the execution result obtained by the resource monitoring line.
Optionally, the process of pre-using the resource operation interface driver software to encapsulate and adapt the asynchronous interface includes:
the method comprises the steps that the rest services of OpenStack4j and the message middleware Websocket are packaged into a Java development framework through RestTemplate in advance;
and encapsulating and adapting the input parameters of the asynchronous interface corresponding to the corresponding resource operation interface of the OpenStack4j.
Optionally, the process of generating a prompt message for informing the user of the execution result includes:
and generating the prompt information for informing the user of the execution result in a Websocket message form.
Optionally, the recording ID information of the resource operated by the asynchronous interface includes:
checking whether the input parameters of the asynchronous interface are correct or not;
and if so, recording the ID information of the resources operated by the asynchronous interface.
The invention also discloses a system for capturing the execution result of the asynchronous interface, which comprises:
the pre-assembly module is used for packaging and adapting the input parameters of the asynchronous interface by utilizing the resource operation interface driving software in advance;
the ID recording module is used for recording the ID information of the resources operated by the asynchronous interface;
the monitoring thread creating module is used for creating a resource monitoring thread and monitoring the running state of the resource by using the resource monitoring thread and the ID information;
the execution result judgment module is used for judging the execution result of the resource after the resource reaches the steady state by using the resource monitoring thread;
and the execution result prompting module is used for generating prompting information for informing the user of the execution result by utilizing the execution result obtained by the resource monitoring line.
Optionally, the pre-assembly module includes:
the packaging unit is used for packaging the rest service of OpenStack4j and the message middleware Websocket into a Java development framework through RestTemplate in advance;
and the parameter assembling unit is used for encapsulating and adapting the input parameters of the asynchronous interface corresponding to the corresponding resource operation interface of the OpenStack4j.
Optionally, the execution result prompting module is specifically configured to generate, in a form of a Websocket message, the prompting information for notifying the user of the execution result by using the execution result obtained by the resource monitoring line.
Optionally, the ID recording module includes:
the checking unit is used for checking whether the input parameters of the asynchronous interface are correct or not;
and the ID recording unit is used for recording the ID information of the resources operated by the asynchronous interface if the verification unit verifies correctly.
The invention also discloses a device for capturing the execution result of the asynchronous interface, which comprises:
a memory for storing a computer program;
a processor for executing the computer program to implement the method of capturing the results of an execution of an asynchronous interface as described above.
The invention also discloses a computer readable storage medium, on which a computer program is stored, which, when executed by a processor, implements a method of capturing results of asynchronous interface execution as described above.
The method for capturing the execution result of the asynchronous interface comprises the following steps: the method comprises the steps that a resource operation interface driving software is utilized in advance to package and adapt input parameters of an asynchronous interface; recording ID information of resources operated by the asynchronous interface; establishing a resource monitoring thread, and monitoring the running state of the resource by using the resource monitoring thread and the ID information; judging an execution result of the resource after the resource reaches a steady state by using a resource monitoring thread; and generating prompt information for informing the user of the execution result by using the execution result obtained by the resource monitoring line.
According to the method, after the asynchronous interface is configured, the resource monitoring thread for monitoring the resource state is created, the resource monitoring thread locks the controlled resource by using the ID information of the resource controlled by the asynchronous interface, monitors the running state of the resource, judges the execution result of the resource after the resource reaches the steady state, finally obtains the execution result of the resource, generates prompt information for informing a user of the execution result, and feeds back the prompt information to the execution result of the resource of the user in time after the resource reaches the steady state, so that the user can quickly sense the execution effect of the asynchronous interface and the change condition of the operated resource, the user can conveniently and quickly make correct decisions and designs, and the development efficiency and the use experience are improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for capturing an execution result of an asynchronous interface according to an embodiment of the present invention;
FIG. 2 is a schematic diagram illustrating a principle of a method for capturing an execution result of an asynchronous interface according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating another method for capturing an execution result of an asynchronous interface according to an embodiment of the present invention;
FIG. 4 is a schematic flowchart illustrating a method for capturing an execution result of an asynchronous interface according to an embodiment of the present invention;
fig. 5 is a schematic flowchart of a method for capturing a rollback execution result of a cloud hard disk backup according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a system for capturing an execution result of an asynchronous interface according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention discloses a method for capturing an execution result of an asynchronous interface, which is shown in figure 1 and comprises the following steps:
s11: and (3) packaging and adapting the input parameters of the asynchronous interface by utilizing resource operation interface driving software in advance.
Specifically, the resource operation interface driver software may include a rest service of OpenStack4j and a Websocket, as shown in fig. 2, OpenStack4j may include a computation service package, a storage service package, and a network service package, where the computation service package corresponds to the computation operation interface, the storage service package corresponds to the storage operation interface, and the network service package corresponds to the network operation interface; the OpenStack4j can package the services in the form of a jar package to obtain an OpenStack4j. jar package, and then, the RestTemplate is used for packaging the rest services of the OpenStack4j and the message middleware Websocket into a Java development framework, so that the OpenStack4j can package and adapt the input parameters of the corresponding resource operation type interface, namely the asynchronous interface, according to the actual application requirements, and the corresponding resources can be controlled through the asynchronous interface subsequently.
S12: and recording ID information of the resource operated by the asynchronous interface.
Specifically, when the resource operation interface is used to drive the software to drive the asynchronous interface to operate the corresponding resource, the ID information of the operated resource is recorded, so that the operated resource can be continuously locked and tracked by using the ID information of the resource in the following, and the state of the resource can be acquired.
S13: and creating a resource monitoring thread, and monitoring the running state of the resource by using the resource monitoring thread and the ID information.
Specifically, in order to obtain the execution result of the resource in time, a resource monitoring thread for monitoring the running state of the resource is specially created, and the resource monitoring thread determines the resource by using the ID information of the resource, thereby realizing the monitoring of the running state of the resource.
S14: and judging the execution result of the resource after the resource reaches the steady state by using the resource monitoring thread.
Specifically, the resource monitoring thread is used to continuously monitor the running state of the resource until the resource reaches a steady state according to the operation of the asynchronous interface, wherein the steady state is the final state when the resource is finally executed according to the operation of the asynchronous interface, at this time, the resource does not perform further operation, the asynchronous interface also completes the control of the resource, since the success or failure of the resource execution is a steady state, the resource monitoring thread is required to specifically judge the execution result corresponding to the resource reaching the steady state, the resource monitoring thread uses the predefined corresponding relationship between the resource state and the state result of the execution result, and judges the corresponding execution result according to the state when the resource reaches the steady state, wherein the corresponding relationship between the state result is the corresponding relationship between various states when the resource reaches the steady state and the corresponding execution result, for example, the corresponding relationship between the available state and the execution result is recorded as success, and a correspondence of the error status and the execution result as failure.
S15: and generating prompt information for informing the user of the execution result by using the execution result obtained by the resource monitoring line.
Specifically, the execution result obtained by the resource monitoring thread is used to generate a prompt message for informing the user of the execution result of the resource, and the prompt message may be a message for displaying the execution result to the user in a text manner.
The prompt information may be information generated in the form of a Websocket message by using a rest service of a message middleware Websocket.
Therefore, after the asynchronous interface is configured, the resource monitoring thread for monitoring the resource state is created, the resource monitoring thread locks the controlled resource by using the ID information of the resource controlled by the asynchronous interface, monitors the running state of the resource, judges the execution result of the resource after reaching the steady state, finally obtains the execution result of the resource, generates prompt information for informing a user of the execution result, and feeds back the prompt information to the execution result of the resource of the user in time after the resource reaches the steady state, so that the user can quickly sense the execution effect of the asynchronous interface and the change condition of the operated resource, the user can quickly make correct decisions and designs, and the development efficiency and the use experience are improved.
The embodiment of the invention discloses a specific method for capturing an execution result of an asynchronous interface, and compared with the previous embodiment, the embodiment further describes and optimizes the technical scheme. Referring to fig. 3 and 4, specifically:
s21: the method comprises the steps that the rest services of OpenStack4j and the message middleware Websocket are packaged into a Java development framework through RestTemplate in advance;
s22: packaging and adapting input parameters of an asynchronous interface corresponding to a resource operation interface corresponding to the OpenStack4 j;
s23: and checking whether the input parameters of the asynchronous interface are correct.
Specifically, before operating the resource by using the asynchronous interface, validity of the input parameter of the asynchronous interface may be checked in advance, whether the input parameter is correctly packaged and adapted is determined, and if the input parameter is incorrect, the resource cannot be successfully operated, and a corresponding parameter prompt message may be generated to prompt the user to package and adapt the input parameter of the asynchronous interface again.
S24: and if so, recording the ID information of the resources operated by the asynchronous interface.
S25: establishing a resource monitoring thread, and monitoring the running state of the resource by using the resource monitoring thread and the ID information;
s26: judging an execution result of the resource after the resource reaches a steady state by using a resource monitoring thread;
s27: and generating prompt information for informing the user of the execution result in a Websocket message mode by using the execution result obtained by the resource monitoring line.
Further, the embodiment of the present invention also discloses a specific embodiment of a method for capturing an execution result of an asynchronous interface, which is shown in fig. 5, and specifically:
specifically, a specific method flow for capturing an execution result of cloud hard disk backup rollback is disclosed herein, wherein an interface of Open4j cloud hard disk backup rollback needs to specify an ID of the cloud hard disk backup and an ID of a target cloud hard disk that needs to be rolled back, and the specific steps are as follows:
s30: and determining an input parameter set, and encapsulating and adapting the input parameters of the asynchronous interface by using the input parameter set.
Specifically, after the resource operation interface driving software is packaged, an input parameter set required by the cloud hard disk backup rollback, namely the ID of the cloud hard disk backup and the ID of the target cloud hard disk required to be rolled back, is determined, and the input parameter set is packaged and adapted as an input parameter of the asynchronous interface.
S31: and checking whether the input parameters of the asynchronous interface are correct, if so, executing S32, and if not, executing S39.
Specifically, after the input parameters are packaged, the input parameters are checked, whether the packaging and the adaptation are successful or not is judged, if yes, the execution is continued, and if not, prompt information of execution failure can be generated to the user.
S32: executing corresponding interfaces os.blockstorage (). volumes (). get () and os.blockstorage (). get () of Open4j to obtain the cloud hard disk capacity and cloud hard disk backup specified by the parameters;
s33: and judging whether the cloud hard disk capacity and the cloud hard disk backup meet the constraint conditions of the backup operation, if so, executing S34, and if not, executing S39.
Specifically, when the cloud hard disk is backed up, it is necessary to determine whether the remaining capacity of the cloud hard disk is greater than the capacity required for the cloud hard disk backup, that is, the constraint condition, if so, the backup may be continued, and if not, the backup may not be continued, so that S39 may be executed, and an execution failure may be prompted.
S34: and confirming and executing the asynchronous interface os.blockstorage (). backups (). restore () of the backup rollback of the cloud hard disk.
Specifically, if the backup can be continued, the corresponding asynchronous interface is called, and the asynchronous interface calls the corresponding cloud hard disk resource to execute backup rollback.
S35: and judging whether the asynchronous interface is successfully executed, if so, executing S36, and otherwise, executing S39.
Specifically, after the asynchronous interface is successfully executed, a corresponding HTTP status code, generally 202, is returned, but after the asynchronous interface is successfully executed, only the operation instruction is issued to the openstack and the corresponding service operation is started on the resource, instead of the execution result of whether the resource is finally successfully or not, so that even if the asynchronous interface is successfully executed, the resource cannot be successfully executed, the subsequent resource monitoring thread is required to monitor, and if the asynchronous interface is unsuccessfully executed, it is indicated that the asynchronous interface fails to control the resource, so that the resource is definitely failed to execute.
S36: and starting a resource monitoring thread RestoreBackupThread, starting while circulation in the thread, and continuously judging the state of the capacity of the cloud hard disk until the state reaches a steady state.
S37: the resource monitoring thread judges whether the capacity of the cloud hard disk is in an available state, if so, S38 is executed, and if not, S39 is executed;
s39: defining successful Websocket Info information and informing a developer through a Websocket form;
s39: and defining lost Websocket Info information and informing the developer through a Websocket form.
Correspondingly, the embodiment of the present invention further discloses a system for capturing an execution result of an asynchronous interface, as shown in fig. 6, the system includes:
the preassembly module 1 is used for packaging and adapting input parameters of the asynchronous interface by utilizing resource operation interface driving software in advance;
the ID recording module 2 is used for recording the ID information of the resources operated by the asynchronous interface;
the monitoring thread creating module 3 is used for creating a resource monitoring thread and monitoring the running state of the resource by using the resource monitoring thread and the ID information;
the execution result judgment module 4 is used for judging the execution result of the resource after the resource reaches the steady state by using the resource monitoring thread;
and the execution result prompting module 5 is used for generating a prompting message for informing the user of the execution result by utilizing the execution result obtained by the resource monitoring line.
Specifically, the preassembly module 1 may specifically include an encapsulation unit and a parameter assembly unit; wherein the content of the first and second substances,
the packaging unit is used for packaging the rest service of OpenStack4j and the message middleware Websocket into a Java development framework through RestTemplate in advance;
and the parameter assembling unit is used for encapsulating and adapting the input parameters of the asynchronous interface corresponding to the corresponding resource operation interface of the OpenStack4j.
Specifically, the execution result prompting module 5 is specifically configured to generate, in the form of a Websocket message, a prompting message for notifying the user of the execution result by using the execution result obtained by the resource monitoring line.
Specifically, the ID recording module 2 may specifically include a verification unit and an ID recording unit; wherein the content of the first and second substances,
the checking unit is used for checking whether the input parameters of the asynchronous interface are correct or not;
and the ID recording unit is used for recording the ID information of the resources operated by the asynchronous interface if the verification unit verifies correctly.
In addition, the embodiment of the invention also discloses a device for capturing the execution result of the asynchronous interface, which comprises:
a memory for storing a computer program;
a processor for executing a computer program to implement a method of capturing results of asynchronous interface execution as described above.
In addition, the embodiment of the present invention also discloses a computer readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method for capturing the execution result of the asynchronous interface as described above is implemented.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The technical content provided by the present invention is described in detail above, and the principle and the implementation of the present invention are explained in this document by applying specific examples, and the above description of the examples is only used to help understanding the method of the present invention and the core idea thereof; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (8)
1. A method for capturing results of asynchronous interface execution, comprising:
the method comprises the steps that a resource operation interface driving software is utilized in advance to package and adapt input parameters of an asynchronous interface;
recording ID information of the resources operated by the asynchronous interface;
creating a resource monitoring thread, and monitoring the running state of the resource by using the resource monitoring thread and the ID information;
judging an execution result of the resource after the resource reaches a steady state by using the resource monitoring thread;
generating prompt information for informing a user of the execution result by using the execution result obtained by the resource monitoring line;
the process of packaging and adapting the asynchronous interface by using the resource operation interface driving software in advance comprises the following steps:
the method comprises the steps that the rest services of OpenStack4j and the message middleware Websocket are packaged into a Java development framework through RestTemplate in advance;
and encapsulating and adapting the input parameters of the asynchronous interface corresponding to the corresponding resource operation interface of the OpenStack4j.
2. The method for capturing the execution result of the asynchronous interface as claimed in claim 1, wherein the process of generating the prompt message for informing the user of the execution result comprises:
and generating the prompt information for informing the user of the execution result in a Websocket message form.
3. The method for capturing the execution result of the asynchronous interface according to claim 1 or 2, wherein the process for recording the ID information of the resource operated by the asynchronous interface comprises:
checking whether the input parameters of the asynchronous interface are correct or not;
and if so, recording the ID information of the resources operated by the asynchronous interface.
4. A system for capturing results of asynchronous interface execution, comprising:
the pre-assembly module is used for packaging and adapting the input parameters of the asynchronous interface by utilizing the resource operation interface driving software in advance;
the ID recording module is used for recording the ID information of the resources operated by the asynchronous interface;
the monitoring thread creating module is used for creating a resource monitoring thread and monitoring the running state of the resource by using the resource monitoring thread and the ID information;
the execution result judgment module is used for judging the execution result of the resource after the resource reaches the steady state by using the resource monitoring thread;
the execution result prompting module is used for generating prompting information for informing a user of the execution result by utilizing the execution result obtained by the resource monitoring line;
wherein the pre-assembly module comprises:
the packaging unit is used for packaging the rest service of OpenStack4j and the message middleware Websocket into a Java development framework through RestTemplate in advance;
and the parameter assembling unit is used for encapsulating and adapting the input parameters of the asynchronous interface corresponding to the corresponding resource operation interface of the OpenStack4j.
5. The system for capturing execution results of an asynchronous interface according to claim 4, wherein the execution result prompting module is specifically configured to generate the prompting information for notifying a user of the execution results in a Websocket message by using the execution results obtained by the resource monitoring line.
6. The system for capturing the execution result of the asynchronous interface according to claim 4 or 5, wherein the ID recording module comprises:
the checking unit is used for checking whether the input parameters of the asynchronous interface are correct or not;
and the ID recording unit is used for recording the ID information of the resources operated by the asynchronous interface if the verification unit verifies correctly.
7. An apparatus for capturing results of asynchronous interface execution, comprising:
a memory for storing a computer program;
a processor for executing the computer program to implement the method of capturing asynchronous interface execution results of any of claims 1 to 3.
8. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, implements a method of capturing asynchronous interface execution results as claimed in any of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910931252.9A CN110688102B (en) | 2019-09-29 | 2019-09-29 | Method, system, device and storage medium for capturing execution result of asynchronous interface |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910931252.9A CN110688102B (en) | 2019-09-29 | 2019-09-29 | Method, system, device and storage medium for capturing execution result of asynchronous interface |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110688102A CN110688102A (en) | 2020-01-14 |
| CN110688102B true CN110688102B (en) | 2022-03-22 |
Family
ID=69110973
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910931252.9A Active CN110688102B (en) | 2019-09-29 | 2019-09-29 | Method, system, device and storage medium for capturing execution result of asynchronous interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110688102B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111666184A (en) * | 2020-06-29 | 2020-09-15 | 腾讯科技（深圳）有限公司 | Solid state drive SSD hard disk test method and device and electronic equipment |
| CN113111283B (en) * | 2021-02-23 | 2023-11-10 | 北京联合信任技术服务有限公司 | Forensic server, forensic server method, storage medium, and program product |
| CN112905362A (en) * | 2021-03-31 | 2021-06-04 | 浙江太美医疗科技股份有限公司 | Method and system for transparently transmitting parameters between applications |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1790260A (en) * | 2004-12-15 | 2006-06-21 | 国际商业机器公司 | System and method for generating asynchronous interfaces and methods from synchronous interfaces and methods |
| CN101599027A (en) * | 2009-06-30 | 2009-12-09 | 中兴通讯股份有限公司 | A kind of thread pool management method and system thereof |
| CN102662742A (en) * | 2012-04-11 | 2012-09-12 | 华为技术有限公司 | Lock-based thread management method and thread management device |
| WO2014088541A1 (en) * | 2012-12-03 | 2014-06-12 | Hewlett-Packard Development Company, L.P. | Asynchronous framework for management of iaas |
| CN105893120A (en) * | 2016-04-21 | 2016-08-24 | 北京京东尚科信息技术有限公司 | Acquisition method and device for thread synchronization resources |
| CN108595331A (en) * | 2018-04-24 | 2018-09-28 | 杭州朗和科技有限公司 | Test method, medium, device and the computing device of asynchronous interface |
| WO2019039741A1 (en) * | 2017-08-23 | 2019-02-28 | 삼성전자 주식회사 | Operating method of operating system and electronic device supporting same |
| CN109491928A (en) * | 2018-11-05 | 2019-03-19 | 深圳乐信软件技术有限公司 | Buffer control method, device, terminal and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103365720B (en) * | 2012-03-28 | 2017-12-05 | 国际商业机器公司 | For dynamically adjusting the method and system of global Heap Allocation under multi-thread environment |
-
2019
- 2019-09-29 CN CN201910931252.9A patent/CN110688102B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1790260A (en) * | 2004-12-15 | 2006-06-21 | 国际商业机器公司 | System and method for generating asynchronous interfaces and methods from synchronous interfaces and methods |
| CN101599027A (en) * | 2009-06-30 | 2009-12-09 | 中兴通讯股份有限公司 | A kind of thread pool management method and system thereof |
| CN102662742A (en) * | 2012-04-11 | 2012-09-12 | 华为技术有限公司 | Lock-based thread management method and thread management device |
| WO2014088541A1 (en) * | 2012-12-03 | 2014-06-12 | Hewlett-Packard Development Company, L.P. | Asynchronous framework for management of iaas |
| CN105893120A (en) * | 2016-04-21 | 2016-08-24 | 北京京东尚科信息技术有限公司 | Acquisition method and device for thread synchronization resources |
| WO2019039741A1 (en) * | 2017-08-23 | 2019-02-28 | 삼성전자 주식회사 | Operating method of operating system and electronic device supporting same |
| CN108595331A (en) * | 2018-04-24 | 2018-09-28 | 杭州朗和科技有限公司 | Test method, medium, device and the computing device of asynchronous interface |
| CN109491928A (en) * | 2018-11-05 | 2019-03-19 | 深圳乐信软件技术有限公司 | Buffer control method, device, terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110688102A (en) | 2020-01-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110688102B (en) | Method, system, device and storage medium for capturing execution result of asynchronous interface | |
| US11102277B2 (en) | System and method for workflow orchestration for use with a cloud computing environment | |
| US8997088B2 (en) | Methods and systems for automated deployment of software applications on heterogeneous cloud environments | |
| US9712379B2 (en) | Robust cloud instance launching | |
| US7721153B2 (en) | System, method and program product for recovering from a failure | |
| US8171475B2 (en) | Intelligent retry method using remote shell | |
| US10171315B2 (en) | Orchestration process template for generation of orchestration process to tolerate errors | |
| AU2021206497B2 (en) | Method and apparatus for authority control, computer device and storage medium | |
| US11327846B2 (en) | System and method for backup and recovery of services in a cloud computing environment | |
| CA2974820A1 (en) | System and method for introducing functionality to an application for use with a network service | |
| CN112148315A (en) | Software deployment method, device, server and storage medium | |
| CN114237498B (en) | Snapshot generation method and system for cloud primary storage data volume | |
| CN109308184B (en) | Middleware installation and update method, device and computer readable storage medium | |
| US11645086B2 (en) | System and method for implementing a filesystem agent management solution | |
| US20120166893A1 (en) | Recording and Preventing Crash in an Appliance | |
| US11379320B2 (en) | Container recovery | |
| US10509646B2 (en) | Software update rollbacks using file system volume snapshots | |
| CN113810379B (en) | Exception handling method and multi-service system | |
| CN105790975A (en) | Service processing operation execution method and device | |
| CN111400094A (en) | Method, device, equipment and medium for restoring factory settings of server system | |
| CN111857744A (en) | Installation method, system, equipment and medium of super-fusion system | |
| CN113849432B (en) | Server firmware data storage method, starting method, device, equipment and medium | |
| JP2009199360A (en) | Server construction method, computer software for same method and storage medium | |
| Zenmyo et al. | A self-healing technique using reusable component-level operation knowledge | |
| CN114090427A (en) | System exception handling method and device |
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 |