WO2019104973A1

WO2019104973A1 - Cross-language invoking method, server, and storage medium

Info

Publication number: WO2019104973A1
Application number: PCT/CN2018/089135
Authority: WO
Inventors: 李刚; 刘汉玉
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-11-30
Filing date: 2018-05-31
Publication date: 2019-06-06
Also published as: CN108255615B; CN108255615A

Abstract

A cross-language invoking method, a server, and a storage medium. The method comprises: receive interface information, a host cluster IP address, and a port address of a service side, and write the host cluster IP address and the port address of the service side into a registration center (S10); create an interface class according to the interface information, and save the interface class to a storage (S20); an invoking class loader loads the interface class to a memory (S30); inquiry, according to the interface information, service information provided by the service side from the registration center (S40); create, according to the service information, a proxy class corresponding to the interface class (S50); generate a unique URL according to the proxy class (S60); receive a request in an http protocol format sent from a requester (S70); convert the request into a hessian protocol format (S80); find a corresponding proxy class according to the URL address in the request, and find a corresponding invoker entity according to a corresponding relationship between the proxy class and the interface class (S90); the invoker entity sends the request in the hessian protocol format to a corresponding host of the service side to initiate a service access request (S100), so as to implement cross-language invoking.

Description

Cross-language calling method, server and storage medium

Priority claim

This application claims the priority of the Chinese Patent Application entitled "Cross-Language Invoking Method, Server and Storage Media", filed on November 30, 2017, with the application number of 201711239546.2, the entire contents of which are incorporated by reference. The way it is combined with this application.

Technical field

The present application relates to the field of service invocation, and in particular, to a cross-language calling method, a server, and a computer readable storage medium.

Background technique

Dubbo is a distributed service framework based on Alibaba's open source, dedicated to improving performance and transparent remote procedure call protocol (RPC) service invocation scheme, and Service-Oriented Architecture (Service-Oriented Architecture, SOA) governance program. Currently, the service platform based on the dubbo framework in the industry does not support cross-language service calls. That is to say, in the service platform based on the dubbo framework, the service party can only provide services using the java language, and the requesting party can only use the java language to invoke the service. This makes the service call language single, limiting service calls.

Summary of the invention

In view of the above, the present application provides a cross-language calling method, a server, and a computer readable storage medium, which are compatible with languages such as java, C++, python, ruby, etc., and perform cross-language calls.

To achieve the above objective, the present application provides a cross-language calling method, the method comprising:

Receiving the interface information of the servant, the host cluster IP address and the port address, and writing the host cluster IP address and port address of the servant to the registration center;

Creating an interface class according to the interface information, and saving to the memory;

Calling the class loader to load the interface class from memory into memory;

Querying, according to the interface information, the service information provided by the service party from the registration center;

Creating a proxy class corresponding to the above interface class according to the service information that is queried;

Generate a unique Uniform Relocation Locator (URL) based on the proxy class;

Receiving a service call request in the http protocol format issued by the requesting party;

Convert the service invocation request from the http protocol format to the hessian protocol format;

Find the corresponding proxy class according to the URL address in the call request, and find the corresponding invoker entity according to the correspondence between the proxy class and the interface class;

The service call request of the hessian protocol format is sent by the invoker entity to the corresponding host of the service party to initiate a service access request.

In addition, the present application also provides a server, the server comprising: a memory, a processor, and a cross-language calling program stored on the memory and executable on the processor, the cross-language calling program being processed The device is executed to implement the following steps:

Calling the class loader to load the interface class from memory into memory;

Generate a unique URL based on the proxy class;

In addition, in order to achieve the above object, the present application further provides a computer readable storage medium including a cross-language calling program, which is implemented as described above when executed by a processor Call any step in the method across languages.

The cross-language calling method, the server and the computer readable storage medium proposed by the application, by receiving the interface information of the servant, the host cluster IP address and the port address, write the servant's host cluster IP address and port address into the registration center, and then Create an interface class according to the interface information, save to the memory, call the class loader to load the interface class from the memory into the memory, and then query the service information provided by the service party from the registry according to the interface information, and create a proxy class corresponding to the interface class. According to the proxy class, a unique URL is generated, and finally the service call request in the http protocol format sent by the requester is received, and the service call request is converted from the http protocol format to the hessian protocol format, and the corresponding proxy class is found according to the URL address in the call request. According to the corresponding relationship between the proxy class and the interface class, the corresponding invoker entity is found, and the invoker protocol sends the service call request of the hessian protocol format to the corresponding host of the service party to initiate a service access request, and the hessian protocol is an open source and a general protocol. Hessian association with the service party In the case of the discussion, the service party can implement services in multiple languages such as C, C++, PHYTHON, etc., thereby solving the problem that the service party and the requester invoke a single language, and realize cross-language invocation.

