CN114020319A - Interface calling method, device, server and computer readable storage medium - Google Patents
Interface calling method, device, server and computer readable storage medium Download PDFInfo
- Publication number
- CN114020319A CN114020319A CN202111145387.6A CN202111145387A CN114020319A CN 114020319 A CN114020319 A CN 114020319A CN 202111145387 A CN202111145387 A CN 202111145387A CN 114020319 A CN114020319 A CN 114020319A
- Authority
- CN
- China
- Prior art keywords
- interface
- processor
- version number
- version
- searching
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the invention relates to the technical field of system development, in particular to a method, a device, a server and a computer readable storage medium for interface calling. The method for calling the interface comprises the following steps: s1: receiving an interface calling request; the interface calling request carries a first version number of an interface which is requested to be called; s2: searching a first processor corresponding to the first version number; s3: if the first processor is not found, a second processor corresponding to a second version number of the interface is found, and the interface is called through the second processor; s4: registering the corresponding relation between the second processor and the first version number into a mapping relation, wherein the mapping relation is used for storing the corresponding relation between the registered interface version number and the processor; wherein the second version number is a maximum version number lower than the first version number. The problem that a corresponding processor needs to be added to each version of interface can be solved, and the versions of the interfaces can be managed more conveniently.
Description
Technical Field
The embodiment of the application relates to the technical field of system development, in particular to a method, a device, a server and a computer readable storage medium for interface calling.
Background
With the development of internet technology, the development mode is continuously evolving, and most of the Browser/Server mode (Browser/Server, B/S structure) is finally rendered into hypertext markup language (HTML) by a template engine and then directly displayed to the middle terminal user. At present, internet development is not only directed to the display of a browser, but an interface is provided for various terminals, such as a mobile terminal or other services, and then services are processed respectively, and the previous interface can be changed when the terminals are independent of each other along with the iteration of versions and the change of the services. Due to the development of services, the field attribute of the interface is greatly changed, if the field attribute is directly modified on the original interface, a calling party is required to modify, and the method is not friendly to the calling party. A good Application Programming Interface (API) needs to ensure backward compatibility, and a change in product requirements cannot affect the normal functions of the existing version, so that version management of the Interface is very important.
The current solution is to redefine an interface of one version, so that a caller can specify interfaces corresponding to two versions, respectively, so that the caller can call interfaces of different versions by modifying the version number, and a provider can newly write an interface corresponding to the version each time the interface is changed.
However, the inventor of the present invention finds that, with the above technical solution, since version numbers on all Uniform Resource Locators (URLs) need to be updated for updating a large version, for example, a V1 version of an interface is upgraded to a V2 version, all interfaces need to provide a processor of a V2 version, even if an interface of any code is not modified so as to add a URL corresponding to a version, if a processor is not added, the processor of the corresponding version cannot be found. Adding a corresponding processor for each version of the interface results in many repetitive tasks and is error prone.
Disclosure of Invention
Embodiments of the present invention provide a method, an apparatus, a server, and a computer-readable storage medium for interface invocation, which can solve the problem that a corresponding processor needs to be added to an interface of each version, and manage the versions of the interfaces more conveniently.
In order to achieve the above object, an embodiment of the present application provides an interface calling method, including: s1: receiving an interface calling request; the interface calling request carries a first version number of an interface which is requested to be called; s2: searching a first processor corresponding to the first version number; s3: if the first processor is not found, a second processor corresponding to a second version number of the interface is found, and the interface is called through the second processor; s4: registering the corresponding relation between the second processor and the first version number into a mapping relation, wherein the mapping relation is used for storing the corresponding relation between the registered interface version number and the processor; wherein the second version number is a maximum version number lower than the first version number.
In order to achieve the above object, an embodiment of the present application further provides an apparatus for interface invocation, including: the receiving module is used for receiving an interface calling request; the interface calling request carries a first version number of an interface which is requested to be called; the searching module is used for searching a first processor corresponding to the first version number; the execution module is used for searching a second processor corresponding to a second version number of the interface if the first processor is not searched, and executing the calling of the interface through the second processor; the registration module is used for registering the corresponding relation between the second processor and the first version number into a mapping relation, and the mapping relation is used for storing the corresponding relation between the registered interface version number and the processor; wherein the second version number is a maximum version number lower than the first version number.
In order to achieve the above object, an embodiment of the present application further provides a server, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of interface calling described above.
To achieve the above object, an embodiment of the present application further provides a computer-readable storage medium storing a computer program, where the computer program, when executed by a processor, implements the method for interface invocation described above.
According to the method for calling the interface, after the interface is called, according to the first version number of the request calling interface carried in the calling request, the first processor corresponding to the first version number of the interface is searched after the calling request of the interface is received, if the first processor is not searched, the first processor corresponding to the first version number is not provided, the second processor corresponding to the second version number of the interface can be searched, and the second processor is adopted to execute calling of the interface. The corresponding relation between the second processor and the first version number is registered in the mapping relation to store the corresponding relation between the first version number and the second processor, so that when the first version number of the interface is called again, the nonexistent first processor does not need to be searched, the corresponding second processor can be searched directly according to the stored corresponding relation between the first version number and the second processor, and the second processor is adopted to execute the calling of the first version number of the interface. The second version number is the maximum version number lower than the first version number, that is, the second version is the closest to the first version, and the second processor corresponding to the second version number better meets the requirement of the first version number of the called interface. Therefore, the method for calling the interface provided by the embodiment can enable the first version number of the interface to be called through the corresponding processor without adding the first processor again, solves the problem that the corresponding processor needs to be added for each version of the interface, and is easier for version management of the interface.
Additionally, the searching for the first processor corresponding to the first version number includes: searching a processor corresponding to the first version number of the interface according to the mapping relation; the searching for the second processor corresponding to the second version number of the interface includes: and searching the processor corresponding to the second version number of the interface according to the mapping relation. Because the mapping relation stores the corresponding relation between the registered interface version number and the processor, the processor corresponding to the interface version number can be quickly found through the mapping relation.
In addition, the mapping relation is the mapping relation between the URL of the interface and the processor; the URL of the interface comprises the version number and the path of the interface; the version number and the path of the registered interface are stored in the first set, and the mapping relation between the path of the registered interface and the processor is stored in the second set. By storing the registered version number and path of the interface in the first set, when the first processor is not found, the maximum version number lower than the first version number is conveniently found; and storing the mapping relation between the registered interface path and the processor in the second set, so that the processor of the version corresponding to the called interface can be conveniently found.
In addition, before the receiving the interface call request, the method further includes: acquiring a third set, wherein the third set comprises version numbers of all unregistered interfaces; traversing the third set, performing the S1 through the S4 for each traversed version number of the unregistered interface. By traversing the third set and executing steps S1 to S4, the registration of the version numbers of all unregistered interfaces and the corresponding relationships of corresponding processors is completed in advance, and after receiving an interface call request, the processor of the called interface version can be directly found out, so as to realize the call of the interface.
In addition, after the acquiring the third set and before the traversing the third set, the method further includes: and sorting the version numbers of all unregistered interfaces in the third set in ascending order. The maximum version number lower than the current version number is conveniently obtained by sequencing the version numbers of the unregistered interfaces in an ascending order.
Additionally, the obtaining a third set includes: acquiring a fourth set, wherein the fourth set comprises version numbers of all unregistered interfaces and version numbers of all registered interfaces; subtracting the first set from the fourth set to obtain the third set. And acquiring a set of unregistered interface version numbers so as to register the corresponding relation between the unregistered interface version numbers and the corresponding processors in the mapping relation, so that the interfaces of all versions have the corresponding processors.
Drawings
One or more embodiments are illustrated by way of example in the accompanying drawings, which correspond to the figures in which like reference numerals refer to similar elements and which are not to scale unless otherwise specified.
FIG. 1 is a flow diagram of an interface invocation method provided in accordance with one embodiment of the present invention;
FIG. 2 is a schematic workflow diagram of an interface calling method according to an embodiment of the present invention;
FIG. 3 is a flow diagram of an interface call method provided in accordance with another embodiment of the present invention;
FIG. 4 is a schematic diagram of an interface invocation means provided in accordance with another embodiment of the present invention;
fig. 5 is a block diagram of a server provided according to another embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that numerous technical details are set forth in order to provide a better understanding of the present application in various embodiments of the present invention. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments. The following embodiments are divided for convenience of description, and should not constitute any limitation to the specific implementation manner of the present invention, and the embodiments may be mutually incorporated and referred to without contradiction.
An embodiment of the present invention relates to an interface calling method, which is applicable to all systems developed based on spring boot, and the following describes implementation details of the interface calling method of the embodiment specifically, and the following only provides implementation details for facilitating understanding, but is not necessary for implementing the present solution. A specific flowchart of the interface calling method of this embodiment is shown in fig. 1, and includes:
Specifically, the interface providing end receives a request of calling the interface from a user, and the first version number of the interface which is requested to be called is carried in the interface calling request. In this embodiment, the user may be a terminal, such as a mobile server.
In one example, the interface providing end is a server, and a specific work flow is shown in fig. 2, including: a control processor, a plurality of processors, and a mapping processor. The control processor is used for receiving an interface calling request of a user, acquiring a corresponding processor according to the URL of the interface, executing the processor and returning an execution result to the user; the multiple processors are used for executing execution commands issued by the control processors, namely the calling of the execution interfaces, and returning execution results to the control processors; the mapping processor is used for storing the processor of the interface and returning the corresponding processor to the control processor according to the request of the control processor for acquiring the processor.
Specifically, after receiving an interface calling request sent by a user, an interface providing end searches for a first processor corresponding to a first version number according to the first version number of the interface which is carried in the interface calling request and requests to call.
In one example, each version number of an interface requires a corresponding processor to perform a call for that version number, as the interface is updated to produce a different version. After receiving an interface calling request sent by a terminal, a control processor in the server acquires a corresponding processor from a mapping processor according to a URL (uniform resource locator) requesting to call an interface, wherein the URL of the interface comprises a version number and a path of the interface. And the mapping processor searches the first processor corresponding to the first version number of the interface requested to be called according to the mapping relation, wherein the mapping relation is the mapping relation between the URL of the interface and the processor. And the mapping processor returns the searched first processor to the control processor, so that the control processor executes the first processor, the interface is called, and the execution result of the interface calling is returned to the terminal.
And 103, if the first processor is not found, finding a second processor corresponding to the second version number of the interface, and executing the calling of the interface through the second processor.
Specifically, in step 102, if the mapping processor does not find the first processor corresponding to the first version number of the interface requested to be called according to the mapping relationship, the mapping processor finds the second processor corresponding to the second version number of the interface according to the mapping relationship between the URL of the interface and the processor, returns the second processor to the control processor, so that the control processor executes the second processor to realize the call of the interface, and returns the execution result of the call of the interface to the terminal.
And 104, registering the corresponding relation between the second processor and the first version number in the mapping relation.
Specifically, in step 103, after the mapping processor finds a second processor corresponding to a second version number of the interface and returns the second processor to the control processor, the mapping processor registers a corresponding relationship between the second processor and the first version number in the mapping relationship, that is, the mapping relationship between the second processor and the first version number is encapsulated in the mapping processor, where the mapping relationship is used to store a corresponding relationship between a registered interface version number and a processor.
In this embodiment, when the first processor corresponding to the first version number of the called interface is not found, the second processor corresponding to the second version number of the interface is found, and the second version number of the found interface is the maximum version number lower than the first version number of the interface.
In the related art, when the interface has a plurality of versions, a corresponding processor needs to be added for each version, which results in repetitive work, but in the embodiment of the present invention, after the interface is called, after receiving a call request of the interface, according to a first version number of a request call interface carried in the call request, a first processor corresponding to the first version number of the interface is searched, if the first processor is not searched, it is indicated that the first processor corresponding to the first version number is not provided, a second processor corresponding to a second version number of the interface can be searched, and the second processor is used to execute the call of the interface. The corresponding relation between the second processor and the first version number is registered in the mapping relation to store the corresponding relation between the first version number and the second processor, so that when the first version number of the interface is called again, the nonexistent first processor does not need to be searched, the corresponding second processor can be searched directly according to the stored corresponding relation between the first version number and the second processor, and the second processor is adopted to execute the calling of the first version number of the interface. The second version number is the maximum version number lower than the first version number, that is, the second version is the closest to the first version, and the second processor corresponding to the second version number better meets the requirement of the first version number of the called interface. Therefore, the method for calling the interface provided by the embodiment can enable the first version number of the interface to be called through the corresponding processor without adding the first processor again, solves the problem that the corresponding processor needs to be added for each version of the interface, and is easier for version management of the interface.
Another embodiment of the present invention relates to an interface calling method, which is applicable to all systems developed based on spring boot, and the following describes in detail the implementation details of the interface calling method of the present embodiment. A specific flowchart of the interface calling method of this embodiment is shown in fig. 3, and includes:
Specifically, the interface provider injects the mapping processor through the SpringIOC container, and traverses the mapping processor to obtain URLs and processors of all registered interfaces. The springIOC container is used for managing the dependency relationship among the objects, and the phenomenon injection is completed by injecting the springIOC container, so that the application can be released from the complex object dependency relationship. In this embodiment, the SpringIOC container is used to free up registered URLs and processors.
According to the obtained URLs of all the registered interfaces and the processor, the URLs of the registered interfaces are divided into version numbers and paths, the version numbers and the paths of the registered interfaces are stored in a first set, and the mapping relation between the paths of the registered interfaces and the processor is stored in a second set. By storing the registered version number and path of the interface in the first set, when the first processor is not found, the maximum version number lower than the first version number is conveniently found; and storing the mapping relation between the registered interface path and the processor in the second set, so that the processor of the version corresponding to the called interface can be conveniently found.
Specifically, the interface provider acquires a set of all interface version numbers from the system, that is, a fourth set, where the fourth set includes version numbers of all unregistered interfaces and version numbers of all registered interfaces, and subtracts the first set from the fourth set to obtain a third set, where the third set includes version numbers and paths of all unregistered interfaces.
Specifically, the interface provider traverses the sorted third set, and performs step 305 to step 307 for each version number of the traversed unregistered interface.
And 308, registering the corresponding relation between the second processor and the first version number in the mapping relation.
It should be noted that, in this embodiment, in order to enable all unregistered interface versions to search for corresponding processors when being called, after acquiring the version numbers of all unregistered interfaces in step 303, steps 305 to 308 are repeatedly executed until all unregistered version numbers are registered, that is, the corresponding relationship between the version numbers of all unregistered interfaces and the corresponding processors is registered in the mapping relationship.
The present embodiment is substantially the same as the first embodiment, and is different in that before receiving an interface call request, a set of unregistered interface version numbers is obtained, so that a correspondence between the unregistered interface version numbers and corresponding processors is registered in a mapping relationship, and in addition, by sorting the unregistered interface version numbers in an ascending order, a maximum version number lower than a current version number is conveniently obtained, so that a processor of a second version number is obtained in a case where a processor of a first version number cannot be found.
The steps of the above methods are divided for clarity, and the implementation may be combined into one step or split some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included, which are all within the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.
Another embodiment of the present invention relates to an interface invoking device, and details of the interface invoking device of the present embodiment are specifically described below, and the following are provided only for facilitating understanding of implementation details, and are not necessary for implementing the present embodiment, and fig. 4 is a schematic diagram of an interface invoking method described in the present embodiment, and includes: a receiving module 401, a lookup module 402, an execution module 403, and a registration module 404.
Specifically, the receiving module 401 is configured to receive an interface call request, where the interface call request carries a first version number of an interface requested to be called.
In one example, before receiving the interface call request, the method further includes: a third set is obtained, wherein the third set comprises version numbers of all unregistered interfaces.
A lookup module 402 configured to lookup a first processor corresponding to the first version number.
In one example, finding a first processor corresponding to a first version number comprises: searching a processor corresponding to the first version number of the interface according to the mapping relation; the second processor corresponding to the second version number of the search interface comprises: and searching the processor corresponding to the second version number of the interface according to the mapping relation.
The executing module 403 is configured to, if the first processor is not found, find a second processor corresponding to a second version number of the interface, and execute the call of the interface through the second processor.
A registering module 404, configured to register a mapping relationship between the second processor and the first version number, where the mapping relationship is used to store a corresponding relationship between a registered interface version number and a processor; wherein the second version number is a maximum version number lower than the first version number.
It should be understood that this embodiment is an example of the apparatus corresponding to the first embodiment, and may be implemented in cooperation with the first embodiment. The related technical details mentioned in the first embodiment are still valid in this embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related-art details mentioned in the present embodiment can also be applied to the first embodiment.
It should be noted that each module referred to in this embodiment is a logical module, and in practical applications, one logical unit may be one physical unit, may be a part of one physical unit, and may be implemented by a combination of multiple physical units. In addition, in order to highlight the innovative part of the present invention, elements that are not so closely related to solving the technical problems proposed by the present invention are not introduced in the present embodiment, but this does not indicate that other elements are not present in the present embodiment.
Another embodiment of the present invention relates to a server, as shown in fig. 5, including: at least one processor 501; and a memory 502 communicatively coupled to the at least one processor 501; the memory 502 stores instructions executable by the at least one processor 501, and the instructions are executed by the at least one processor 501, so that the at least one processor 501 can execute the method called by the interface in the above embodiments.
Where the memory and processor are connected by a bus, the bus may comprise any number of interconnected buses and bridges, the buses connecting together one or more of the various circuits of the processor and the memory. The bus may also connect various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor is transmitted over a wireless medium via an antenna, which further receives the data and transmits the data to the processor.
The processor is responsible for managing the bus and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And the memory may be used to store data used by the processor in performing operations.
Another embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The computer program realizes the above-described method embodiments when executed by a processor.
That is, as can be understood by those skilled in the art, all or part of the steps in the method for implementing the embodiments described above may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.
Claims (9)
1. A method for interface invocation, comprising:
s1: receiving an interface calling request; the interface calling request carries a first version number of an interface which is requested to be called;
s2: searching a first processor corresponding to the first version number;
s3: if the first processor is not found, a second processor corresponding to a second version number of the interface is found, and the interface is called through the second processor;
s4: registering the corresponding relation between the second processor and the first version number into a mapping relation, wherein the mapping relation is used for storing the corresponding relation between the registered interface version number and the processor;
wherein the second version number is a maximum version number lower than the first version number.
2. The method of interface invocation according to claim 1, wherein said searching for the first processor corresponding to said first version number comprises:
searching a processor corresponding to the first version number of the interface according to the mapping relation;
the searching for the second processor corresponding to the second version number of the interface includes:
and searching the processor corresponding to the second version number of the interface according to the mapping relation.
3. The interface calling method according to claim 1, wherein the mapping relationship is a mapping relationship between a URL of the interface and the processor; the URL of the interface comprises the version number and the path of the interface;
the version number and the path of the registered interface are stored in the first set, and the mapping relation between the path of the registered interface and the processor is stored in the second set.
4. The interface call method according to claim 3, further comprising, before the receiving the interface call request:
acquiring a third set, wherein the third set comprises version numbers and paths of all unregistered interfaces;
traversing the third set, performing the S1 through the S4 for each traversed version number of the unregistered interface.
5. The method called by the interface of claim 4, wherein after said obtaining the third set and before said traversing the third set, further comprising:
and sorting the version numbers of all unregistered interfaces in the third set in ascending order.
6. The method of interface invocation according to claim 4, wherein said obtaining a third set comprises:
acquiring a fourth set, wherein the fourth set comprises version numbers and paths of all interfaces;
subtracting the first set from the fourth set to obtain the third set.
7. An apparatus for interface invocation, comprising:
the receiving module is used for receiving an interface calling request; the interface calling request carries a first version number of an interface which is requested to be called;
the searching module is used for searching a first processor corresponding to the first version number;
the execution module is used for searching a second processor corresponding to a second version number of the interface if the first processor is not searched, and executing the calling of the interface through the second processor;
the registration module is used for registering the corresponding relation between the second processor and the first version number into a mapping relation, and the mapping relation is used for storing the corresponding relation between the registered interface version number and the processor; wherein the second version number is a maximum version number lower than the first version number.
8. A server, comprising:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method called by the interface of any one of claims 1 to 6.
9. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method of interface invocation of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111145387.6A CN114020319A (en) | 2021-09-28 | 2021-09-28 | Interface calling method, device, server and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111145387.6A CN114020319A (en) | 2021-09-28 | 2021-09-28 | Interface calling method, device, server and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114020319A true CN114020319A (en) | 2022-02-08 |
Family
ID=80054987
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111145387.6A Pending CN114020319A (en) | 2021-09-28 | 2021-09-28 | Interface calling method, device, server and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114020319A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115695555A (en) * | 2022-09-06 | 2023-02-03 | 恒生电子股份有限公司 | Interface calling method, system, processing equipment and storage medium |
-
2021
- 2021-09-28 CN CN202111145387.6A patent/CN114020319A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115695555A (en) * | 2022-09-06 | 2023-02-03 | 恒生电子股份有限公司 | Interface calling method, system, processing equipment and storage medium |
| CN115695555B (en) * | 2022-09-06 | 2023-09-12 | 恒生电子股份有限公司 | Interface calling method, system, processing device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10713375B2 (en) | Database public interface | |
| US9967370B2 (en) | OData enabled mobile software applications | |
| US10558653B2 (en) | Dynamic, variable-data attribute data service | |
| CN114064690A (en) | Data processing method and device | |
| US20170161511A1 (en) | Database public interface | |
| CN110351325B (en) | Data processing method and related equipment | |
| CN108776587B (en) | Data acquisition method and device, computer equipment and storage medium | |
| CN111797073A (en) | Database management method, electronic device, and computer-readable storage medium | |
| US11263542B2 (en) | Technologies for auto discover and connect to a rest interface | |
| US7970779B2 (en) | Application interface including dynamic transform definitions | |
| CN113760948A (en) | Data query method and device | |
| CN114020319A (en) | Interface calling method, device, server and computer readable storage medium | |
| CN113625998B (en) | Request processing method and device | |
| CN111666074B (en) | Web application customization method, related device and system | |
| CN112860308A (en) | Configuration method of interface definition, service processing method, server and storage medium | |
| CN112597423B (en) | Webpage content display method, terminal and server | |
| US10114864B1 (en) | List element query support and processing | |
| CN110471708B (en) | Method and device for acquiring configuration items based on reusable components | |
| CN110309000B (en) | Application update prompting method and terminal equipment | |
| CN115034175A (en) | Table data processing method, device, terminal and storage medium | |
| US8655910B1 (en) | Methods and systems for coupling client-side and server-side persistence frameworks | |
| CN113157722A (en) | Data processing method, device, server, system and storage medium | |
| CN111880773A (en) | Data processing method and device, electronic equipment and storage medium | |
| US11301498B2 (en) | Multi-cloud object store access | |
| CN112068899A (en) | Plug-in loading method and device, electronic equipment and storage medium |
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 |