Remote procedure call interface updating method and device, equipment and medium

Abstract

The embodiment of the invention discloses a remote procedure call interface updating method and device, equipment and a medium, and the method comprises the steps: searching and obtaining a to-be-updated remote procedure call interface code file package in a preset interface code file package storage space, determining a target to-be-updated interface corresponding to the to-be-updated remote procedure call interface code file package; and based on a new code file loader which is named different from the original code file loader of the target to-be-updated interface, loading file content of the to-be-updated remote procedure call interface code file package into a preset virtual machine memory, and completing updating of the target to-be-updated interface. According to the technical scheme, the problem that the code updating result of the remote procedure calling interface cannot be subjected to hot deployment is solved, hot deployment of the code updating file of the remote procedure calling interface is achieved, and the interface updating efficiency is improved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer communication technology, and in particular to a remote procedure call interface updating method, device, equipment and medium. Background Art

[0002] Remote Procedure Call (RPC) is a protocol that an application can use to request services from an application on another computer in the network, which can improve the interoperability between different programs.

[0003] However, in the process of implementing the present invention, it was found that there are at least the following technical problems in the prior art: the Java Virtual Machine (JVM) memory does not support the cancellation or replacement of the same and referenced class, which results in that after the RPC interface code is modified, the new code of the modified and updated RPC interface needs to be redeployed to the server to take effect. This process is time-consuming and may affect user use during the redeployment period, which is not quick and convenient enough. Summary of the invention

[0004] The embodiments of the present invention provide a remote procedure call interface update method, device, equipment and medium, which can realize hot deployment of code update files of the remote procedure call interface, do not affect the normal operation of the server during the interface update process, and improve the efficiency of the interface update.

[0005] In a first aspect, an embodiment of the present invention provides a remote procedure call interface update method, the method comprising:

[0006] Searching and acquiring the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determining the target interface to be updated corresponding to the remote procedure call interface code file package to be updated;

[0007] Based on a new code file loader named differently from the original code file loader of the target interface to be updated, the file content of the remote procedure call interface code file package to be updated is loaded into the preset virtual machine memory to complete the update of the target interface to be updated.

[0008] In a second aspect, an embodiment of the present invention further provides a remote procedure call interface updating device, the device comprising:

[0009] The interface update file acquisition module is used to search and acquire the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determine the target interface to be updated corresponding to the remote procedure call interface code file package to be updated;

[0010] The interface update module is used to load the file content of the remote procedure call interface code file package to be updated into the preset virtual machine memory based on a new code file loader named differently from the original code file loader of the target interface to be updated, thereby completing the update of the target interface to be updated.

[0011] In a third aspect, an embodiment of the present invention further provides a computer device, the computer device comprising:

[0012] one or more processors;

[0013] A memory for storing one or more programs;

[0014] When the one or more programs are executed by the one or more processors, the one or more processors implement the remote procedure call interface updating method provided by any embodiment of the present invention.

[0015] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a remote procedure call interface updating method as provided in any embodiment of the present invention.

[0016] The technical solution of this embodiment is that when it is necessary to update the remote procedure call interface, the server providing the interface service will search and obtain the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determine the target interface to be updated corresponding to the remote procedure call interface code file package to be updated; then, based on a new code file loader named differently from the original code file loader of the target interface to be updated, the file content of the remote procedure call interface code file package to be updated is loaded into the preset virtual machine memory to complete the update of the target interface to be updated. The technical solution of this embodiment solves the problem that the code update result of the remote procedure call interface cannot be hot deployed, realizes the hot deployment of the code update file of the remote procedure call interface, does not affect the normal operation of the server during the interface update process, and improves the efficiency of the interface update. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A flowchart of a remote procedure call interface updating method provided by an embodiment of the present invention;

[0018] Figure 2 A flowchart of a remote procedure call interface updating method provided by an embodiment of the present invention;

[0019] Figure 3 A schematic diagram of the structure of a remote procedure call interface updating device provided by an embodiment of the present invention;

[0020] Figure 4A schematic diagram of the structure of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0021] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0022] Figure 1 This is a flowchart of a remote procedure call interface update method provided by an embodiment of the present invention. This embodiment can be applied to a scenario where a server providing a remote procedure call interface service updates a registered remote procedure call interface. The method can be executed by a remote procedure call interface update device, which can be implemented by software and / or hardware and integrated into a computer device with application development function.