DRAWINGS

1 is a schematic diagram of a preferred embodiment of a server of the present application;

2 is a schematic diagram of an application environment of a cross-language calling method;

3 is a block diagram showing a preferred embodiment of the cross-language calling program in FIG. 1 or FIG. 2;

4 is a flow chart of a preferred embodiment of a cross-language invocation method of the present application.

The implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings.

Detailed ways

It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

As shown in FIG. 1, it is a schematic diagram of a preferred embodiment of the server 1 of the present application.

In this embodiment, the server 1 may be a server, a smart phone, a tablet computer, a personal computer, a portable computer, and other electronic devices having computing functions.

The server 1 includes a memory 11, a processor 12, a network interface 13, a communication bus 14, and a cross-language invocation program 10 stored on the memory 11 and executable on the processor 12.

The network interface 13 can optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). Communication bus 14 is used to implement connection communication between these components.

The memory 11 includes at least one type of readable storage medium. The at least one type of readable storage medium may be a non-volatile storage medium such as a flash memory, a hard disk, a multimedia card, a card type memory, or the like. In some embodiments, the memory 11 may be an internal storage unit of the server 1, such as a hard disk of the server 1. In other embodiments, the memory 11 may also be an external storage unit of the server 1, such as a plug-in hard disk equipped on the server 1, a smart memory card (SMC), and a secure digital ( Secure Digital, SD) cards, flash cards (FC cards), etc.

In this embodiment, the memory 11 can be used not only for storing application software installed on the server 1 and various types of data, such as a cross-language calling program 10, a binary codec specification, etc., but also for temporarily storing Output or data to be output, such as interface classes.

The processor 12, in some embodiments, may be a Central Processing Unit (CPU), microprocessor or other data processing chip for running program code or processing data stored in the memory 11, such as performing cross-language calls. The computer program code of the program 10 and the codec of the request message binary, and the like.

Preferably, the server 1 may also include a display, which may be referred to as a display screen or display unit. In some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an Organic Light-Emitting Diode (OLED) touch sensor. The display is used to display information processed in the server 1 and a work interface for displaying visualizations.

Preferably, the server 1 may further include a user interface, and the user interface may include an input unit such as a keyboard, a voice output device such as an audio, a headphone, and the like.

In the embodiment of the server 1 shown in FIG. 1, the program code of the cross-language invocation program 10 is stored in the memory 11 as a computer storage medium, and when the processor 12 executes the program code of the cross-language invocation program 10, the following steps are implemented:

Calling the class loader to load the interface class from memory into memory;

Generate a unique URL based on the proxy class;

In this embodiment, as shown in FIG. 2, it is a schematic diagram of an application environment of a cross-language invocation method. The server 1 provides a service page 2 for receiving interface information, a host cluster IP address, and a port address filled in by the service party 3. The interface information is obtained by the registration center 5 issuing service information before the server 3 logs in to the server 1. After receiving the interface information, the host cluster IP address, and the port address filled in by the servant 3, the cross-language invoking program 10 writes the host cluster IP address and port address of the servant 3 to the registration center 5. For example, when the service provider S wants to provide a face recognition service on the server, the service information is first published in the zookeeper. After receiving the service information, the zookeeper returns an interface information to the service provider S. The server S fills in the interface information, the host cluster IP address, and the port address on the service page of the server, and the server writes the host cluster IP address and port address of the face recognition of the server S to the zookeeper.

The cross-language caller 10 creates an interface class based on the received interface information. The interface information provided by the service party includes a package name, a class name, and a method name. Therefore, the interface class defines a package name, a class name, a method name, a request parameter, and a return parameter. E.g:

Save the generated interface class to local storage, such as hard disk, disk, and so on. The interface class created is to expose the service of the servant 3 to the port of the requester 4, which is convenient to call.

