CN111597059A - Interface calling request processing method and device and electronic equipment - Google Patents
Interface calling request processing method and device and electronic equipment Download PDFInfo
- Publication number
- CN111597059A CN111597059A CN202010308295.4A CN202010308295A CN111597059A CN 111597059 A CN111597059 A CN 111597059A CN 202010308295 A CN202010308295 A CN 202010308295A CN 111597059 A CN111597059 A CN 111597059A
- Authority
- CN
- China
- Prior art keywords
- interface
- target
- target interface
- module
- configuration module
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 20
- 238000000034 method Methods 0.000 claims abstract description 42
- 238000012545 processing Methods 0.000 claims abstract description 34
- 230000004044 response Effects 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 3
- 238000011161 development Methods 0.000 abstract description 6
- 230000018109 developmental process Effects 0.000 abstract description 6
- 230000033772 system development Effects 0.000 abstract description 5
- 230000008569 process Effects 0.000 description 15
- 238000010586 diagram Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 10
- 238000006243 chemical reaction Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 5
- 230000003993 interaction Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 238000005111 flow chemistry technique Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000011282 treatment Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
Abstract
The disclosure relates to an interface call request processing method and device, an electronic device and a computer readable medium. The method comprises the following steps: acquiring an interface calling request, wherein the interface calling request comprises a target interface type and interface parameters; determining a target interface configuration module in a configuration library based on the target interface category; acquiring return data by a target interface based on the target interface configuration module and the interface parameters; and assembling the return data to respond to the interface calling request. The interface calling request processing method, the interface calling request processing device, the electronic equipment and the computer readable medium enable developers to call multiple ports through a unified interface, save interface development time and improve system development efficiency.
Description
Technical Field
The present disclosure relates to the field of computer information processing, and in particular, to a method and an apparatus for processing an interface call request, an electronic device, and a computer-readable medium.
Background
In a website providing financial services, it is often necessary to provide a variety of user services, such as member registration, security verification, recommendation policy, and the like, which are often located in different servers. For the user side, it is very tedious to know the specific server where each service is located and then perform data interaction, in this case, an API gateway can be introduced to perform website access, and the user side only needs to interact with the API gateway and does not need to communicate with interfaces of each business party respectively, so that various functions of the financial service website can be realized.
For each user end accessing the inside of the financial service website, they may be implemented by many different protocols, such as PC protocol, H5 protocol, APP protocol, etc., but for the internal server of the financial service website, it is impossible to provide data support for each protocol, which may bring a great amount of tasks to the service provided by the server, so that a protocol conversion needs to be performed at the gateway layer to convert the protocol requests of various formats of the user into the corresponding protocols at the bottom of the financial server, such as HTTP- > PC protocol, etc., at the gateway layer. Therefore, in the process of gateway development, developers often need to develop conversion among a plurality of sets of network protocol interfaces, and in the process of interface gateway conversion, conversion among a large number of parameters is involved, and a minor error brings great trouble in the process of later-stage user use.
Therefore, a new interface call request processing method, apparatus, electronic device and computer readable medium are needed.
The above information disclosed in this background section is only for enhancement of understanding of the background of the disclosure and therefore it may contain information that does not constitute prior art that is already known to a person of ordinary skill in the art.
Disclosure of Invention
In view of this, the present disclosure provides an interface call request processing method, an interface call request processing apparatus, an electronic device, and a computer readable medium, which enable a developer to call multiple ports through a unified interface, save interface development time, and improve system development efficiency.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to an aspect of the present disclosure, an interface call request processing method is provided, including: acquiring an interface calling request, wherein the interface calling request comprises a target interface type and interface parameters; determining a target interface configuration module in a configuration library based on the target interface category; acquiring return data by a target interface based on the target interface configuration module and the interface parameters; and assembling the return data to respond to the interface calling request.
Optionally, the obtaining the interface call request includes: and acquiring a gateway interface calling request compiled by a hypertext preprocessor.
Optionally, the obtaining the interface call request includes: and acquiring the interface calling request through a receiving layer in the AppCore application.
Optionally, obtaining the interface call request through a receiving layer in the AppCore application includes: acquiring the interface calling request through a receiving layer in an AppCore application; and analyzing the interface calling request through a dynamic server page to obtain the target interface category and the interface parameters.
Optionally, determining a target interface configuration module in the configuration library based on the target interface category, further includes: and loading the target interface configuration module through a view layer in the AppCore application.
Optionally, determining a target interface configuration module in the configuration library based on the target interface category, further includes: generating an interface configuration module based on an interface calling command of a mobile terminal application to generate the configuration library; generating an interface configuration module based on an interface calling command of a desktop-side application to generate the configuration library; and generating an interface configuration module based on an interface calling command of the dynamic webpage to generate the configuration library.
Optionally, obtaining, by the target interface terminal, return data based on the target interface configuration module and the interface parameter includes: sending the interface parameters to the target interface configuration module through a control layer in an AppCore application; and the target interface configuration module acquires return data from the target interface terminal based on the interface parameters.
Optionally, sending the interface parameter to the target interface configuration module through a control layer in an AppCore application, further including: and realizing the routing function in the control layer based on the model, the view and the controller service processing logic.
Optionally, the obtaining, by the target interface, return data by the target interface based on the interface parameter by the target interface configuration module includes: the target interface configuration module processes the interface parameters to generate an interface command; sending the interface command to the target interface; and acquiring the return data of the target interface through a data layer in the AppCore application.
Optionally, assembling the return data to respond to the interface call request includes: assembling the return data into a hypertext preprocessor format in response to the interface call request.
According to an aspect of the present disclosure, an interface call request processing apparatus is provided, the apparatus including: the system comprises a request module, a processing module and a processing module, wherein the request module is used for acquiring an interface calling request, and the interface calling request comprises a target interface type and an interface parameter; the target module is used for determining a target interface configuration module in the configuration library based on the target interface category; the data module is used for acquiring return data by the target interface based on the target interface configuration module and the interface parameters; and the response module is used for assembling the return data to respond to the interface calling request.
Optionally, the request module is further configured to obtain a gateway interface call request compiled by a hypertext preprocessor.
Optionally, the request module is further configured to obtain the interface call request through a receiving layer in an AppCore application.
Optionally, the request module includes: the obtaining unit is used for obtaining the interface calling request through a receiving layer in the AppCore application; and the analysis unit is used for analyzing the interface calling request through a dynamic server page to obtain the target interface type and the interface parameters.
Optionally, the target module further includes: and the loading unit is used for loading the target interface configuration module through a view layer in the AppCore application.
Optionally, the target module further includes: the configuration library unit is used for generating an interface configuration module based on an interface calling command of the mobile terminal application so as to generate the configuration library; generating an interface configuration module based on an interface calling command of a desktop-side application to generate the configuration library; and generating an interface configuration module based on an interface calling command of the dynamic webpage to generate the configuration library.
Optionally, the data module includes: the sending unit is used for sending the interface parameters to the target interface configuration module through a control layer in an AppCore application; and the data unit is used for acquiring the return data by the target interface terminal based on the interface parameters by the target interface configuration module.
Optionally, the sending unit is further configured to implement a routing function in the control layer based on a model, a view, and a controller service processing logic.
Optionally, the data unit is further configured to process the interface parameter by the target interface configuration module, and generate an interface command; sending the interface command to the target interface; and acquiring the return data of the target interface through a data layer in the AppCore application.
Optionally, the response module is further configured to assemble the return data into a hypertext preprocessor format to respond to the interface call request.
According to an aspect of the present disclosure, an electronic device is provided, the electronic device including: one or more processors; storage means for storing one or more programs; when executed by one or more processors, cause the one or more processors to implement a method as above.
According to an aspect of the disclosure, a computer-readable medium is proposed, on which a computer program is stored, which program, when being executed by a processor, carries out the method as above.
According to the interface calling request processing method, the interface calling request processing device, the electronic equipment and the computer readable medium, an interface calling request is obtained, wherein the interface calling request comprises a target interface type and an interface parameter; determining a target interface configuration module in a configuration library based on the target interface category; acquiring return data by a target interface based on the target interface configuration module and the interface parameters; and the returned data is assembled to respond to the interface calling request, so that developers can call multiple ports through a unified interface, the interface development time is saved, and the system development efficiency is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings. The drawings described below are merely some embodiments of the present disclosure, and other drawings may be derived from those drawings by those of ordinary skill in the art without inventive effort.
Fig. 1 is a system block diagram illustrating an interface call request processing method and apparatus according to an exemplary embodiment.
Fig. 2 is a flow diagram illustrating a method for interface call request processing in accordance with an exemplary embodiment.
Fig. 3 is a diagram illustrating an interface call request processing method according to an example embodiment.
Fig. 4 is a flowchart illustrating an interface call request processing method according to another exemplary embodiment.
Fig. 5 is a flowchart illustrating an interface call request processing method according to another exemplary embodiment.
Fig. 6 is a block diagram illustrating an interface call request processing apparatus according to an example embodiment.
FIG. 7 is a block diagram illustrating an electronic device in accordance with an example embodiment.
FIG. 8 is a block diagram illustrating a computer-readable medium in accordance with an example embodiment.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the disclosure.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
It will be understood that, although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one element from another. Thus, a first component discussed below may be termed a second component without departing from the teachings of the disclosed concept. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
It is to be understood by those skilled in the art that the drawings are merely schematic representations of exemplary embodiments, and that the blocks or processes shown in the drawings are not necessarily required to practice the present disclosure and are, therefore, not intended to limit the scope of the present disclosure.
Fig. 1 is a system block diagram illustrating an interface call request processing method and apparatus according to an exemplary embodiment.
As shown in fig. 1, the system architecture 10 may include user terminals 101, 102, 103, a network 104 and gateway server 105, system server 106. The medium of the network 104 to provide communication links between the user terminals 101, 102, 103 and the gateway server 105; network 104 also serves as a medium for providing a communication link between system server 106 and gateway server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may interact with the gateway server 105 via the network 104 using the user terminals 101, 102, 103, and the gateway server 105 may perform protocol conversion processing on the user's information and then forward it to the system server 106. The user terminals 101, 102, 103 may have various communication client applications installed thereon, such as a financial services application, a shopping application, a web browser application, an instant messaging tool, a mailbox client, social platform software, and the like.
The user terminals 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The gateway server 105 may be a server that provides various services, such as a background management server that supports financial services-like websites browsed by users using the user terminals 101, 102, 103. The background management server can analyze and process the received user data and feed back the processing result to the administrator of the financial service website.
The gateway server 105 may for example obtain an interface call request from the user terminal 101, 102, 103, the interface call request comprising a target interface category and interface parameters; the gateway server 105 may determine a target interface configuration module in a configuration library, for example, based on the target interface category; the gateway server 105 may retrieve the return data by the target interface, e.g., based on the target interface configuration module and the interface parameters; the gateway server 105 may, for example, assemble the return data in response to the interface call request.
The gateway server 105 may be a single entity server, or may be composed of a plurality of servers, for example, it should be noted that the interface call request processing method provided by the embodiment of the present disclosure may be executed by the gateway server 105, and accordingly, the interface call request processing device may be disposed in the gateway server 105. And the web page end provided for the user to browse the financial service platform is generally located at the user terminal 101, 102, 103.
Fig. 2 is a flow diagram illustrating a method for interface call request processing in accordance with an exemplary embodiment. The interface call request processing method 20 includes at least steps S202 to S208.
As shown in fig. 2, in S202, an interface call request is obtained, where the interface call request includes a target interface category and interface parameters. The method comprises the following steps: a gateway interface call request compiled by a hypertext preprocessor (php) is obtained. PHP is a general open source scripting language. PHP is a commonly used web site programming language that is a scripting language executed on the server side.
In one embodiment, obtaining an interface call request comprises: and acquiring the interface calling request through a receiving layer in the AppCore application. The AppCore is an MVC-mode-based APP application which is constructed by taking an AspCox framework as a core.
In the AppCore application, a dynamic Server Pages (ASP) service may be added, and the dynamic Server Pages are a script platform developed by microsoft and run on a Server side, and managed by a program of Internet Information Services (IIS) under Windows.
The ASP returns data to the web browser after being analyzed by the server, so the ASP does not need to worry about whether the browser of the client can run the code of the server. Since all programs will be executed on the web server side, including all script programs embedded in ordinary HTML. After the program is executed, the server only returns the execution result to the client browser, so that the load of the client browser is reduced, and the interaction speed is greatly improved.
In one embodiment, acquiring the interface call request through a receiving layer in an AppCore application includes: acquiring the interface calling request through a receiving layer in an AppCore application; and analyzing the interface calling request through a dynamic server page to obtain the target interface category and the interface parameters.
More specifically, the receiving layer in the AppCore application is a single entry, URL mode of operation (routing function), which may contain three parameters: m, c, a; the address where a user accesses a web page may be, for example: asp? m is admin & c is index & a is login; in the AppCore application, the following treatments can be done:
firstly, positioning the target under a directory of/App/Lib/Action/Admin from m to Admin;
based on the catalog of/App/Lib/Action/Admin, positioning the file from c ═ index to a file of/App/Lib/Action/Admin/indexaction.class.asp;
once again, locate from a ═ logic to the Sub logic () function block inside indexation.
In S204, a target interface configuration module is determined in the configuration library based on the target interface category. Further comprising: and loading the target interface configuration module through a view layer in the AppCore application.
In S206, return data is obtained by the target interface based on the target interface configuration module and the interface parameters. The method comprises the following steps: sending the interface parameters to the target interface configuration module through a control layer in an AppCore application; and the target interface configuration module acquires return data from the target interface terminal based on the interface parameters.
The parameter conversion protocols of the interface ends of different types can be configured in the interface configuration module by developers, and different interface configuration modules are generated based on the parameter conversion protocols of the interface ends of different types. In practical application, different interface configuration modules are called according to the interface types for processing so as to obtain the return parameters.
In S208, the return data is assembled in response to the interface call request. The method comprises the following steps: assembling the return data into a hypertext preprocessor format in response to the interface call request. And rearranging the returned poetry sentences again according to the php format, assembling the poetry sentences into a data packet which can be analyzed by the user side, and returning the data packet to respond to the interface calling request.
Fig. 3 is a diagram illustrating an interface call request processing method according to an example embodiment. As shown in fig. 3, a developer may configure a corresponding terminal calling configuration file in advance, and may also use an AppCore scheme to develop an interface. In an actual application scene, the AppCore receives interface calling information, processes the interface calling information and returns data.
According to the interface calling request processing method, an interface calling request is obtained, wherein the interface calling request comprises a target interface type and interface parameters; determining a target interface configuration module in a configuration library based on the target interface category; acquiring return data by a target interface based on the target interface configuration module and the interface parameters; and the returned data is assembled to respond to the interface calling request, so that developers can call multiple ports through a unified interface, the interface development time is saved, and the system development efficiency is improved.
It should be clearly understood that this disclosure describes how to make and use particular examples, but the principles of this disclosure are not limited to any details of these examples. Rather, these principles can be applied to many other embodiments based on the teachings of the present disclosure.
Fig. 4 is a flowchart illustrating an interface call request processing method according to another exemplary embodiment. The flow shown in fig. 4 is a detailed description of "determining a target interface configuration module in the configuration library based on the target interface category" in S204 in the flow shown in fig. 2.
As shown in fig. 4, in S402, a target interface configuration module is determined in the configuration library based on the target interface category.
In S404, an interface configuration module is generated based on an interface call command of the mobile terminal application to generate the configuration library.
In S406, an interface configuration module is generated based on an interface call command of the desktop application to generate the configuration library.
In S408, an interface configuration module is generated based on the interface call command of the dynamic web page to generate the configuration library.
Fig. 5 is a flowchart illustrating an interface call request processing method according to another exemplary embodiment. The flow shown in fig. 5 is a detailed description of S206 "obtaining return data by the target interface based on the target interface configuration module and the interface parameter" in the flow shown in fig. 2.
As shown in fig. 5, in S502, the routing function in the control layer is implemented based on the model, view, controller service processing logic. Model (model) -view (view) -controller (controller) processing logic is a software design paradigm, and the code is organized by a method of separating business logic, data and interface display, and the business logic is gathered into one component, so that the business logic does not need to be rewritten while the interface is customized and user interaction is improved and personalized.
Where a Model is the portion of the application that is used to process the application data logic. Typically, model objects are responsible for accessing data in a database. View (View) is the part of the application that handles the display of data. Typically views are created from model data. A Controller is a part of an application that handles user interaction. Typically the controller is responsible for reading data from the view, controlling user input, and sending data to the model.
In S504, the interface parameters are sent to the target interface configuration module through a control layer in the AppCore application. Based on model (model) -view (view) -controller processing logic, the AppCore application sends the interface parameters to the target interface configuration module.
In S506, the target interface configuration module processes the interface parameter to generate an interface command. The target interface configuration module processes the interface parameters based on a preset parameter conversion protocol to generate an interface command which can be recognized by a server in the internal system.
In S508, the interface command is sent to the target interface.
In S510, return data of the target interface is acquired through a data layer in the AppCore application. The data may also be assembled, for example, to generate response data.
Those skilled in the art will appreciate that all or part of the steps implementing the above embodiments are implemented as computer programs executed by a CPU. When executed by the CPU, performs the functions defined by the above-described methods provided by the present disclosure. The program may be stored in a computer readable storage medium, which may be a read-only memory, a magnetic or optical disk, or the like.
Furthermore, it should be noted that the above-mentioned figures are only schematic illustrations of the processes involved in the methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Embodiments of the disclosed apparatus are described that may be used to perform embodiments of the disclosed methods. For details not disclosed in the embodiments of the apparatus of the present disclosure, refer to the embodiments of the method of the present disclosure.
Fig. 6 is a block diagram illustrating an interface call request processing apparatus according to an example embodiment. As shown in fig. 6, the interface call request processing means 60 includes: a request module 602, a target module 604, a data module 606, and a response module 608.
The request module 602 is configured to obtain an interface call request, where the interface call request includes a target interface category and an interface parameter; the request module 602 is further configured to obtain a gateway interface call request compiled by a hypertext preprocessor. The request module 602 is further configured to obtain the interface call request through a receiving layer in the AppCore application.
The request module 602 includes: the obtaining unit is used for obtaining the interface calling request through a receiving layer in the AppCore application; and the analysis unit is used for analyzing the interface calling request through a dynamic server page to obtain the target interface type and the interface parameters.
The target module 604 is configured to determine a target interface configuration module in the configuration library based on the target interface category; the goal module 604 further comprises: and the loading unit is used for loading the target interface configuration module through a view layer in the AppCore application.
The goal module 604 further comprises: the configuration library unit is used for generating an interface configuration module based on an interface calling command of the mobile terminal application so as to generate the configuration library; generating an interface configuration module based on an interface calling command of a desktop-side application to generate the configuration library; and generating an interface configuration module based on an interface calling command of the dynamic webpage to generate the configuration library.
The data module 606 is used for acquiring return data from the target interface based on the target interface configuration module and the interface parameters; the data module 606 includes: the sending unit is used for sending the interface parameters to the target interface configuration module through a control layer in an AppCore application; and the sending unit is also used for realizing the routing function in the control layer based on a model, a view and a controller service processing logic.
The data module 606 further comprises: and the data unit is used for acquiring the return data by the target interface terminal based on the interface parameters by the target interface configuration module. The data unit is also used for processing the interface parameters by the target interface configuration module to generate an interface command; sending the interface command to the target interface; and acquiring the return data of the target interface through a data layer in the AppCore application.
The response module 608 is used to assemble the return data to respond to the interface call request. The response module 608 is also used to assemble the return data into a hypertext preprocessor format in response to the interface call request.
According to the interface calling request processing device, an interface calling request is obtained, wherein the interface calling request comprises a target interface type and interface parameters; determining a target interface configuration module in a configuration library based on the target interface category; acquiring return data by a target interface based on the target interface configuration module and the interface parameters; and the returned data is assembled to respond to the interface calling request, so that developers can call multiple ports through a unified interface, the interface development time is saved, and the system development efficiency is improved.
FIG. 7 is a block diagram illustrating an electronic device in accordance with an example embodiment.
An electronic device 700 according to this embodiment of the disclosure is described below with reference to fig. 7. The electronic device 700 shown in fig. 7 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 7, electronic device 700 is embodied in the form of a general purpose computing device. The components of the electronic device 700 may include, but are not limited to: at least one processing unit 710, at least one memory unit 720, a bus 730 that connects the various system components (including the memory unit 720 and the processing unit 710), a display unit 740, and the like.
Wherein the storage unit stores program codes executable by the processing unit 710 to cause the processing unit 710 to perform the steps according to various exemplary embodiments of the present disclosure described in the above-mentioned electronic prescription flow processing method section of the present specification. For example, the processing unit 710 may perform the steps as shown in fig. 2, 3, 4.
The memory unit 720 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)7201 and/or a cache memory unit 7202, and may further include a read only memory unit (ROM) 7203.
The memory unit 720 may also include a program/utility 7204 having a set (at least one) of program modules 7205, such program modules 7205 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 thereof, may comprise an implementation of a network environment.
The electronic device 700 may also communicate with one or more external devices 700' (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 700, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 700 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 750. Also, the electronic device 700 may 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 the network adapter 760. The network adapter 760 may communicate with other modules of the electronic device 700 via the bus 730. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, as shown in fig. 8, the technical solution according to the embodiment of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, or a network device, etc.) to execute the above method according to the embodiment of the present disclosure.
The software product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage 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.
Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The computer readable medium carries one or more programs which, when executed by a device, cause the computer readable medium to perform the functions of: acquiring an interface calling request, wherein the interface calling request comprises a target interface type and interface parameters; determining a target interface configuration module in a configuration library based on the target interface category; acquiring return data by a target interface based on the target interface configuration module and the interface parameters; and assembling the return data to respond to the interface calling request.
Those skilled in the art will appreciate that the modules described above may be distributed in the apparatus according to the description of the embodiments, or may be modified accordingly in one or more apparatuses unique from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
Exemplary embodiments of the present disclosure are specifically illustrated and described above. It is to be understood that the present disclosure is not limited to the precise arrangements, instrumentalities, or instrumentalities described herein; on the contrary, the disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (10)
1. An interface call request processing method, comprising:
acquiring an interface calling request, wherein the interface calling request comprises a target interface type and interface parameters;
determining a target interface configuration module in a configuration library based on the target interface category;
acquiring return data by a target interface based on the target interface configuration module and the interface parameters;
and assembling the return data to respond to the interface calling request.
2. The method of claim 1, wherein obtaining an interface call request comprises:
and acquiring a gateway interface calling request compiled by a hypertext preprocessor.
3. The method of any of claims 1-2, wherein obtaining an interface call request comprises:
and acquiring the interface calling request through a receiving layer in the AppCore application.
4. The method of any one of claims 1-3, wherein obtaining the interface call request through a receiving layer in an AppCore application comprises:
acquiring the interface calling request through a receiving layer in an AppCore application;
and analyzing the interface calling request through a dynamic server page to obtain the target interface category and the interface parameters.
5. The method of any of claims 1-4, wherein determining a target interface configuration module in a configuration repository based on a target interface category, further comprises:
and loading the target interface configuration module through a view layer in the AppCore application.
6. The method of any of claims 1-5, wherein determining a target interface configuration module in a configuration repository based on a target interface category, further comprises:
generating an interface configuration module based on an interface calling command of a mobile terminal application to generate the configuration library;
generating an interface configuration module based on an interface calling command of a desktop-side application to generate the configuration library;
and generating an interface configuration module based on an interface calling command of the dynamic webpage to generate the configuration library.
7. The method of any of claims 1-6, wherein obtaining return data by the target interface side based on the target interface configuration module and the interface parameters comprises:
sending the interface parameters to the target interface configuration module through a control layer in an AppCore application;
and the target interface configuration module acquires return data from the target interface terminal based on the interface parameters.
8. An interface call request processing apparatus, comprising:
the system comprises a request module, a processing module and a processing module, wherein the request module is used for acquiring an interface calling request, and the interface calling request comprises a target interface type and an interface parameter;
the target module is used for determining a target interface configuration module in the configuration library based on the target interface category;
the data module is used for acquiring return data by the target interface based on the target interface configuration module and the interface parameters;
and the response module is used for assembling the return data to respond to the interface calling request.
9. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010308295.4A CN111597059A (en) | 2020-04-18 | 2020-04-18 | Interface calling request processing method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010308295.4A CN111597059A (en) | 2020-04-18 | 2020-04-18 | Interface calling request processing method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111597059A true CN111597059A (en) | 2020-08-28 |
Family
ID=72187551
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010308295.4A Pending CN111597059A (en) | 2020-04-18 | 2020-04-18 | Interface calling request processing method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111597059A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113590234A (en) * | 2021-07-12 | 2021-11-02 | 远光软件股份有限公司 | Method, device and equipment for automatically acquiring data and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106484421A (en) * | 2016-10-11 | 2017-03-08 | 武汉斗鱼网络科技有限公司 | A kind of method and system quickly generating api interface |
| CN107770225A (en) * | 2016-08-22 | 2018-03-06 | 北京京东尚科信息技术有限公司 | A kind of webService accesses system and the method for accessing webService |
| CN107918562A (en) * | 2016-10-11 | 2018-04-17 | 北京京东尚科信息技术有限公司 | A kind of unified interface management method and system |
| US20190199750A1 (en) * | 2017-12-21 | 2019-06-27 | International Business Machines Corporation | Temporary interface to provide intelligent application access |
| CN110324169A (en) * | 2018-03-30 | 2019-10-11 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of interface management |
| CN110891057A (en) * | 2019-11-22 | 2020-03-17 | 北京启迪区块链科技发展有限公司 | Protocol conversion method, device, equipment and storage medium |
-
2020
- 2020-04-18 CN CN202010308295.4A patent/CN111597059A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107770225A (en) * | 2016-08-22 | 2018-03-06 | 北京京东尚科信息技术有限公司 | A kind of webService accesses system and the method for accessing webService |
| CN106484421A (en) * | 2016-10-11 | 2017-03-08 | 武汉斗鱼网络科技有限公司 | A kind of method and system quickly generating api interface |
| CN107918562A (en) * | 2016-10-11 | 2018-04-17 | 北京京东尚科信息技术有限公司 | A kind of unified interface management method and system |
| US20190199750A1 (en) * | 2017-12-21 | 2019-06-27 | International Business Machines Corporation | Temporary interface to provide intelligent application access |
| CN110324169A (en) * | 2018-03-30 | 2019-10-11 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of interface management |
| CN110891057A (en) * | 2019-11-22 | 2020-03-17 | 北京启迪区块链科技发展有限公司 | Protocol conversion method, device, equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113590234A (en) * | 2021-07-12 | 2021-11-02 | 远光软件股份有限公司 | Method, device and equipment for automatically acquiring data and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108984714B (en) | Page rendering method and device, electronic equipment and computer readable medium | |
| US7992127B2 (en) | Method and system of encapsulating web site transactions for computer-aided generation of web services | |
| US20100017502A1 (en) | Web page content translator | |
| WO2020263573A1 (en) | Systems and methods for seamlessly integrating multiple products by using a common visual modeler | |
| CN109218368A (en) | Realize method, apparatus, electronic equipment and the readable medium of Http reverse proxy | |
| CN101223524A (en) | A computer implemented method for populating graphical topological displays | |
| US20100229081A1 (en) | Method for Providing a Navigation Element in an Application | |
| CN110795181A (en) | Application program interface display method and device based on skip protocol and electronic equipment | |
| US20200302350A1 (en) | Natural language processing based business domain modeling | |
| US7716573B2 (en) | Method and system for broadly sharing UML-based models | |
| US8510707B1 (en) | Mainframe-based web service development accelerator | |
| WO2023092580A1 (en) | Page display method and apparatus, storage medium, and electronic device | |
| CN104954363A (en) | Method and device for generating interface document | |
| CN110795651A (en) | Method and device for saving front-end data and electronic equipment | |
| US8555239B1 (en) | Mainframe-based web service development accelerator | |
| JP2021500650A (en) | Search engine optimization techniques | |
| CN111597059A (en) | Interface calling request processing method and device and electronic equipment | |
| WO2018197939A1 (en) | Adding voice commands to invoke web services | |
| CN112394907A (en) | Container-based delivery system construction method, application delivery method and delivery system | |
| CN112347383A (en) | Sharing link generation method and device and electronic equipment | |
| AU2018390863B2 (en) | Computer system and method for extracting dynamic content from websites | |
| CN111198738A (en) | Mobile terminal page display method and device and electronic equipment | |
| CN112384940A (en) | Mechanism for WEB crawling of electronic business resource page | |
| CN111988405B (en) | Message rewriting method of load balancing device and load balancing device | |
| US8479175B1 (en) | Mainframe-based web service development accelerator |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20200828 |