[0023] like Figure 1 As shown, the remote procedure call interface updating method of this embodiment includes the following steps:

[0024] S110: Search and obtain the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determine the target interface to be updated corresponding to the remote procedure call interface code file package to be updated.

[0025] Among them, the preset interface code file package storage space can be a preset Java code file package (Jar package) storage space, which is used to store the interface function update code file of the registered remote procedure call interface (Remote Procedure Call, RPC interface). The address information of the preset interface code file package storage space can be used as the default storage path of an Rpc interface Jar package to be updated, and the storage path is the default reading path of a non-network application class (webAppClass). When it is necessary to update the registered Rpc interface, the remote procedure call interface code file package to be updated that needs to be updated will be fully searched in the preset interface code file package storage space based on the address information of the preset interface code file package storage space.

[0026] Specifically, the update of a registered Rpc interface refers to the update of the code for implementing the interface function. For example, the interface function originally provided by the registered Rpc interface corresponds to function method 1, and function method 1 can be used to implement the newly added function. According to the business needs in the application process, a deletion function needs to be added to the Rpc interface. Then, the function implementation code of the registered Rpc interface is updated, and function method 2 is added to add a deletion function method in the interface. In the prior art, the Java Virtual Machine (Jvm) memory does not support the cancellation or replacement of classes with the same name and being referenced. After the Rpc interface code is modified, the new code needs to be redeployed to the server to take effect, that is, the hot deployment of the new interface function cannot be realized, which is time-consuming. The redeployment period may affect user use and is not fast and convenient enough.

[0027] Based on the technical solution of this implementation example, the registered RPC interface function can be updated at any time according to user needs during the operation of the server. After completing the Rpc interface update code file (i.e., the remote procedure call interface code file package to be updated), the user can save the remote procedure call interface code file package to be updated to the preset interface code file package storage space at any time and trigger the interface update; accordingly, the server will receive an interface code update reminder message. Therefore, when the server obtains the interface code update reminder message, it will search and obtain the remote procedure call interface code file package to be updated in the preset interface code file package storage space.

[0028] Furthermore, after obtaining the remote procedure call interface code file package to be updated, the target interface to be updated, that is, the registered Rpc interface that needs to be functionally updated, will be determined based on the identification information of the code file package. Specifically, the identification information of the remote procedure call interface code file to be updated will include the identification information of the corresponding Rpc interface, so that the corresponding target interface to be updated can be matched in the registered interface list.

[0029] S120. Based on a new code file loader named differently from the original code file loader of the target interface to be updated, the file content of the remote procedure call interface code file package to be updated is loaded into a preset virtual machine memory to complete the update of the target interface to be updated.

[0030] The update of the target interface to be updated is equivalent to modifying and updating the original interface function implementation code. For example, after Aclass is loaded by Jvm, if Aclass is modified, a new Aclass will be obtained. Since Jvm cannot load the same class repeatedly, Jvm will not load the new Aclass, and the original Aclass (class is the file after code compilation) will still be running in Jvm. The new function of the target interface to be updated cannot be updated.

[0031] In this embodiment, in order to successfully load the new Aclass into the Jvm, a new code file loader (Classloader) with a different name from the original code file loader of the target interface to be updated is used to load the file content of the remote procedure call interface code file package to be updated into the preset virtual machine memory, thereby realizing the update of the registered Rpc interface.

[0032] During this process, the original code file loader of the target interface to be updated can be obtained first, and the name of the original code file loader can be changed; then a new code file loader with a name different from the original code file loader can be configured, and the file content of the remote procedure call interface code file package to be updated can be loaded into the preset virtual machine memory through the new code file loader.

[0033] The technical solution of this embodiment is that when it is necessary to update the remote procedure call interface, the server providing the interface service will search and obtain the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determine the target interface to be updated corresponding to the remote procedure call interface code file package to be updated; then, based on a new code file loader named differently from the original code file loader of the target interface to be updated, the file content of the remote procedure call interface code file package to be updated is loaded into the preset virtual machine memory to complete the update of the target interface to be updated. The technical solution of this embodiment solves the problem that the code update result of the remote procedure call interface cannot be hot deployed, realizes the hot deployment of the code update file of the remote procedure call interface, does not affect the normal operation of the server during the interface update process, and improves the efficiency of the interface update.