The cross-language caller 10 calls the class loader to load the interface class from local storage into virtual machine memory. The generated interface class is only stored in the local memory. When the interface class is used, the cross-language caller 10 loads the interface class into the virtual machine memory by calling the class loader. Suppose you need to call the interface class of the servant S, start the virtual machine, and then load the interface class of the servant S from the hard disk to the running memory of the system.

The cross-language invoking program 10 queries the service center-provided service information from the registry 5 based on the interface information. For example, after receiving the interface information filled in by the service party S, the cross-language invoking program queries the zookeeper for the service information about the face recognition of the service party S.

The cross-language caller 10 creates a proxy class corresponding to the above interface class based on the queried service information. Wherein, if there are multiple hosts providing services under the servant 3 interface, the corresponding proxy class also has multiple invoker entities associated with multiple hosts. For example, the cross-language caller automatically rewrites the dubbo initialization process based on the service information to create a dynamic proxy class corresponding to the interface class. Bind the proxy class to the interface class.

The cross-language caller 10 generates a unique URL based on the created proxy class. Among them, the URL generation rule is to automatically generate a unique URL address according to each method name. Bind the unique URL address to the corresponding interface class. The URL is the address of the web page and consists of two main parts: the protocol and the destination. The agreement includes http, ftp, telnet, etc. The destination can be a file name, a directory name, or the name of a computer. For example, the cross-language caller binds the unique URL address generated by the proxy class to the interface class on the virtual machine so that requester A can find the servant S when searching for the service.

When the requesting party 4 needs to apply for a service, the requesting party 4 sends a service invocation request in the http protocol format to the cross-language invoking program 10, and the cross-language invoking program 10 receives the service invoking request in the http protocol format issued by the requesting party 4. The service invocation request is composed of a request method URI protocol/version, a request header, and a request body. For example, the requester A sends a request to the face recognition service that sends the http protocol format based on the dubbo platform.

The cross-language caller 10 converts the service call request from the http protocol format to the hessian protocol format. The hessian is a lightweight remoting onhttp tool that provides RMI functionality using a simple method. Compared to WebService, Hessian is simpler and faster. The binary RPC protocol is adopted, which is more suitable for transmitting binary data. The cross-language caller 10 and the servant 3 predetermine the binary codec specification of the service call request, and the hessian binary-encodes the service call request through a predetermined binary codec specification to generate a binary code stream. The URL address in the service call request is read according to the generated binary stream. The hessian protocol is an open source, general-purpose protocol. In the case where the cross-language calling program 10 and the servant 3 implement the hessian protocol, the requesting party 4 can make service calls to the servant 3 in various languages such as java, C++, python, and ruby. For example, based on the dubbo platform, the requester A's face recognition service call request is converted from the http protocol format to the hessian protocol format to generate a binary code stream.

The cross-language caller 10 finds the corresponding proxy class according to the URL address in the service call request, and then finds the corresponding invoker entity according to the correspondence between the interface class and the proxy class. For example, the dubbo platform finds the corresponding proxy class according to the URL address in the face recognition service call request, and then finds the corresponding invoker entity from the interface class according to the correspondence between the interface class and the proxy class.

The invoker entity sends a binary code stream of the service call request in the hessian protocol format to the host corresponding to the invoker entity, and the server 3 decodes the binary code stream requested by the service call according to a predetermined binary codec specification. , read out the service call request of the requester 4, initiate a service call. For example, after receiving the face recognition service call request in the hessian protocol format sent by the invoker entity, the face recognition host of the service party S decodes the binary stream of the hessian protocol format by using a predetermined binary codec specification to initiate a face. Identify service calls.

The cross-language calling method provided by the foregoing embodiment provides a service page that receives interface information, a host cluster IP address, and a port address, writes the host cluster IP address and port address to the registration center, and creates an interface class according to the interface information to be loaded into the virtual machine. In the memory, according to the interface information, the proxy information is created from the registration center to create a proxy class and generate a unique URL, and then receives the http protocol format service call request sent by the requester, converts the http protocol format into a hessian protocol format, and finds according to the URL address. The corresponding interface class and the corresponding invoker entity, and finally the invoker entity sends the service call request of the hessian protocol format to the corresponding host of the service party, and is compatible with other languages for service call, and realizes cross-language call between the requester and the service party. .

