CN114697371A - Remote calling method and device - Google Patents
Remote calling method and device Download PDFInfo
- Publication number
- CN114697371A CN114697371A CN202210384545.1A CN202210384545A CN114697371A CN 114697371 A CN114697371 A CN 114697371A CN 202210384545 A CN202210384545 A CN 202210384545A CN 114697371 A CN114697371 A CN 114697371A
- Authority
- CN
- China
- Prior art keywords
- processing result
- response message
- field
- exception
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 238000012545 processing Methods 0.000 claims abstract description 140
- 230000004044 response Effects 0.000 claims abstract description 97
- 230000008569 process Effects 0.000 claims abstract description 25
- 238000012546 transfer Methods 0.000 claims abstract description 16
- 238000004806 packaging method and process Methods 0.000 claims abstract description 10
- 230000005540 biological transmission Effects 0.000 claims description 8
- 230000002159 abnormal effect Effects 0.000 abstract description 13
- 238000005538 encapsulation Methods 0.000 abstract description 3
- 238000004590 computer program Methods 0.000 description 7
- 230000009471 action Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The application discloses a remote calling method, wherein a client sends a remote calling request to a server when the client carries out remote calling to the server, and the remote calling request comprises a request address and request parameters. And the server side processes according to the request address and the request parameter to obtain a processing result. And then packaging the processing result according to a predefined information transfer format to obtain a response message, and sending the response message to the client. The information transfer format defines fields included in the response message and field types corresponding to the fields. That is, no matter the processing result is normal or abnormal, the processing result can be encapsulated through a predefined information transfer format and then transferred to the client, so that the client can know the processing result, the client does not need to carry the encapsulation type of the response message when sending the remote call request, and the call process is simplified.
Description
Technical Field
The application relates to the technical field of data processing, in particular to a remote calling method and device.
Background
With the continuous development of internet technology, the traffic volume is larger and larger, and the performance of one machine cannot be met if the larger and larger traffic volume needs to be met, so that a plurality of machines can be used for dealing with a large-scale application scene. The business system is vertically split into a plurality of micro-services, and the micro-services are changed into a distributed architecture so as to better perform business processing.
Traditional micro-services adopt RestTemplate to realize remote calling among services, and remote calling based on RsetTemplate is complex in use and low in flexibility and affects calling efficiency.
Disclosure of Invention
In view of this, embodiments of the present application provide a remote invocation method and apparatus to implement an invocation framework based on Spring Cloud as a micro service, simplify invocation complexity, and improve invocation efficiency.
In order to solve the above problem, the technical solution provided by the embodiment of the present application is as follows:
in a first aspect of the present application, a remote invocation method is applied to a server, where the server provides a micro service for a client based on a Spring Cloud, and the method includes:
receiving a remote calling request sent by the client, wherein the remote calling request comprises a request address and a request parameter;
processing according to the request address and the request parameter to obtain a processing result;
packaging the processing result according to a predefined information transfer format to obtain a response message, wherein the information transfer format defines fields included in the response message and field types corresponding to the fields;
and sending the response message to the client.
In one possible implementation, the fields include one or more of a result field, a data field, an error coding field, an error prompt field, and an exception information field.
In a possible implementation manner, in response to that the processing result is an exception processing result, the result field is FALSE, and the exception information field carries exception information; and responding to the normal processing result of the processing result, wherein the result field in the response message is True, and the data field is used for carrying result data.
In a possible implementation manner, the encapsulating the processing result according to a predefined information delivery format to obtain a response message includes: and encapsulating the processing result according to a predefined information transmission format, and performing serialization processing on the encapsulated data to obtain a response message.
In one possible implementation, the messaging format is the JsonResult format; the status code of the response message is 200.
In a second aspect of the present application, there is provided a remote invocation method, which is applied to a client that requests a service from a server based on a Spring Cloud, and includes:
receiving a response message sent by a server, wherein the response message comprises a field reflecting a processing result;
decoding the response message by using a decoder to obtain a processing result;
and responding to the processing result as an exception processing result, acquiring exception information from the response message, and processing according to the exception information.
In a possible implementation manner, the decoding, by a decoder, the response message to obtain a processing result includes:
and performing deserialization processing and decoding on the response message by using a decoder to obtain a processing result.
In a possible implementation manner, the acquiring exception information from the response message in response to the processing result being an exception processing result, and performing processing according to the exception information includes:
acquiring exception information from the response message by using the decoder, packaging the exception information to obtain RPCException, and transmitting the RPCException to an exception handler;
and the exception handler processes the RPCException.
In one possible implementation, the method further includes:
acquiring prompt information carried by an error prompt field from the RPCException;
and displaying the prompt information to a user.
In one possible implementation, the decoder is an OpenFeign decoder.
In a third aspect of the present application, a remote invocation device is provided, where the remote invocation device is applied to a server, and the server provides a micro service for a client based on a Spring Cloud, where the remote invocation device includes: the device comprises a receiving unit, a processing unit, an encapsulating unit and a sending unit.
The receiving unit is used for receiving a remote calling request sent by the client, wherein the remote calling request comprises a request address and a request parameter;
the processing unit is used for processing according to the request address and the request parameter to obtain a processing result;
an encapsulating unit, configured to encapsulate the processing result according to a predefined information delivery format, to obtain a response message, where the information delivery format defines fields included in the response message and field types corresponding to the fields;
and the sending unit is used for sending the response message to the client.
In one possible implementation, the fields include one or more of a result field, a data field, an error coding field, an error prompt field, and an exception information field.
In a possible implementation manner, in response to that the processing result is an exception processing result, the result field is FALSE, and the exception information field carries exception information; and responding to the normal processing result of the processing result, wherein the result field in the response message is True, and the data field is used for carrying result data.
In a possible implementation manner, the encapsulating unit is specifically configured to encapsulate the processing result according to a preset information delivery format, and perform serialization processing on encapsulated data to obtain a response message.
In one possible implementation, the messaging format is the JsonResult format; the status code of the response message is 200.
In a fourth aspect of the present application, there is provided a remote invocation device, which is applied to a client, where the client requests a service from a server based on a Spring Cloud, and the remote invocation device includes: the device comprises a receiving unit, a decoding unit and a processing unit.
The receiving unit is used for receiving a response message sent by the server, wherein the response message comprises a field reflecting a processing result;
the decoding unit is used for decoding the response message by using a decoder to obtain a processing result;
and the processing unit is used for responding to the processing result as an exception processing result, acquiring exception information from the response message and processing according to the exception information.
In a possible implementation manner, the decoding unit is specifically configured to perform deserialization processing and decoding on the response message by using a decoder, so as to obtain a processing result.
In a possible implementation manner, the processing unit is specifically configured to acquire exception information from the response message by using the decoder, encapsulate the exception information to obtain RPCException, and transmit the RPCException to an exception handler; and the exception handler processes the RPCException.
In one possible implementation, the apparatus further includes: an acquisition unit and a display unit;
the obtaining unit is configured to obtain, from the RPCException, prompt information carried by an error prompt field;
and the display unit is used for displaying the prompt information to a user.
In one possible implementation, the decoder is an OpenFeign decoder.
In a fifth aspect of embodiments of the present application, there is provided an electronic device, including: a processor, a memory;
the memory for storing computer readable instructions or a computer program;
the processor is configured to read the computer readable instructions or the computer program to enable the electronic device to implement the remote invocation method of the first aspect or the second aspect.
In a sixth aspect of the present application, there is provided a computer-readable storage medium having stored therein instructions that, when run on a device, cause the device to perform the remote invocation method of the first or second aspect.
In a seventh aspect of the present application, there is provided a computer program product for causing a computer to perform the remote invocation method of the first or second aspect when the computer program product runs on the computer.
Therefore, the embodiment of the application has the following beneficial effects:
when a client side carries out remote calling to a server side in the embodiment of the application, the client side sends a remote calling request to the server side, and the remote calling request comprises a request address and request parameters. And the server side processes according to the request address and the request parameter to obtain a processing result. And then packaging the processing result according to a predefined information transfer format to obtain a response message, and sending the response message to the client. The information delivery format defines fields included in the response message and field types corresponding to the fields, for example, the defined fields include a result field, and the result field may reflect whether the call is successful or not. That is, no matter the processing result is normal or abnormal, the processing result can be encapsulated through a predefined information transfer format and then transferred to the client, so that the client can know the processing result, the client does not need to carry the encapsulation type of the response message when sending the remote call request, and the call process is simplified.
Drawings
Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;
fig. 2 is an interaction diagram of a remote invocation method provided in an embodiment of the present application;
fig. 3 is a structural diagram of a remote invocation device according to an embodiment of the present application;
fig. 4 is a structural diagram of another remote invocation device according to an embodiment of the application.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, embodiments accompanying the drawings are described in detail below.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description will first discuss technical terms related to the embodiments of the present application.
Remote calls, also known as Remote Procedure Calls (RPCs), are a request for services from a Remote computer over a network to enable access to Remote resources as well as local resources. For example, it refers to a process on computer a calling a process on another computer B, wherein the calling process on computer a is suspended and the called process on computer B starts executing, and when the value returns to computer a, the computer a process continues executing. The caller (computer a) can pass information to the callee (computer B) by using parameters, and then can get information by the returned results.
In traditional Java development, RestTemplate is usually used as a common scheme for remote invocation, which is essentially a tool for HTTP request, and provides common request templates including GET, POST, PUT, and the like. The caller realizes the remote calling based on HTTP by specifying three parameters of request address, request parameter and object type converted by HTTP response. However, since the caller's RestTemplate-based remote call needs to specify the request address and object type, it cannot make a remote call as if it were calling a local method.
Based on this, the application provides a remote calling method based on Spring Cloud, and a uniform information return format, namely an information transfer format, is predefined at a server. After the server side processes the remote call request sent by the client side to obtain the processing result, the processing result is packaged by using the predefined information transfer format, the definition of the information transfer format is not needed on the client side, and the call flow is simplified.
Referring to fig. 1, the application scenario provided in the embodiment of the present application is schematically illustrated, where the application scenario includes a caller a and a callee B. The caller A sends a remote call request to the callee B, and the callee B performs processing according to the remote call request to obtain a processing result. And if the processing result is an abnormal processing result, acquiring abnormal information, packaging the abnormal information according to a predefined information transmission format, and acquiring a response message. The called party B sends the response message to the calling party A, so that the calling party A analyzes the response message to obtain the exception information, and encapsulates the exception information into RPCException to throw the RPCException to the exception handler for processing. The exception handler will handle different processing depending on its own processing power.
To facilitate understanding of the technical solutions provided by the embodiments of the present application, the following description is made with reference to the accompanying drawings.
Referring to fig. 2, which is a flowchart of a remote invocation method provided in an embodiment of the present application, as shown in fig. 2, the method may include:
s201: the client sends a remote calling request to the server, wherein the remote calling request comprises a request address and request parameters.
In this embodiment, when a client remotely invokes a service provided by a server, a remote invocation request is sent to the server, where the remote invocation request includes a request address and a request parameter. The request address may be a Uniform Resource Locator (URL) of the web page, and the request parameter is used for information required by the server to provide the remote service.
S202: and the server side processes according to the request address and the request parameter to obtain a processing result.
After receiving a remote call request sent by a client, a server responds according to a request address and request parameters in the remote call request to obtain a processing result.
S203: and the server encapsulates the processing result according to a predefined information transmission format to obtain a response message.
And after the processing result is obtained, the server encapsulates the processing result according to a predefined information transmission format to obtain a response message. The predefined information transfer format defines fields included in the response message and field types corresponding to the fields. The information delivery format may be a JsonResult format. That is, the type of the return message is predefined at the server, and the return message is a defined return type regardless of whether the return message is a normal message or an abnormal message, so that the abnormal message can be carried in the result of the normal return (i.e., in the response message with the status code of 200).
In particular, the fields may include a result field, a data field, an error code field, an error prompt field, and an exception information field. The result field is used for indicating that the processing result is a normal processing result or an abnormal processing result; the error coding field is used for indicating that when the processing result is an exception processing result, the error coding field is used for supporting an exception type, for example, when the code is 1, the login timeout is represented, when the code is 2, the repeated login is represented, and the like; the error prompt field is used for indicating the displayed prompt information when the processing result is the abnormal processing result; and the exception information field is used for carrying detailed exception information when the processing result is an exception processing result. The error prompt field may include a first prompt field and a second prompt field, where prompt information carried by the first prompt field is used for displaying to a user, and prompt information carried by the second prompt field is used for transmitting to the system. Such as the information delivery format shown in table 1.
Table 1 information delivery format
| Type of field | Name of field | Meaning of a field |
| boolean | success | Whether the call was successful or not |
| Object | data | Returning result data |
| String | errCode | Error coding |
| String | errMsg | Error prompt message (for user to see) |
| String | sysErrMsg | System error prompt message |
| String | exception | Abnormal information |
Setting the success field as true for a normal processing result, and putting the returned data into the data; if the remote call is abnormal, the success field is set to false, the status code of the response message is set to 200, and the errCode field, the errMsg field, the sysErrMsg field, and the except field are filled. The state code of the response message is set to 200, which is used to indicate that the server side has processed the remote invocation request sent by the client side.
In an embodiment of the present application, an exception handler is preconfigured at the server, and is configured to, when a processing result is an exception handling result, obtain exception information, and package the exception information according to an information delivery format, to obtain a response message.
In one embodiment of the present application, when two processes communicate, various types of data can be sent, including text, pictures, audio, and video, but these data are transmitted over the network in binary form. When two Java processes communicate, serialization and deserialization processes are required to implement inter-process paired object transfer. Specifically, the sender converts the Java object into a byte object and then transmits the byte object over the network; the receiver needs to recover the Java object from the byte sequence. Optionally, the server encapsulates the processing result according to a preset information transfer format, and performs serialization processing on the encapsulated data to obtain the response message.
S204: and the server side sends a response message to the client side.
S205: and the client decodes the response message by using a decoder to obtain a processing result.
After receiving the response message sent by the server, the client decodes the response message by using a decoder of the client to obtain a processing result. Specifically, the response message is decoded by a decoder, and the information carried by each field is extracted from the response message. For example, the information carried by the success field is acquired, and the processing result is determined to be a normal processing result or an abnormal processing result through the information of the field. Wherein, the decoder is an OpenFeign decoder
In an embodiment of the present application, when the server side obtains the response message and performs serialization processing, the client side performs deserialization and decoding processing on the response message when parsing the response message by using the decoder, so as to obtain a processing result.
S206: and responding to the processing result as an exception processing result, the client acquires exception information from the response message by using a decoder and processes according to the exception information.
In this embodiment, when the response processing result is the exception processing result, that is, when the success field is False, the client acquires exception information from the response message by using the decoder, and performs processing according to the exception information.
Specifically, after the exception information is acquired, the decoder encapsulates the exception information to obtain RPCException, and transmits the RPCException to the exception handler, so that the exception handler processes the RPCException. The RPCException includes a plurality of information related to the exception, including information carried by an errCode field, an errMsg field, a sysErrMsg field, and an excepting field, for example.
In one embodiment of the present application, when the exception handler has the ability to handle the exception condition indicated by RPCException, then the exception condition is handled. And when the exception handler does not have the capability of handling the exception condition indicated by the RPCException, acquiring the prompt information carried by the error prompt field from the RPCException and displaying the prompt information.
Therefore, when the client performs remote calling to the server, the client sends a remote calling request to the server, wherein the remote calling request comprises a request address and a request parameter. And the server side processes according to the request address and the request parameter to obtain a processing result. And then packaging the processing result according to a predefined information transfer format to obtain a response message, and sending the response message to the client. The information delivery format defines fields included in the response message and field types corresponding to the fields, for example, the defined fields include a result field, and the result field may reflect whether the call is successful or not. That is, no matter the processing result is normal or abnormal, the processing result can be encapsulated through a predefined information transmission format and then transmitted to the client, so that the client can know the processing result, the client does not need to carry the encapsulation type of the response message when sending the remote call request, and the call process is simplified.
Based on the above method embodiment, an embodiment of the present application further provides a remote invocation device, which will be described below with reference to the accompanying drawings.
Referring to fig. 3, the remote invocation device provided in the embodiment of the present application is applied to a server, where the server provides micro services for a client based on a Spring Cloud, and the device 300 includes: a receiving unit 301, a processing unit 302, a packaging unit 303 and a transmitting unit 304.
A receiving unit 301, configured to receive a remote invocation request sent by the client, where the remote invocation request includes a request address and a request parameter;
a processing unit 302, configured to perform processing according to the request address and the request parameter, and obtain a processing result;
an encapsulating unit 303, configured to encapsulate the processing result according to a predefined information delivery format, to obtain a response message, where the information delivery format defines fields included in the response message and field types corresponding to the fields;
a sending unit 304, configured to send the response message to the client.
In one possible implementation, the fields include one or more of a result field, a data field, an error coding field, an error prompt field, an exception information field.
In a possible implementation manner, in response to that the processing result is an exception processing result, the result field is FALSE, and the exception information field carries exception information; and responding to the normal processing result of the processing result, wherein the result field in the response message is True, and the data field is used for carrying result data.
In a possible implementation manner, the encapsulating unit 303 is specifically configured to encapsulate the processing result according to a preset information delivery format, and perform serialization processing on the encapsulated data to obtain the response message.
In one possible implementation, the messaging format is the JsonResult format; the status code of the response message is 200.
It should be noted that, for implementation of each unit in this embodiment, reference may be made to related descriptions in the foregoing method embodiments, and details of this embodiment are not repeated herein.
Referring to fig. 4, which is another remote invocation device provided in the embodiment of the present application, the device 400 is applied to a client, where the client requests a service from a server based on a Spring Cloud, and the device includes: a receiving unit 401, a decoding unit 402 and a processing unit 403.
A receiving unit 401, configured to receive a response message sent by a server, where the response message includes a field reflecting a processing result;
a decoding unit 402, configured to decode the response message by using a decoder, to obtain a processing result;
and the processing unit 403, configured to, in response to the processing result being an exception handling result, obtain exception information from the response message, and perform processing according to the exception information.
In a possible implementation manner, the decoding unit 402 is specifically configured to perform deserialization processing and decoding on the response message by using a decoder, so as to obtain a processing result.
In a possible implementation manner, the processing unit 403 is specifically configured to acquire exception information from the response message by using the decoder, encapsulate the exception information to obtain RPCException, and transmit the RPCException to an exception handler; and the exception handler processes the RPCException.
In one possible implementation, the apparatus further includes: an acquisition unit and a display unit;
the obtaining unit is configured to obtain, from the RPCException, prompt information carried by an error prompt field;
and the display unit is used for displaying the prompt information to a user.
In one possible implementation, the decoder is an OpenFeign decoder.
It should be noted that, implementation of each unit in this embodiment may refer to the above method embodiment, and this embodiment is not described herein again.
In addition, an embodiment of the present application provides an apparatus, including: a processor, a memory;
the memory for storing computer readable instructions or a computer program;
the processor is configured to read the computer readable instructions or the computer program to enable the device to implement the data transmission method.
Embodiments of the present application provide a computer-readable storage medium including instructions or a computer program, which when run on a computer, cause the computer to perform the data transmission method described above.
It should be noted that, in the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the system or the device disclosed by the embodiment, the description is simple because the system or the device corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description.
It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
It is further 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 the process, method, article, or apparatus that comprises the element.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A remote calling method is applied to a server, and the server provides micro services for a client based on Spring Cloud, and the method comprises the following steps:
receiving a remote calling request sent by the client, wherein the remote calling request comprises a request address and a request parameter;
processing according to the request address and the request parameter to obtain a processing result;
packaging the processing result according to a predefined information transfer format to obtain a response message, wherein the information transfer format defines fields included in the response message and field types corresponding to the fields;
and sending the response message to the client.
2. The method of claim 1, wherein the fields comprise one or more of a result field, a data field, an error coding field, an error prompt field, and an exception information field.
3. The method of claim 2, wherein in response to the processing result being an exception processing result, the result field is FALSE and the exception information field carries exception information; and responding to the normal processing result of the processing result, wherein the result field in the response message is True, and the data field is used for carrying result data.
4. The method according to any one of claims 1 to 3, wherein said encapsulating the processing result according to a predefined information delivery format to obtain a response message comprises:
and packaging the processing result according to a predefined information transmission format, and performing serialization processing on the packaged data to obtain a response message.
5. The method of claim 1, wherein the messaging format is a JsonResult format; the status code of the response message is 200.
6. A remote calling method is applied to a client, the client requests a service from a server based on Spring Cloud, and the method comprises the following steps:
receiving a response message sent by a server, wherein the response message comprises a field reflecting a processing result;
decoding the response message by using a decoder to obtain a processing result;
and responding to the processing result as an exception processing result, acquiring exception information from the response message, and processing according to the exception information.
7. The method of claim 6, wherein decoding the response message with a decoder to obtain a processing result comprises:
and performing deserialization processing and decoding on the response message by using a decoder to obtain a processing result.
8. The method according to claim 6, wherein the obtaining exception information from the response message in response to the processing result being an exception processing result and performing processing according to the exception information includes:
acquiring exception information from the response message by using the decoder, packaging the exception information to obtain RPCException, and transmitting the RPCException to an exception handler;
and the exception handler processes the RPCException.
9. The method of claim 8, further comprising:
acquiring prompt information carried by an error prompt field from the RPCException;
and displaying the prompt information to a user.
10. The method of claim 9, wherein the decoder is an OpenFeign decoder.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210384545.1A CN114697371A (en) | 2022-04-13 | 2022-04-13 | Remote calling method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210384545.1A CN114697371A (en) | 2022-04-13 | 2022-04-13 | Remote calling method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114697371A true CN114697371A (en) | 2022-07-01 |
Family
ID=82143376
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210384545.1A Pending CN114697371A (en) | 2022-04-13 | 2022-04-13 | Remote calling method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114697371A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115065674A (en) * | 2022-08-03 | 2022-09-16 | 北京金堤科技有限公司 | Communication method and device |
| CN117555708A (en) * | 2024-01-11 | 2024-02-13 | 中国人民解放军国防科技大学 | Windows microservice framework program calling method, system and device |
| CN118034959A (en) * | 2024-04-10 | 2024-05-14 | 腾讯科技（深圳）有限公司 | Remote Procedure Call (RPC) service calling method and device and electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107241333A (en) * | 2017-06-13 | 2017-10-10 | 上海微烛信息技术有限公司 | Recognition methods, system, Network Security Device and the server of exception request |
| CN109614253A (en) * | 2018-12-12 | 2019-04-12 | 郑州云海信息技术有限公司 | A kind of method and device for realizing remote procedure call |
| CN112783049A (en) * | 2020-12-31 | 2021-05-11 | 西安邮电大学 | Lamp networking remote control system based on little service |
-
2022
- 2022-04-13 CN CN202210384545.1A patent/CN114697371A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107241333A (en) * | 2017-06-13 | 2017-10-10 | 上海微烛信息技术有限公司 | Recognition methods, system, Network Security Device and the server of exception request |
| CN109614253A (en) * | 2018-12-12 | 2019-04-12 | 郑州云海信息技术有限公司 | A kind of method and device for realizing remote procedure call |
| CN112783049A (en) * | 2020-12-31 | 2021-05-11 | 西安邮电大学 | Lamp networking remote control system based on little service |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115065674A (en) * | 2022-08-03 | 2022-09-16 | 北京金堤科技有限公司 | Communication method and device |
| CN115065674B (en) * | 2022-08-03 | 2023-03-24 | 北京金堤科技有限公司 | Communication method and device |
| CN117555708A (en) * | 2024-01-11 | 2024-02-13 | 中国人民解放军国防科技大学 | Windows microservice framework program calling method, system and device |
| CN117555708B (en) * | 2024-01-11 | 2024-03-26 | 中国人民解放军国防科技大学 | Windows microservice framework program calling method, system and device |
| CN118034959A (en) * | 2024-04-10 | 2024-05-14 | 腾讯科技（深圳）有限公司 | Remote Procedure Call (RPC) service calling method and device and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114697371A (en) | Remote calling method and device | |
| WO2017181823A1 (en) | Protocol conversion method, platform, and protocol conversion gateway | |
| US20160337290A1 (en) | Message Push Method and Apparatus | |
| KR102463014B1 (en) | Method and apparatus for interworking in heterogeneous systems | |
| CN112527525A (en) | Distributed event bus processing method based on message queue, terminal and medium | |
| WO2016127792A1 (en) | User event response method and device | |
| CN110753129A (en) | Message transmission method, system, device, equipment and computer readable storage medium | |
| CN110636124B (en) | VPP cluster management method and device, electronic equipment and storage medium | |
| CN109343975B (en) | Method and apparatus for inter-page asynchronous communication | |
| CN103297453A (en) | Method, browser end and system for achieving instant communication | |
| CN103888348B (en) | E-mail applications system and electron post transmission method, device | |
| CN114416075A (en) | Service processing method and device | |
| CN112596931B (en) | Cross-process communication method and device, electronic equipment and storage medium | |
| CN106911666B (en) | Wearable intelligent device and message processing method and system thereof | |
| CN107040613B (en) | Message transmission method and system | |
| CN111988418B (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN113867732A (en) | Message information processing method, system and storage medium | |
| CN111930531A (en) | Data processing method, data production method, data consumption method, data production device, data consumption device and data consumption medium | |
| CN106357713B (en) | Method for realizing remote procedure call, client device and server device | |
| CN111464824A (en) | Message sending method and system, server and storage medium | |
| CN106357654B (en) | Remote procedure calling method, device and communication system | |
| CN106454403B (en) | Data display method, equipment and system | |
| CN102843312B (en) | The sending and receiving method of instant message and device | |
| CN113051202A (en) | Interface adaptation method, device, electronic equipment and computer readable storage medium | |
| CN115473939A (en) | Page communication method and device based on customer relationship management CRM system |
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 |