[0034] Figure 2 A flowchart of a remote procedure call interface update method provided by an embodiment of the present invention, this embodiment and the remote procedure call interface update method in the above embodiment belong to the same inventive concept, and further describes the remote procedure call interface update process. The method can be executed by a remote procedure call interface update device, which can be implemented by software and / or hardware, and integrated in a computer device with application development function.

[0035] like Figure 2 As shown, the remote procedure call interface updating method of this embodiment includes the following steps:

[0036] S210. During the server startup process, after establishing a connection with the preset interface registration platform and determining the existing interface, searching and obtaining the remote procedure call interface code file package to be updated in the preset interface code file package storage space.

[0037] Specifically, during the server startup process, the server will establish a connection with the interface registration center to register a new remote procedure call interface or notify the service interface that is in a usable state. The interface registration center is used by the server to register a new remote service interface and provide a list of usable service interfaces for clients requesting Rpc services. The preset interface registration platform can be an Rpc interface registration platform implemented by open source frameworks such as zookeeper, eureka or consul.

[0038] In this embodiment, in addition to completing the routine new interface registration and usable status service interface preparation work, the server will also read the remote procedure call interface code file package to be updated in full from a pre-set default path. If any remote procedure call interface code file package to be updated can be read, it indicates that the corresponding registered interface needs to be updated; if no remote procedure call interface code file package to be updated is read, it indicates that there is no registered interface that needs to be updated temporarily. The remote procedure call interface code file package to be updated is the updated interface function implementation code file of the registered interface that needs to be updated.

[0039] S220: Determine the target interface to be updated corresponding to the remote procedure call interface code file package to be updated.

[0040] After obtaining the remote procedure call interface code file package to be updated, the target interface to be updated, that is, the registered Rpc interface that needs to be updated, will be determined based on the identification information of the code file package. Specifically, the identification information of the remote procedure call interface code file to be updated will contain the identification information of the corresponding Rpc interface, so that the corresponding target interface to be updated can be matched in the registered interface list.

[0041] In an optional implementation, the name of the remote procedure call interface code file package to be updated may be corresponding storage path information or call path information, etc., which contains information content consistent with the target interface to be updated.

[0042] S230: Parse the remote procedure call interface code file package to be updated to obtain the file content to be updated.

[0043] The file content to be updated is the code file content for implementing the functions in the remote procedure call interface code file package to be updated.

[0044] S240: Obtain the source code file loader of the target interface to be updated, and change the name of the source code file loader.

[0045] Among them, the original code file loader is an existing loader, which is used to load the original code file into the Jvm when the target interface to be updated is registered for the first time. Since the same class file cannot be loaded again, the name of the original code file loader must be changed first in this embodiment. For example, a new identification information can be added to indicate that it is the original code file loader, which does not conflict with the new code file loader.

[0046] S250: Configure a new code file loader with a name different from that of the original code file loader, and load the to-be-updated file content into a preset virtual machine memory through the new code file loader.

[0047] The new code file loader is a custom class loader based on the parent delegation mode. The custom class loader can be named with the information interface function identifier to distinguish it from the original code file loader. Furthermore, the new code file loader can be used to load the file content to be updated into the preset virtual machine memory, thereby realizing the registration of the updated interface function.

[0048] Since the old and new functions of the interface are named differently, they can also exist at the same time. That is, the naming of the original code file loader and the naming of the new code file loader are used as the call identifiers of the interface function before the update and the interface function after the update of the target interface to be updated respectively; the client that calls the service can call each function of a certain Rpc interface that has undergone functional update based on specific different function identifiers (that is, interface aliases). Among them, the naming of the original code file loader and the naming of the new code file loader contain the same interface identifier and different method function identifiers.

[0049] The technical solution of this embodiment is to check whether there is a remote procedure call interface code file package to be updated when the server is started, that is, to determine whether the remote procedure call interface is to be updated, and then determine the corresponding target interface to be updated based on the read remote procedure call interface code file package to be updated; then, based on a new code file loader named differently from the original code file loader of the target interface to be updated, load the file content of the remote procedure call interface code file package to be updated into the preset virtual machine memory to complete the update of the target interface to be updated. The technical solution of this embodiment solves the problem that the code update result of the remote procedure call interface cannot be hot deployed, realizes the hot deployment of the code update file of the remote procedure call interface, does not affect the normal operation of the server during the interface update process, improves the efficiency of the interface update, and can also support the existence of two or more interface functions being called for one interface.