As shown in FIG. 3, it is a block diagram of a preferred embodiment of the cross-language invocation program 10 of FIG. 1 or 2. A module as referred to in this application refers to a series of computer program instructions that are capable of performing a particular function.

In this embodiment, the cross-language calling program 10 includes: a receiving module 110, an interface class creating module 120, a loading module 130, a query module 140, a proxy class creating module 150, a URL generating module 160, a converting module 170, a searching module 180, The sending module 190, the functions or operating steps implemented by the modules 110-190 are similar to the above, and are not described in detail herein, for example, where:

The receiving module 110 is configured to receive the interface information of the servant, the host cluster IP address and the port address, write the host cluster IP address and port address of the servant to the registration center, or receive a service call request in the http protocol format sent by the requesting party;

An interface class creation module 120, configured to create an interface class according to the interface information, and save the file to a memory;

The loading module 130 is configured to call the class loader to load the interface class from the memory into the memory;

The querying module 140 is configured to query, according to the interface information, the service information provided by the service party from the registration center;

The proxy class creation module 150 is configured to create a proxy class corresponding to the interface class according to the queried service information;

a URL generating module 160, configured to generate a unique URL according to the proxy class;

The conversion module 170 is configured to convert the service call request from the http protocol format to the hessian protocol format;

The searching module 180 is configured to find a corresponding proxy class according to the URL address in the calling request, and find a corresponding invoker entity according to the correspondence between the proxy class and the interface class;

The sending module 190 is configured to send, by the invoker entity, a service invocation request in a hessian protocol format to a corresponding host of the service party to initiate a service access request.

As shown in FIG. 4, it is a flow chart of a preferred embodiment of the cross-language invocation method of the present application.

In the present embodiment, when the processor 12 executes the computer program of the cross-language invocation program 10 stored in the memory 11, the following steps are implemented to implement the cross-language calling method:

Step S10, receiving the interface information of the servant, the host cluster IP address, and the port address, and writing the host cluster IP address and port address of the servant to the registration center;

Step S20, creating an interface class according to the interface information, and saving to the memory;

Step S30, calling the class loader to load the interface class from the memory into the memory;

Step S40: Query, according to the interface information, the service information provided by the service party from the registration center;

Step S50: Create a proxy class corresponding to the interface class according to the queried service information.

Step S60, generating a unique URL according to the proxy class;

Step S70, receiving a service call request in the http protocol format sent by the requesting party;

Step S80, converting the service call request from the http protocol format to the hessian protocol format;

Step S90: Find a corresponding proxy class according to the URL address in the call request, and find a corresponding invoker entity according to the correspondence between the proxy class and the interface class;

Step S100: The invoker entity sends a service invocation request in the hessian protocol format to the corresponding host of the service party to initiate a service access request.

In this embodiment, as shown in FIG. 2, it is a schematic diagram of an application environment of a cross-language invocation method. The server 1 provides a service page 2 for receiving interface information, a host cluster IP address, and a port address filled in by the service party 3. The interface information is obtained by the registration center 5 issuing service information before the server 3 logs in to the server 1. After receiving the interface information, the host cluster IP address, and the port address filled in by the servant 3, the cross-language invoking program 10 writes the host cluster IP address and port address of the servant 3 to the registration center 5. For example, when the service provider S wants to provide the voiceprint recognition service on the server, the service information is first published in the zookeeper. After receiving the service information, the zookeeper returns an interface information to the service provider S. The service provider S fills in the interface information, the host cluster IP address, and the port address on the service page of the server. The platform writes the host cluster IP address and port address of the voice mask identified by the server S to the zookeeper.

The cross-language caller 10 creates an interface class based on the received interface information. The interface information provided by the servant 3 includes a package name, a class name, and a method name. Therefore, the interface class defines a package name, a class name, a method name, a request parameter, and a return parameter. E.g:

The cross-language caller 10 calls the class loader to load the interface class from local storage onto the virtual machine memory. The generated interface class is only stored in the local memory. When the interface class is needed, the class loader is called to load the interface class into the virtual machine memory. Suppose you need to call the interface class of the servant S, start the virtual machine, and then load the interface class of the servant S from the hard disk to the running memory of the system.

