CN111752720A - Asynchronous request disguising synchronous request method - Google Patents
Asynchronous request disguising synchronous request method Download PDFInfo
- Publication number
- CN111752720A CN111752720A CN202010615668.2A CN202010615668A CN111752720A CN 111752720 A CN111752720 A CN 111752720A CN 202010615668 A CN202010615668 A CN 202010615668A CN 111752720 A CN111752720 A CN 111752720A
- Authority
- CN
- China
- Prior art keywords
- result
- asynchronous
- class
- request
- processing
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/52—Program synchronisation; Mutual exclusion, e.g. by means of semaphores
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to the field of asynchronous request calling, and provides an asynchronous request disguised synchronous request method. The main idea is to let the back-end be asynchronous requests, but masquerade as synchronous requests to the front-end, which maintains business coherence. The main scheme includes that a front-end page requests a back-end interface; self-defining an asynchronous executor class, and defining asynchronous annotation @ Async in the class; defining a class of asynchronous processing results, wherein the class supports generic T, and generic T receives return result class; defining an isDone method in the asynchronous processing result class, and judging whether the asynchronous method is executed or not through the isDone method; a calling instance is newly built, and a corresponding fetching and returning processing result is obtained by judging whether the execution of the isDone method is completed or not in the instance; the front end obtains the processing result, if the result is normal, the result is displayed according to the requirement, if the result is abnormal, a single inquiry result request method is requested, the execution result is returned, and meanwhile, friendly prompt appears on the page to prompt the service to wait patiently.
Description
Technical Field
The invention relates to the field of asynchronous request calling, and provides an asynchronous request disguised synchronous request method.
Background
While the high efficiency and high speed correspondence are pursued more and more, some application embrace AI or process robots, and more of the intelligentized things are calculation, model training and anthropomorphic operation, which means that a large amount of operations exist behind the robots, and the time consumption is long, so that some api interfaces provided by the robots are asynchronously called, but business continuity is required in many business scenes, synchronous waiting results are required, and a method for processing asynchronous requests disguised as synchronous requests is generated based on the scenes;
disclosure of Invention
The invention relates to the field of asynchronous request calling, and provides an asynchronous request disguised synchronous request method, which is mainly used for solving the problem that the continuity of a business can be ensured only by waiting for an asynchronous return result because a back-end service is in an asynchronous calling mode while the continuity of the business needs to be maintained from top to bottom, and the method for solving the problem is as follows: the back-end is also an asynchronous request, but masquerades as a synchronous request to the front-end, which maintains business continuity while satisfying that the back-end must be an asynchronous request.
An asynchronous request masquerading synchronous request method comprises the following steps:
s1, requesting a rear-end interface by the front-end page;
s2, self-defining an asynchronous executor class, and using @ Async annotation on the corresponding service processing class to achieve the effect of single thread execution, namely asynchronous request;
s3, defining a class of asynchronous processing result, wherein the class supports a generic T, and the generic T receives the return result class;
s4, defining an isDone method in the asynchronous processing result class, and judging whether the asynchronous method is executed or not through the isDone method;
s5, newly building a calling instance, and obtaining a corresponding return processing result by judging whether the execution of the isDone method is completed in the instance;
s6, the front end obtains the processing result, if the result is normal, the result is displayed according to the requirement, if the result is abnormal, a single query result request method is requested, the method is a compensation mechanism, the execution result is returned when asynchronous execution is not completed, and meanwhile, a friendly prompt appears on the page to prompt the service to wait patiently;
and S7, setting the front end and the back end to keep long connection, and avoiding the overtime interruption of the front end and the back end.
In the above technical scheme: the step S1 includes the steps of:
step 1: newly building an API class, and defining a back-end remote interface URL in the API class;
step 2: calling an interface of a remote back end in a remote RPC mode;
in the above technical scheme: the step S2 includes the steps of:
step 1: creating a new class to obtain a user-defined asynchronous actuator class E;
step 2: declaring an Async annotation in the class E, automatically injecting the annotation into a pointing container when starting by using a project, and adding a surrounding travel tangent plane on the annotated method by using the spring AOP principle when initializing the container to generate a dynamic proxy class E so as to independently start a thread and independently execute the thread;
and step 3: newly building a service logic processing class A, and annotating by using @ Async on a method B of the service logic class A, so that the method B can be executed by a single thread during execution to achieve the asynchronous processing effect, and the method B is a third party API interface requiring asynchronous calling;
in the above technical scheme: the step S3 includes the steps of:
step 1: newly creating a Result type Result, wherein the Result is a user-defined Result public type, and the method comprises the following steps: returning a code, information msg, content data and Result special receiving and processing results;
step 2: remotely calling a third-party API in a method B in a business logic processing class A annotated by @ Async, setting a processing time duration timeout, inquiring an asynchronous callback Result if the time exceeds the processing time duration, and creating a Result to receive the processing Result if the time duration exceeds the processing time duration;
and step 3: the processed Result class is managed into an E class by self-defining a generic T of the asynchronous executor E class;
and 4, step 4: and taking the user-defined asynchronous executor class E as a return value of the service logic processing class A, and returning to an upstream calling interface.
In the above technical scheme: the step S4 includes the steps of:
step 1: defining an isDone method in a user-defined asynchronous executor E class, and judging whether the asynchronous processing flow is executed or not through the isDone method;
step 2: the isDone method is false if the result is normal, and if the result is abnormal or null;
in the above technical scheme: the step S5 includes the steps of:
step 1: a class C is newly established, wherein the class C provides RPC service class for the outside and is also a calling party of the service logic processing class A;
step 2: judging whether the Result of asynchronous processing is more than or not in the C type by judging the isDone () method of the asynchronous executor E, if so, obtaining a return Result, obtaining a public Result by using a get () method, and returning the public Result to the front end;
and step 3: if the loop is not taken, the compensation mechanism can set a timeout to prevent the loop result from being completed asynchronously, but it should be noted that the compensation mechanism needs a loop time limit to avoid dead loop.
In the above technical scheme: the step S6 includes the steps of:
step 1: acquiring a return Result on a front-end page, and if the code is a successful identification code, acquiring data and displaying the data as required;
step 2: if the code is failure, showing a failure reason msg;
and step 3: if the code is not used for acquiring data, providing an interface special for inquiring a processing result for inquiry, and simultaneously displaying a friendly prompt on a page to prompt service patience waiting;
in the above technical scheme: the step S7 includes the steps of:
step 1: and setting nginx to keep long connection, avoiding the front end from requesting timeout interruption, and setting proxy _ read _ timeout 300 of the nginx.
Because the invention adopts the technical scheme, the invention has the following beneficial effects:
the scheme is suitable for a scene that a back-end interface asynchronously calls a third party api, but a service system needs to synchronously receive a result to keep service continuity;
adapting to scenes, and being capable of seamlessly accessing each system, the method can be used:
the method is suitable for scenes of asynchronous call and asynchronous return and asynchronous call and synchronous return, and the light-weight component can be used as long as the scenes correspond to each other, can be seamlessly accessed into each system, can reduce the coupling between the systems, and can improve the flexibility and the responsiveness of service change of the systems.
Third, the operation of the business is not sensed, although the internal operation is asynchronous calling, the operation of the business is not divided into a plurality of steps, and the fluency and the continuity of the business are guaranteed.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail with reference to the following embodiments. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.
The detailed description of the embodiments of the present invention is not intended to limit the scope of the invention as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present invention without making any creative effort, shall fall within the protection scope of the present invention.
It is noted that 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.
An asynchronous request masquerading synchronous request method comprises the following steps:
s1, requesting a rear-end interface by the front-end page;
s2, self-defining an asynchronous executor class, and using @ Async annotation on the corresponding service processing class to achieve the effect of single thread execution, namely asynchronous request;
s3, defining a class of asynchronous processing result, wherein the class supports a generic T, and the generic T receives the return result class;
s4, defining an isDone method in the asynchronous processing result class, and judging whether the asynchronous method is executed or not through the isDone method;
s5, newly building a calling instance, and obtaining a corresponding return processing result by judging whether the execution of the isDone method is completed in the instance;
s6, the front end obtains the processing result, if the result is normal, the result is displayed according to the requirement, if the result is abnormal, a single query result request method is requested, the method is a compensation mechanism, the execution result is returned when asynchronous execution is not completed, and meanwhile, a friendly prompt appears on the page to prompt the service to wait patiently;
and S7, setting the front end and the back end to keep long connection, and avoiding the overtime interruption of the front end and the back end.
In the above technical scheme: the step S1 includes the steps of:
step 1: newly building an API class, and defining a back-end remote interface URL in the API class;
step 2: calling an interface of a remote back end in a remote RPC mode;
in the above technical scheme: the step S2 includes the steps of:
step 1: creating a new class to obtain a user-defined asynchronous actuator class E;
step 2: declaring an Async annotation in the class E, automatically injecting the annotation into a pointing container when starting by using a project, and adding a surrounding travel tangent plane on the annotated method by using the spring AOP principle when initializing the container to generate a dynamic proxy class E so as to independently start a thread and independently execute the thread;
and step 3: newly building a service logic processing class A, and annotating by using @ Async on a method B of the service logic class A, so that the method B can be executed by a single thread during execution to achieve the asynchronous processing effect, and the method B is a third party API interface requiring asynchronous calling;
in the above technical scheme: the step S3 includes the steps of:
step 1: newly creating a Result type Result, wherein the Result is a user-defined Result public type, and the method comprises the following steps: returning a code, information msg, content data and Result special receiving and processing results;
step 2: remotely calling a third-party API in a method B in a business logic processing class A annotated by @ Async, setting a processing time duration timeout, inquiring an asynchronous callback Result if the time exceeds the processing time duration, and creating a Result to receive the processing Result if the time duration exceeds the processing time duration;
and step 3: the processed Result class is managed into an E class by self-defining a generic T of the asynchronous executor E class;
and 4, step 4: and taking the user-defined asynchronous executor class E as a return value of the service logic processing class A, and returning to an upstream calling interface.
In the above technical scheme: the step S4 includes the steps of:
step 1: defining an isDone method in a user-defined asynchronous executor E class, and judging whether the asynchronous processing flow is executed or not through the isDone method;
step 2: the isDone method is false if the result is normal, and if the result is abnormal or null;
in the above technical scheme: the step S5 includes the steps of:
step 1: a class C is newly established, wherein the class C provides RPC service class for the outside and is also a calling party of the service logic processing class A;
step 2: judging whether the Result of asynchronous processing is more than or not in the C type by judging the isDone () method of the asynchronous executor E, if so, obtaining a return Result, obtaining a public Result by using a get () method, and returning the public Result to the front end;
and step 3: if the loop is not taken, the compensation mechanism can set a timeout to prevent the loop result from being completed asynchronously, but it should be noted that the compensation mechanism needs a loop time limit to avoid dead loop.
In the above technical scheme: the step S6 includes the steps of:
step 1: acquiring a return Result on a front-end page, and if the code is a successful identification code, acquiring data and displaying the data as required;
step 2: if the code is failure, showing a failure reason msg;
and step 3: if the code is not used for acquiring data, providing an interface special for inquiring a processing result for inquiry, and simultaneously displaying a friendly prompt on a page to prompt service patience waiting;
in the above technical scheme: the step S7 includes the steps of:
step 1: and setting nginx to keep long connection, avoiding the front end from requesting timeout interruption, and setting proxy _ read _ timeout 300 of the nginx.
Claims (8)
1. An asynchronous request masquerading synchronous request method is characterized by comprising the following steps:
s1, requesting a rear-end interface by the front-end page;
s2, self-defining an asynchronous executor class, and using @ Async annotation on the corresponding service processing class to achieve the effect of single thread execution, namely asynchronous request;
s3, defining a class of asynchronous processing result, wherein the class supports a generic T, and the generic T receives the return result class;
s4, defining an isDone method in the asynchronous processing result class, and judging whether the asynchronous method is executed or not through the isDone method;
s5, newly building a calling instance, and obtaining a corresponding return processing result by judging whether the execution of the isDone method is completed in the instance;
s6, the front end obtains the processing result, if the result is normal, the result is displayed according to the requirement, if the result is abnormal, a single query result request method is requested, the method is a compensation mechanism, the execution result is returned when asynchronous execution is not completed, and meanwhile, a friendly prompt appears on the page to prompt the service to wait patiently;
and S7, setting the front end and the back end to keep long connection, and avoiding the overtime interruption of the front end and the back end.
2. The asynchronous request masquerading synchronous request method as recited in claim 1, wherein the step S1 comprises the steps of:
step 1: newly building an API class, and defining a back-end remote interface URL in the API class;
step 2: and calling an interface of a remote back end in a remote RPC mode.
3. The asynchronous request masquerading synchronous request method as recited in claim 1, wherein the step S2 comprises the steps of:
step 1: creating a new class to obtain a user-defined asynchronous actuator class E;
step 2: declaring an Async annotation in the class E, automatically injecting the annotation into a pointing container when starting by using a project, and adding a surrounding travel tangent plane on the annotated method by using the spring AOP principle when initializing the container to generate a dynamic proxy class E so as to independently start a thread and independently execute the thread;
and step 3: the newly-built business logic processes the class A and notes by using @ Async on a method B of the business logic class A, so that the method B can be executed by a single thread during execution to achieve the asynchronous processing effect, and the method B is a third party API interface requiring asynchronous calling.
4. The asynchronous request masquerading synchronous request method as recited in claim 1, wherein the step S3 comprises the steps of:
step 1: newly creating a Result type Result, wherein the Result is a user-defined Result public type, and the method comprises the following steps: returning a code, information msg, content data and Result special receiving and processing results;
step 2: remotely calling a third-party API in a method B in a business logic processing class A annotated by @ Async, setting a processing time duration timeout, inquiring an asynchronous callback Result if the time exceeds the processing time duration, and creating a Result to receive the processing Result if the time duration exceeds the processing time duration;
and step 3: the processed Result class is managed into an E class by self-defining a generic T of the asynchronous executor E class;
and 4, step 4: and taking the user-defined asynchronous executor class E as a return value of the service logic processing class A, and returning to an upstream calling interface.
5. The asynchronous request masquerading synchronous request method as recited in claim 1, wherein the step S4 comprises the steps of:
step 1: defining an isDone method in a user-defined asynchronous executor E class, and judging whether the asynchronous processing flow is executed or not through the isDone method;
step 2: the isDone method is false if the result is normal, or if the result is abnormal or null.
6. The asynchronous request masquerading synchronous request method as recited in claim 1, wherein the step S5 comprises the steps of:
step 1: a class C is newly established, wherein the class C provides RPC service class for the outside and is also a calling party of the service logic processing class A;
step 2: judging whether the Result of asynchronous processing is more than or not in the C type by judging the isDone () method of the asynchronous executor E, if so, obtaining a return Result, obtaining a public Result by using a get () method, and returning the public Result to the front end;
and step 3: if the loop is not taken, the compensation mechanism can set a timeout to prevent the loop result from being completed asynchronously, but it should be noted that the compensation mechanism needs a loop time limit to avoid dead loop.
7. The asynchronous request masquerading synchronous request method as recited in claim 1, wherein the step S6 comprises the steps of:
step 1: acquiring a return Result on a front-end page, and if the code is a successful identification code, acquiring data and displaying the data as required;
step 2: if the code is failure, showing a failure reason msg;
and step 3: if the code is not used for acquiring data, an interface special for inquiring a processing result is provided for inquiring, and meanwhile, a friendly prompt is displayed on a page to prompt the service to wait patiently.
8. The asynchronous request masquerading synchronous request method as recited in claim 1, wherein the step S7 comprises the steps of:
step 1: and setting nginx to keep long connection, avoiding the front end from requesting timeout interruption, and setting proxy _ read _ timeout 300 of the nginx.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010615668.2A CN111752720B (en) | 2020-06-27 | 2020-06-27 | Asynchronous request disguising synchronous request method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010615668.2A CN111752720B (en) | 2020-06-27 | 2020-06-27 | Asynchronous request disguising synchronous request method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111752720A true CN111752720A (en) | 2020-10-09 |
| CN111752720B CN111752720B (en) | 2023-07-07 |
Family
ID=72678455
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010615668.2A Active CN111752720B (en) | 2020-06-27 | 2020-06-27 | Asynchronous request disguising synchronous request method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111752720B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113434582A (en) * | 2021-06-24 | 2021-09-24 | 平安国际智慧城市科技股份有限公司 | Service data processing method and device, computer equipment and storage medium |
| CN114928663A (en) * | 2022-06-02 | 2022-08-19 | 蜂助手股份有限公司 | Method and device for recognizing callback message |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060206903A1 (en) * | 2005-03-10 | 2006-09-14 | Microsoft Corporation | System data interfaces, related architectures, print system data interfaces and related print system architectures |
| US20070130574A1 (en) * | 2005-12-01 | 2007-06-07 | Apptran Software | Method and system for event-based remote procedure call implementation in a distributed computing system |
| US20090172636A1 (en) * | 2006-03-31 | 2009-07-02 | Tim Griffith | Interactive development tool and debugger for web services |
| WO2009143105A2 (en) * | 2008-05-20 | 2009-11-26 | Raytheon Company | Method and apparatus for providing a synchronous interface for an asynchronous service |
| US20120260261A1 (en) * | 2011-04-07 | 2012-10-11 | Microsoft Corporation | Asynchronous callback driven messaging request completion notification |
| CN109656724A (en) * | 2018-09-27 | 2019-04-19 | 深圳壹账通智能科技有限公司 | Method for processing business, device, equipment and computer readable storage medium |
| CN110166730A (en) * | 2019-06-06 | 2019-08-23 | 苏州科达科技股份有限公司 | A kind of request processing method, device, equipment and readable storage medium storing program for executing |
| CN110611687A (en) * | 2018-06-15 | 2019-12-24 | 武汉安天信息技术有限责任公司 | Remote procedure call implementation method based on Redis and related device |
-
2020
- 2020-06-27 CN CN202010615668.2A patent/CN111752720B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060206903A1 (en) * | 2005-03-10 | 2006-09-14 | Microsoft Corporation | System data interfaces, related architectures, print system data interfaces and related print system architectures |
| US20070130574A1 (en) * | 2005-12-01 | 2007-06-07 | Apptran Software | Method and system for event-based remote procedure call implementation in a distributed computing system |
| US20090172636A1 (en) * | 2006-03-31 | 2009-07-02 | Tim Griffith | Interactive development tool and debugger for web services |
| WO2009143105A2 (en) * | 2008-05-20 | 2009-11-26 | Raytheon Company | Method and apparatus for providing a synchronous interface for an asynchronous service |
| US20120260261A1 (en) * | 2011-04-07 | 2012-10-11 | Microsoft Corporation | Asynchronous callback driven messaging request completion notification |
| CN110611687A (en) * | 2018-06-15 | 2019-12-24 | 武汉安天信息技术有限责任公司 | Remote procedure call implementation method based on Redis and related device |
| CN109656724A (en) * | 2018-09-27 | 2019-04-19 | 深圳壹账通智能科技有限公司 | Method for processing business, device, equipment and computer readable storage medium |
| CN110166730A (en) * | 2019-06-06 | 2019-08-23 | 苏州科达科技股份有限公司 | A kind of request processing method, device, equipment and readable storage medium storing program for executing |
Non-Patent Citations (3)
| Title |
|---|
| KLAUS V. GLEISSENTHALL 等: "\"Pretend synchrony: synchronous verification of asynchronous distributed programs\"", 《 PROCEEDINGS OF THE ACM ON PROGRAMMING LANGUAGES》 * |
| THOMAS HERAULT 等: ""practical scalable consensus for pseudo-synchronous distributed systems"", 《SC\'15》 * |
| 刘嫣如: ""中小银行事后监督系统的设计与实现"", 中国优秀硕士学位论文全文数据库 (信息科技辑) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113434582A (en) * | 2021-06-24 | 2021-09-24 | 平安国际智慧城市科技股份有限公司 | Service data processing method and device, computer equipment and storage medium |
| CN114928663A (en) * | 2022-06-02 | 2022-08-19 | 蜂助手股份有限公司 | Method and device for recognizing callback message |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111752720B (en) | 2023-07-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP2019207710A (en) | Interaction method between smart voice apparatuses, device, apparatus, and storage medium | |
| CN111752720A (en) | Asynchronous request disguising synchronous request method | |
| US10296373B2 (en) | Generic wait service: pausing and resuming a plurality of BPEL processes arranged in correlation sets by a central generic wait server | |
| WO2017028719A1 (en) | Metadata output method, client side, and metadata server | |
| WO2019047441A1 (en) | Communication optimization method and system | |
| US20130117414A1 (en) | Dynamic Interface to Read Database Through Remote Procedure Call | |
| US7970814B2 (en) | Method and apparatus for providing a synchronous interface for an asynchronous service | |
| CN106686021B (en) | Service calling method and gateway | |
| WO2023197656A1 (en) | Interface element positioning method, electronic device and storage medium | |
| CN110333919B (en) | Method and equipment for presenting social object information | |
| CN113065054B (en) | Request processing method, request processing device, electronic equipment and storage medium | |
| CN114006946B (en) | Method, device, equipment and storage medium for processing homogeneous resource request | |
| CN109729121B (en) | Cloud storage system and method for realizing custom data processing in cloud storage system | |
| CN110995817B (en) | Request callback method and device and client equipment | |
| CN111461659A (en) | Personal contract business processing method, device, medium and equipment based on big data | |
| WO2021068382A1 (en) | Multi-window operation control method and apparatus, and device and storage medium | |
| US9992528B2 (en) | System and methods thereof for displaying video content | |
| CN111338829A (en) | Method and device for calling remote procedure call service | |
| CN110874176B (en) | Interaction method, storage medium, operating system and device | |
| CN111274176B (en) | Information processing method, electronic equipment, system and storage medium | |
| CN114205366A (en) | Cross-platform data synchronization method and device, equipment, medium and product thereof | |
| CN111125427A (en) | Video file reading method and device, electronic equipment and medium | |
| JP2022551454A (en) | Stored procedure execution method, device, database system and storage medium | |
| CN111461658A (en) | Enterprise contract business processing method, device, medium and equipment based on big data | |
| US20130159551A1 (en) | Parameter Driven Value Conversion Framework In Client/Server Architectures |
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 |