[0050] Figure 3 A structural diagram of a remote procedure call interface updating device provided in an embodiment of the present invention. This embodiment is applicable to a scenario in which a server providing a remote procedure call interface service updates a registered remote procedure call interface. The device can be implemented by software and / or hardware and integrated into a computer terminal device with application development capabilities.

[0051] like Figure 3 As shown, the remote procedure call interface updating device includes: an interface update file acquisition module 310 and an interface update module 320.

[0052] Among them, the interface update file acquisition module 310 is used to search and obtain the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determine the target interface to be updated corresponding to the remote procedure call interface code file package to be updated; the interface update module 320 is used to load the file content of the remote procedure call interface code file package to be updated into the preset virtual machine memory based on a new code file loader named differently from the original code file loader of the target interface to be updated, so as to complete the update of the target interface to be updated.

[0053] The technical solution of this embodiment is that when it is necessary to update the remote procedure call interface, the server providing the interface service will search and obtain the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determine the target interface to be updated corresponding to the remote procedure call interface code file package to be updated; then, based on a new code file loader named differently from the original code file loader of the target interface to be updated, the file content of the remote procedure call interface code file package to be updated is loaded into the preset virtual machine memory to complete the update of the target interface to be updated. The technical solution of this embodiment solves the problem that the code update result of the remote procedure call interface cannot be hot deployed, realizes the hot deployment of the code update file of the remote procedure call interface, does not affect the normal operation of the server during the interface update process, and improves the efficiency of the interface update.

[0054] Optionally, the interface update file acquisition module 310 is specifically used to:

[0055] During the operation of the server, when an interface code update reminder message is obtained, the remote procedure call interface code file package to be updated is searched and obtained in the preset interface code file package storage space.

[0056] Optionally, the interface update file acquisition module 310 is specifically used to:

[0057] During the server startup process, after establishing a connection with the preset interface registration platform and determining the existing interface, the remote procedure call interface code file package to be updated is searched and obtained in the preset interface code file package storage space.

[0058] Optionally, the interface update file acquisition module 310 may also be specifically used for:

[0059] Obtaining interface identification information of the remote procedure call interface code file package to be updated;

[0060] The target interface to be updated corresponding to the remote procedure call interface code file package to be updated is determined according to the interface identification information.

[0061] Optionally, the interface updating module 320 is specifically used for:

[0062] Obtaining the source code file loader of the target interface to be updated, and changing the name of the source code file loader;

[0063] A new code file loader named differently from the original code file loader is configured, and the file content of the remote procedure call interface code file package to be updated is loaded into the preset virtual machine memory through the new code file loader.

[0064] Optionally, the interface updating module 320 is further configured to:

[0065] The remote procedure call interface code file package to be updated is parsed to obtain the file content.

[0066] Optionally, the interface update file acquisition module 310 may also be used to:

[0067] Using the name of the original code file loader and the name of the new code file loader as call identifiers of the pre-update interface function and the post-update interface function of the target interface to be updated, respectively;

[0068] The naming of the original code file loader and the naming of the new code file loader contain the same interface identifier and different method function identifiers.

[0069] The remote procedure call interface updating device provided in the embodiment of the present invention can execute the remote procedure call interface updating method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0070] Figure 4 A schematic diagram of the structure of a computer device provided in an embodiment of the present invention. Figure 4 A block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention is shown. Figure 4 The computer device 12 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention. The computer device 12 can be any terminal device with computing capabilities, such as an intelligent controller and server, a mobile phone and other terminal devices.

[0071] like Figure 4 As shown, the computer device 12 is in the form of a general-purpose computing device. The components of the computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that connects various system components (including the system memory 28 and the processing unit 16).

[0072] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus architectures. By way of example, these architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MAC) bus, an Enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0073] The computer device 12 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the computer device 12, including volatile and non-volatile media, removable and non-removable media.

[0074] The system memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The computer device 12 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 4 not shown, usually called a "hard drive"). Although Figure 4 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0075] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 42 generally perform the functions and / or methods of the embodiments described herein.