The cross-language invoking program 10 queries the service center 3 for the service information provided from the registrar 5 based on the interface information. For example, after receiving the interface information filled in by the service provider S based on the dubbo platform, the service information of the voice sender identification of the service party S is queried in the zookeeper.

When the requesting party 4 needs to apply for a service, the requesting party 4 sends a service invocation request in the http protocol format to the cross-language invoking program 10, and the cross-language invoking program 10 receives the service invoking request in the http protocol format issued by the requesting party 4. The service invocation request is composed of a request method URI protocol/version, a request header, and a request body. For example, the requester A sends a voiceprint recognition service call request to the dubbo platform based on the http protocol format.

The cross-language caller 10 converts the service call request from the http protocol format to the hessian protocol format. The cross-language caller 10 and the servant 3 predetermine the binary codec specification of the service call request, and the hessian binary-encodes the service call request through a predetermined binary codec specification to generate a binary code stream. The URL address in the service call request is read according to the generated binary stream. Among them, the hessian protocol is an open source, general-purpose protocol. In the case that the server and the server 3 implement the hessian protocol, the requesting party 4 can make service calls to the service party 3 in various languages such as java, C++, python, ruby, and the like. For example, the cross-language caller converts the voiceprint recognition service invocation request of requester A from the http protocol format to the hessian protocol format to generate a binary code stream.

The cross-language invoking program 10 finds the corresponding interface class according to the URL address in the service invocation request, and then finds the corresponding invoker entity from the proxy class according to the correspondence between the interface class and the proxy class. For example, the cross-language calling program finds the corresponding proxy class according to the URL address in the voiceprint recognition service call request, and then finds the corresponding invoker entity from the interface class according to the correspondence between the interface class and the proxy class.

The invoker entity sends a binary code stream of the service call request in the hessian protocol format to the host corresponding to the invoker entity, and the server 3 decodes the binary code stream requested by the service call according to a predetermined binary codec specification. , read out the service call request of the requester 4, initiate a service call. For example, after receiving the voiceprint recognition service call request of the hessian protocol format sent by the invoker entity, the voiceprint recognition host of the service party S decodes the binary code stream of the hessian protocol format by using a predetermined binary codec specification, and initiates a voiceprint. Identify service calls.

The cross-language calling method in the foregoing embodiment writes the host cluster IP address and port address received by the service page into the registration center, creates an interface class according to the received interface information, loads the virtual machine into the virtual machine memory, and then queries the service according to the interface information. Information and create a proxy class to generate a unique URL, and finally convert the http protocol format that receives the service call request into a hessian protocol format, and find the corresponding invoker entity to send the service call request in the hessian protocol format to the corresponding host of the service party, so that Based on the dubbo platform, it can be compatible with Java, C++, Python, ruby and other languages to expand the scope of service calls.

In addition, the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium includes a cross-language calling program 10, and when the cross-language calling program 10 is executed by the processor, the following operations are implemented:

Calling the class loader to load the interface class from memory into memory;

Generate a unique URL based on the proxy class;

Preferably, the interface class defines an interface package name, an interface class name, a method name in the interface class, a request parameter, and a return function.

Preferably, the service party issues service information through the registration center and obtains interface information.

Preferably, if the servant has multiple hosts providing services, the proxy class also includes a plurality of invoker entities associated with the plurality of hosts.

Preferably, the URL generation rule is to automatically generate a unique URL address according to each method name.

The specific implementation manner of the computer readable storage medium of the present application is substantially the same as the specific implementation manner of the above-mentioned cross-language calling method, and details are not described herein again.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM as described above). , a disk, an optical disk, including a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in the various embodiments of the present application.

The above is only a preferred embodiment of the present application, and thus does not limit the scope of the patent application, and the equivalent structure or equivalent process transformation made by the specification and the drawings of the present application, or directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of this application.

Claims

A cross-language calling method, the method comprising:

Receiving the interface information of the servant, the host cluster IP address and the port address, and writing the host cluster IP address and port address of the servant to the registration center;

Creating an interface class according to the interface information, and saving to the memory;

Calling the class loader to load the interface class from memory into memory;

Querying, according to the interface information, the service information provided by the service party from the registration center;

Creating a proxy class corresponding to the above interface class according to the service information that is queried;

Generate a unique URL based on the proxy class;

Receiving a service call request in the http protocol format issued by the requesting party;

