Component calling method, device and system, server and readable medium

Abstract

An embodiment of the invention discloses a component calling method, a component calling device, a component calling system, a server and a readable medium. The component calling method comprises thefollowing steps of: receiving a component calling request comprising callback parameters; transmitting the component calling request to a component providing application server through a created firstthread, enabling the component providing application server to generate a calling success message and calls a component method, transmitting the calling success message to a component market server,and calling a result of calling the component method back to the component calling application server according to the callback parameters; and receiving the calling success message, terminating the first thread according to the calling success message, and transmitting the calling success message to a component calling application server, so that the component calling application server waits forthe result called back by the component providing application server. According to the component calling method, the component calling device, the component calling system, the server and the readable medium provided by the embodiment of the invention, normal calling of the component is ensured, and the stability and the resource utilization rate of the servers in the component market are improved.

Description

technical field [0001] The embodiment of the present invention relates to computer technology, and in particular to a component calling method, device, system, server and readable medium. Background technique [0002] In the prior art, the commonly used component invocation method flow is mainly: the component invocation application server sends a component invocation request to the component providing application server through the component market; the component providing application server also successfully invokes the invocation result to the component invoking application through the component market server. [0003] In the course of realizing the present invention, the inventor finds that there are at least the following problems in the prior art: [0004] When thread blocking occurs in the component market, it may lead to the inability to normally receive the invocation request of the new component invoking the application server, and / or the inability to normally rec...

AI Technical Summary

Problems solved by technology

[0004] When thread blocking occurs in the component market, it may lead to the inability to normally receive the invocation request of the new component invoking the application server, and / or the inability to normally receive the invocation result sent by the application server provided by the component, which wastes the thread resources of the server in the component market, and The normal invocation of components cannot be guaranteed; when a large number of components in parallel received by the component market call the application server, the thread resources of the server in the component market may be exhausted, which may cause the performance of each interface in the component market to degrade or even become unavailable, making the component Abnormal call or even the server crash of the component market, that is, the server stability of the component market is poor

Images