[0076] The computer device 12 may also communicate with one or more external devices 14 (e.g., keyboards, pointing devices, displays 24, etc.), one or more devices that enable a user to interact with the computer device 12, and / or any device that enables the computer device 12 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via an input / output (I / O) interface 22. Furthermore, the computer device 12 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 20. As shown, the network adapter 20 communicates with the other modules of the computer device 12 via the bus 18. It should be understood that although Figure 4Not shown, other hardware and / or software modules may be used in conjunction with computer device 12, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0077] The processing unit 16 executes various functional applications and data processing by running the program stored in the system memory 28, for example, implementing the remote procedure call interface update method provided in the embodiment of the present invention, the method comprising:

[0078] Searching and acquiring the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determining the target interface to be updated corresponding to the remote procedure call interface code file package to be updated;

[0079] Based on a new code file loader named differently from the original code file loader of the target interface to be updated, the file content of the remote procedure call interface code file package to be updated is loaded into the preset virtual machine memory to complete the update of the target interface to be updated.

[0080] An embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the remote procedure call interface updating method provided by any embodiment of the present invention is implemented. The method includes:

[0081] Searching and acquiring the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determining the target interface to be updated corresponding to the remote procedure call interface code file package to be updated;

[0082] Based on a new code file loader named differently from the original code file loader of the target interface to be updated, the file content of the remote procedure call interface code file package to be updated is loaded into the preset virtual machine memory to complete the update of the target interface to be updated.

[0083] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0084] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0085] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0086] Computer program code for performing the operation of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0087] It should be understood by those skilled in the art that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be implemented by a program code executable by a computer device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0088] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A remote procedure call interface update method, characterized in that: include: Searching and acquiring the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determining the target interface to be updated corresponding to the remote procedure call interface code file package to be updated; Based on a new code file loader named differently from the original code file loader of the target interface to be updated, the file content of the remote procedure call interface code file package to be updated is loaded into the preset virtual machine memory to complete the update of the target interface to be updated.

2. The method according to claim 1, characterized in that The step of searching and obtaining the remote procedure call interface code file package to be updated in the preset interface code file package storage space includes: During the operation of the server, when an interface code update reminder message is obtained, the remote procedure call interface code file package to be updated is searched and obtained in the preset interface code file package storage space.

3. The method according to claim 1, characterized in that The step of searching and obtaining the remote procedure call interface code file package to be updated in the preset interface code file package storage space includes: During the server startup process, after establishing a connection with the preset interface registration platform and determining the existing interface, the remote procedure call interface code file package to be updated is searched and obtained in the preset interface code file package storage space.

4. The method according to claim 1, characterized in that: The step of determining a target interface to be updated corresponding to the remote procedure call interface code file package to be updated includes: Obtaining interface identification information of the remote procedure call interface code file package to be updated; The target interface to be updated corresponding to the remote procedure call interface code file package to be updated is determined according to the interface identification information.

5. The method according to any one of claims 1 to 4, characterized in that: The method of loading the file content of the remote procedure call interface code file package to be updated into the preset virtual machine memory based on the new code file loader named differently from the original code file loader of the target interface to be updated includes: Obtaining the source code file loader of the target interface to be updated, and changing the name of the source code file loader; A new code file loader named differently from the original code file loader is configured, and the file content of the remote procedure call interface code file package to be updated is loaded into the preset virtual machine memory through the new code file loader.

6. The method according to claim 5, characterized in that Before loading the file content of the remote procedure call interface code file package to be updated into the preset virtual machine memory, the method further includes: The remote procedure call interface code file package to be updated is parsed to obtain the file content.

7. The method according to claim 1, characterized in that The method further comprises: Using the name of the original code file loader and the name of the new code file loader as call identifiers of the pre-update interface function and the post-update interface function of the target interface to be updated, respectively; The naming of the original code file loader and the naming of the new code file loader contain the same interface identifier and different method function identifiers.

8. A remote procedure call interface updating device, characterized in that: include: The interface update file acquisition module is used to search and acquire the remote procedure call interface code file package to be updated in the preset interface code file package storage space, and determine the target interface to be updated corresponding to the remote procedure call interface code file package to be updated; The interface update module is used to load the file content of the remote procedure call interface code file package to be updated into the preset virtual machine memory based on a new code file loader named differently from the original code file loader of the target interface to be updated, thereby completing the update of the target interface to be updated.

9. A computer device, characterized in that: The computer device comprises: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the remote procedure call interface updating method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the remote procedure call interface updating method as described in any one of claims 1 to 7 is implemented.

Images