Convert the service invocation request from the http protocol format to the hessian protocol format;

Find the corresponding proxy class according to the URL address in the call request, and find the corresponding invoker entity according to the correspondence between the proxy class and the interface class;

The service call request of the hessian protocol format is sent by the invoker entity to the corresponding host of the service party to initiate a service access request.
The cross-language calling method according to claim 1, wherein the interface class defines an interface package name, an interface class name, a method name in the interface class, a request parameter, and a return function.
The cross-language calling method according to claim 2, wherein the interface class is stored in a local memory, and in use, the calling class loader loads the interface class into the virtual machine memory.
The cross-language calling method according to claim 1, wherein the service party issues service information through the registration center and obtains interface information.
The cross-language calling method according to claim 1, wherein if the servant has a plurality of hosts providing services, the proxy class also includes a plurality of invoker entities associated with the plurality of hosts.
The cross-language calling method according to claim 1, wherein the URL generation rule automatically generates a unique URL address according to each method name.
The cross-language calling method according to claim 6, wherein the URL address is composed of a protocol and a destination.
A server, comprising: a memory, a processor, wherein the memory stores a cross-language calling program, and the cross-language calling program is executed by the processor, and the following steps can be implemented:

Receiving the interface information of the servant, the host cluster IP address and the port address, and writing the host cluster IP address and port address of the servant to the registration center;

Creating an interface class according to the interface information, and saving to the memory;

Calling the class loader to load the interface class from memory into memory;

Querying, according to the interface information, the service information provided by the service party from the registration center;

Creating a proxy class corresponding to the above interface class according to the service information that is queried;

Generate a unique URL based on the proxy class;

Receiving a service call request in the http protocol format issued by the requesting party;

Convert the service invocation request from the http protocol format to the hessian protocol format;

Find the corresponding proxy class according to the URL address in the call request, and find the corresponding invoker entity according to the correspondence between the proxy class and the interface class;

The service call request of the hessian protocol format is sent by the invoker entity to the corresponding host of the service party to initiate a service access request.
The server according to claim 8, wherein the interface class defines an interface package name, an interface class name, a method name in the interface class, a request parameter, and a return function.
The server according to claim 9, wherein the interface class is stored in a local memory, and in use, the class loader is called to load the interface class into the virtual machine memory.
The server according to claim 8, wherein the service party issues service information through the registration center and obtains interface information.
The server according to claim 8, wherein if the server has multiple hosts providing services, the agent class also includes a plurality of invoker entities associated with the plurality of hosts.
The server according to claim 8, wherein said URL generation rule is to automatically generate a unique URL address based on each method name.
The server according to claim 13, wherein said URL address is composed of a protocol and a destination.
A computer readable storage medium, wherein the computer readable storage medium includes a cross-language calling program, and when the system cross-language calling program is executed by a processor, the following steps can be implemented:

Receiving the interface information of the servant, the host cluster IP address and the port address, and writing the host group IP address and port address of the servant to the registration center;

Creating an interface class according to the interface information, and saving to the memory;

Calling the class loader to load the interface class from memory into memory;

Querying, according to the interface information, the service information provided by the service party from the registration center;

Creating a proxy class corresponding to the above interface class according to the service information that is queried;

Generate a unique URL based on the proxy class;

Receiving a service call request in the http protocol format issued by the requesting party;

Convert the service invocation request from the http protocol format to the hessian protocol format;

Find the corresponding proxy class according to the URL address in the call request, and find the corresponding invoker entity according to the correspondence between the proxy class and the interface class;

The service call request of the hessian protocol format is sent by the invoker entity to the corresponding host of the service party to initiate a service access request.
The computer readable storage medium of claim 15, wherein the interface class defines an interface package name, an interface class name, a method name in the interface class, a request parameter, and a return function.
The computer readable storage medium of claim 16, wherein the interface class is stored in a local memory, and in use, the class loader is called to load the interface class into the virtual machine memory.
A computer readable storage medium according to claim 15, wherein said service party issues service information through a registration center and obtains interface information.
The computer readable storage medium according to claim 15, wherein if the servant has a plurality of hosts providing services, the proxy class also includes a plurality of invoker entities associated with the plurality of hosts.
The computer readable storage medium according to claim 15, wherein said URL generation rule is to automatically generate a unique URL address based on each method name.