CN113448652A - Request processing method and device - Google Patents

Request processing method and device Download PDF

Info

Publication number
CN113448652A
CN113448652A CN202010219269.4A CN202010219269A CN113448652A CN 113448652 A CN113448652 A CN 113448652A CN 202010219269 A CN202010219269 A CN 202010219269A CN 113448652 A CN113448652 A CN 113448652A
Authority
CN
China
Prior art keywords
interface
calling
result
information
output
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
Application number
CN202010219269.4A
Other languages
Chinese (zh)
Inventor
莫文
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Original Assignee
Beijing Jingdong Century Trading Co Ltd
Beijing Wodong Tianjun Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Century Trading Co Ltd, Beijing Wodong Tianjun Information Technology Co Ltd filed Critical Beijing Jingdong Century Trading Co Ltd
Priority to CN202010219269.4A priority Critical patent/CN113448652A/en
Publication of CN113448652A publication Critical patent/CN113448652A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/448Execution paradigms, e.g. implementations of programming paradigms
    • G06F9/4482Procedural
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25Integrating or interfacing systems involving database management systems
    • G06F16/252Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application

Abstract

The invention discloses a request processing method and device, and relates to the technical field of computers. A specific implementation mode of the method comprises the steps of receiving an interface calling request, and acquiring a calling chain identifier in the request; searching interface calling chain information according to the calling chain identifier, analyzing an interface list of the interface calling chain information, and further circulating the interface list to obtain an interface calling result; and mapping and returning the interface calling result based on the interface output result mapping information. Therefore, the implementation mode of the invention can solve the problem that the existing various different interfaces can not be automatically integrated and uniformly output.

Description

Request processing method and device
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a request processing method and apparatus.
Background
Due to the development of services, generally developed information systems are complex, more and more interfaces of the systems are provided, and more interfaces among the systems are called. In such a case, it becomes necessary to integrate the interfaces into a unified output.
In the process of implementing the invention, the inventor finds that at least the following problems exist in the prior art:
in the prior art, the integration and unified output of the interfaces cannot be realized through configuration automation, that is, a large number of different interfaces cannot be automatically integrated and unified output.
Disclosure of Invention
In view of this, embodiments of the present invention provide a request processing method and apparatus, which can solve the problem that a variety of different interfaces cannot be automatically integrated and output uniformly.
In order to achieve the above object, according to an aspect of the embodiments of the present invention, a request processing method is provided, including receiving an interface call request, and obtaining a call chain identifier in the request; searching interface calling chain information according to the calling chain identifier, analyzing an interface list of the interface calling chain information, and further circulating the interface list to obtain an interface calling result; and mapping and returning the interface calling result based on the interface output result mapping information.
Optionally, comprising:
and based on the interface output result mapping information, selecting an output interface calling result, and further mapping and returning the output interface calling result.
Optionally, the method further comprises:
selecting an output interface calling result field according to the interface output result mapping information to obtain a value corresponding to the field;
and replacing the corresponding value of the field with the corresponding field in the mapping information, calculating a final output result and returning.
Optionally, the list of cyclic interfaces comprises:
analyzing the access configuration of the current interface, and acquiring corresponding access specific value information according to the access configuration;
calling the current interface to obtain a calling result and storing the calling result as the specific value information of the input parameter called by the subsequent interface;
and circularly calling the next interface until the interface list is ended.
Optionally, before receiving the interface call request, the method further includes:
and configuring the basic interface information on a preset configuration page to record the name of each interface, the input-parameter configuration and the output-parameter configuration, and further building an interface calling chain according to the service requirement to generate an interface list and a calling chain identifier.
In addition, the invention also provides a request processing device, which comprises an interface calling module, a processing module and a processing module, wherein the interface calling module is used for receiving the interface calling request; the interface call analysis module is used for acquiring a call chain identifier in the request; the interface calling chain configuration module is used for searching the interface calling chain information according to the calling chain identifier, analyzing an interface list of the interface calling chain information and further circulating the interface list to obtain an interface calling result; and the interface output mapping configuration module is used for mapping and returning the interface calling result based on the interface output result mapping information.
Optionally, the mapping configuration module maps and returns the interface calling result based on the mapping information of the interface output result, including:
selecting an output interface calling result field according to the interface output result mapping information to obtain a value corresponding to the field;
and replacing the corresponding value of the field with the corresponding field in the mapping information, calculating a final output result and returning.
Optionally, the method further comprises:
the interface information configuration module is used for configuring the interface basic information on a preset configuration page so as to record the name of each interface and the access configuration;
and the interface calling chain configuration module is also used for building an interface calling chain according to the service requirement so as to generate an interface list and a calling chain identifier.
One embodiment of the above invention has the following advantages or benefits: the method comprises the steps of acquiring a call chain identifier in a request by adopting a receiving interface call request; searching interface calling chain information according to the calling chain identifier, analyzing an interface list of the interface calling chain information, and further circulating the interface list to obtain an interface calling result; the technical means of mapping and returning the interface calling result based on the interface output result mapping information overcomes the technical problem that the existing various different interfaces cannot be automatically integrated and uniformly output, and further achieves the technical effect of realizing the integration and uniform output of the interfaces through configuration automation.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
fig. 1 is a schematic diagram of a main flow of a request processing method according to a first embodiment of the present invention;
FIG. 2 is a schematic diagram of a main flow of a request processing method according to another embodiment of the present invention;
FIG. 3 is a schematic diagram of a main flow of a request processing method according to yet another embodiment of the present invention;
FIG. 4 is a schematic diagram of the main modules of a request processing apparatus according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of the main modules of a request processing device according to another embodiment of the present invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of a main flow of a request processing method according to a first embodiment of the present invention, as shown in fig. 1, the request processing method includes:
step S101, receiving an interface calling request, and acquiring a calling chain identifier in the request.
In some embodiments, step S101 may receive an external unified interface call request, and when the external call request is received, perform call analysis, obtain a call chain identifier in the request, and perform interface call at a back end.
As another embodiment, before performing step S101, the interface basic information may be configured on a preset configuration page to record each interface name and the entry configuration and the exit configuration. That is, the configuration page at the back end configures information of each independent interface, such as an enter configuration and an exit configuration. And then, according to the service requirement, building an interface calling chain to generate an interface list and a calling chain identifier. That is, the association relationship of the independent interfaces is configured, and the interface list of the interface call chain has order. For example: the interface 1 calls the interface 2, the interface 2 calls the interface 3, and an interface list is generated all the time. Meanwhile, the input parameters called by each interface are configured, for example, the output interface of the interface 1 is used as the input parameter of the subsequent interface, and the output of the interface 2 is also used as the input of the subsequent interface, and the recursion is performed in turn. And if all the interfaces are successfully called, obtaining the output result of the whole interface calling chain.
It should be noted that, when the interface call chain is established, an identifier, that is, a call chain identifier, is named for the interface call chain. Then the corresponding relation between the calling chain identification and the interface calling chain is configured and stored.
Step S102, searching interface calling chain information according to the calling chain identification, analyzing an interface list of the interface calling chain information, and further circulating the interface list to obtain an interface calling result.
In some embodiments, when cycling the interface list, the specific implementation process may include: analyzing the access configuration of the current interface, and acquiring the corresponding access specific value information according to the access configuration. And calling the current interface to obtain a calling result and storing the calling result as the specific value information of the input parameter called by the subsequent interface. And circularly calling the next interface until the interface list is ended.
The corresponding entry specific value information may be obtained through the interface call request, or may be obtained from the entry specific value information stored in advance.
And step S103, mapping the interface calling result based on the interface output result mapping information and returning.
In some embodiments, step S103 may map the obtained interface calling result according to a certain field name to obtain an output result with a fixed format, that is, perform field mapping on the interface calling result to convert the interface calling result into a specific format. For example, fields of JSON are configured to be mapped to additional field names, or field values. It should be noted that the output interface calling result may be selected based on the interface output result mapping information, and the output interface calling result is mapped and returned. Namely, according to the actual service requirement, the obtained interface calling result can be selectively output.
In a further embodiment, the output interface call result field may be selected according to the interface output result mapping information, so as to obtain a value corresponding to the field. And replacing the corresponding value of the field with the corresponding field in the mapping information, calculating a final output result and returning.
It can be seen that the request processing method of the present invention forms an interface call chain after arranging the input and output parameter contents and rules of the interface and configuring, so as to obtain the result of the call chain, and then converts the result into a specific result for output according to a certain mapping rule, thereby realizing the integration and uniform output of the interface.
Fig. 2 is a schematic diagram of a main flow of a request processing method according to another embodiment of the present invention, where the request processing method may include:
step S201, receiving an interface calling request, and acquiring a calling chain identifier in the request.
Step S202, searching interface calling chain information according to the calling chain identification, and analyzing an interface list of the interface calling chain information.
Step S203, looping the interface list to obtain an interface calling result. The specific implementation process comprises the following steps:
the method comprises the following steps: analyzing the access configuration of the current interface, and acquiring the corresponding access specific value information according to the access configuration.
Step two: and calling the current interface to obtain a calling result and storing the calling result as the specific value information of the input parameter called by the subsequent interface.
Step three: and circularly calling the next interface until the interface list is ended.
And step S204, selecting an output interface calling result field according to the interface output result mapping information to obtain a value corresponding to the field.
And step S205, replacing the corresponding field in the mapping information with the value corresponding to the field, calculating a final output result and returning the final output result.
Fig. 3 is a schematic diagram of a main flow of a request processing method according to still another embodiment of the present invention, and the request processing method may include:
step S301, configuring the basic interface information on a preset configuration page to record each interface name and the access configuration.
In some embodiments, the ingress and egress information is stored separately and then associated to the interface.
Step S302, according to the business requirement, an interface calling chain is set up to generate an interface list and a calling chain identifier. The specific implementation process comprises the following steps:
and determining the basic information of the called interface according to the service requirement. The called interface can be selected in the interface configuration list, the parameter information of the currently selected interface is set from the initial calling parameter information (for example, the parameter type and number conditions need to be met), and the parameter information of the current interface is used as the parameter information of the next calling interface until the service requirement is met.
In an embodiment, the called interface basic information may be determined according to data required by the service, for example: if the service needs the data a, which interface can obtain the data a can be searched, and if not, whether the data a can be obtained in an assembling mode is searched, that is, the data a is obtained by sequentially calling a plurality of interfaces.
Step S303, receiving an interface calling request, and acquiring a calling chain identifier in the request.
Step S304, searching the interface calling chain information according to the calling chain identification, and analyzing the interface list of the interface calling chain information.
Step S305, the interface list is circulated to obtain an interface calling result. The specific implementation process comprises the following steps:
the method comprises the following steps: analyzing the access configuration of the current interface, and acquiring the corresponding access specific value information according to the access configuration.
Step two: and calling the current interface to obtain a calling result and storing the calling result as the specific value information of the input parameter called by the subsequent interface.
Step three: and circularly calling the next interface until the interface list is ended.
Step S306, selecting an output interface calling result field according to the interface output result mapping information to obtain a value corresponding to the field.
And step S307, replacing the corresponding field in the mapping information with the value corresponding to the field, calculating a final output result and returning the final output result.
In summary, the request processing method of the present invention combines the configuration interface information (including the input parameter and the output parameter) into a call chain, so as to integrate the call of the interface, and achieve the technical effects of automatic integration and unified output of a variety of different interfaces, that is, the integration and unified output of the interfaces are achieved through configuration automation.
Fig. 4 is a schematic diagram of main modules of a request processing apparatus according to an embodiment of the present invention, and as shown in fig. 4, the request processing apparatus 400 includes an interface call module 401, an interface call analysis module 402, an interface call chain configuration module 403, and an interface output mapping configuration module 404. The interface calling module 401 receives an interface calling request; the interface call analysis module 402 obtains a call chain identifier in the request; the interface call chain configuration module 403 searches for interface call chain information according to the call chain identifier, analyzes an interface list of the interface call chain information, and further circulates the interface list to obtain an interface call result; the interface output mapping configuration module 404 maps and returns the interface calling result based on the interface output result mapping information.
In some embodiments, the interface output mapping configuration module 404 selects an output interface calling result based on the interface output result mapping information, and further maps and returns the output interface calling result.
In a further embodiment, the interface output mapping configuration module 404 selects an output interface call result field according to the interface output result mapping information to obtain a value corresponding to the field; and replacing the corresponding value of the field with the corresponding field in the mapping information, calculating a final output result and returning.
As further embodiments, the interface call chain configuration module 403 loops through the list of interfaces, including:
analyzing the access configuration of the current interface, and acquiring corresponding access specific value information according to the access configuration; calling the current interface to obtain a calling result and storing the calling result as the specific value information of the input parameter called by the subsequent interface; and circularly calling the next interface until the interface list is ended.
As still other embodiments, as shown in fig. 5, the method further includes:
the interface information configuration module 405 is configured to configure the interface basic information on a preset configuration page, so as to record each interface name and the access configuration.
The interface call chain configuration module 404 is further configured to build an interface call chain according to the service requirement, so as to generate an interface list and a call chain identifier.
It should be noted that, the request processing method and the request processing apparatus of the present invention have corresponding relation in the specific implementation content, and therefore, the repeated content is not described again.
Fig. 6 illustrates an exemplary system architecture 600 to which the request processing method or request processing apparatus of embodiments of the invention may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. The terminal devices 601, 602, 603 may have installed thereon various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 601, 602, 603 may be various electronic devices having request processing screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 605 may be a server providing various services, such as a background management server (for example only) providing support for shopping websites browsed by users using the terminal devices 601, 602, 603. The backend management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (for example, target push information, product information — just an example) to the terminal device.
It should be noted that the request processing method provided by the embodiment of the present invention is generally executed by the server 605, and accordingly, the computing device is generally disposed in the server 605.
It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device 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 invention.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM703, various programs and data necessary for the operation of the computer system 700 are also stored. The CPU701, the ROM702, and the RAM703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 707 including components such as a Cathode Ray Tube (CRT), a liquid crystal request processor (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer 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 of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, 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. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer 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 computer readable signal medium may also be any computer readable medium that is not a computer 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 computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprises an interface calling module, an interface calling analysis module, an interface calling chain configuration module and an interface output mapping configuration module. Wherein the names of the modules do not in some cases constitute a limitation of the module itself.
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs, and when the one or more programs are executed by a device, the device comprises a receiving interface call request, and acquires a call chain identifier in the request; searching interface calling chain information according to the calling chain identifier, analyzing an interface list of the interface calling chain information, and further circulating the interface list to obtain an interface calling result; and mapping and returning the interface calling result based on the interface output result mapping information.
According to the technical scheme of the embodiment of the invention, the problem that the existing various different interfaces cannot be automatically integrated and uniformly output can be solved.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A method for processing a request, comprising:
receiving an interface calling request, and acquiring a calling chain identifier in the request;
searching interface calling chain information according to the calling chain identifier, analyzing an interface list of the interface calling chain information, and further circulating the interface list to obtain an interface calling result;
and mapping and returning the interface calling result based on the interface output result mapping information.
2. The method of claim 1, comprising:
and based on the interface output result mapping information, selecting an output interface calling result, and further mapping and returning the output interface calling result.
3. The method of claim 2, further comprising:
selecting an output interface calling result field according to the interface output result mapping information to obtain a value corresponding to the field;
and replacing the corresponding value of the field with the corresponding field in the mapping information, calculating a final output result and returning.
4. The method of claim 1, wherein cycling the list of interfaces comprises:
analyzing the access configuration of the current interface, and acquiring corresponding access specific value information according to the access configuration;
calling the current interface to obtain a calling result and storing the calling result as the specific value information of the input parameter called by the subsequent interface;
and circularly calling the next interface until the interface list is ended.
5. The method of any of claims 1-4, wherein prior to receiving the interface call request, further comprising:
and configuring the basic interface information on a preset configuration page to record the name of each interface, the input-parameter configuration and the output-parameter configuration, and further building an interface calling chain according to the service requirement to generate an interface list and a calling chain identifier.
6. A request processing apparatus, comprising:
the interface calling module is used for receiving an interface calling request;
the interface call analysis module is used for acquiring a call chain identifier in the request;
the interface calling chain configuration module is used for searching the interface calling chain information according to the calling chain identifier, analyzing an interface list of the interface calling chain information and further circulating the interface list to obtain an interface calling result;
and the interface output mapping configuration module is used for mapping and returning the interface calling result based on the interface output result mapping information.
7. The apparatus of claim 6, wherein the interface output mapping configuration module maps and returns the interface calling result based on the interface output result mapping information, and comprises:
selecting an output interface calling result field according to the interface output result mapping information to obtain a value corresponding to the field;
and replacing the corresponding value of the field with the corresponding field in the mapping information, calculating a final output result and returning.
8. The apparatus of claim 6, further comprising:
the interface information configuration module is used for configuring the interface basic information on a preset configuration page so as to record the name of each interface and the access configuration;
and the interface calling chain configuration module is also used for building an interface calling chain according to the service requirement so as to generate an interface list and a calling chain identifier.
9. An electronic device, comprising:
one or more processors;
a storage device 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-5.
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-5.
CN202010219269.4A 2020-03-25 2020-03-25 Request processing method and device Pending CN113448652A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010219269.4A CN113448652A (en) 2020-03-25 2020-03-25 Request processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010219269.4A CN113448652A (en) 2020-03-25 2020-03-25 Request processing method and device

Publications (1)

Publication Number Publication Date
CN113448652A true CN113448652A (en) 2021-09-28

Family

ID=77807540

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010219269.4A Pending CN113448652A (en) 2020-03-25 2020-03-25 Request processing method and device

Country Status (1)

Country Link
CN (1) CN113448652A (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106790718A (en) * 2017-03-16 2017-05-31 北京搜狐新媒体信息技术有限公司 Service call link analysis method and system
CN110334007A (en) * 2019-05-27 2019-10-15 深圳壹账通智能科技有限公司 A kind of functional interface calls verification method and device, electronic equipment and storage medium

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106790718A (en) * 2017-03-16 2017-05-31 北京搜狐新媒体信息技术有限公司 Service call link analysis method and system
CN110334007A (en) * 2019-05-27 2019-10-15 深圳壹账通智能科技有限公司 A kind of functional interface calls verification method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
CN111447257B (en) Message conversion method and device
CN110471848B (en) Method and device for dynamically returning message
CN113076153B (en) Interface calling method and device
CN111427701A (en) Workflow engine system and business processing method
CN110321252B (en) Skill service resource scheduling method and device
CN112084042A (en) Message processing method and device
CN108959294B (en) Method and device for accessing search engine
CN110795328A (en) Interface testing method and device
CN110764769B (en) Method and device for processing user request
CN112948138A (en) Method and device for processing message
CN111382953A (en) Dynamic process generation method and device
CN112685481A (en) Data processing method and device
CN111414154A (en) Method and device for front-end development, electronic equipment and storage medium
CN112052152A (en) Simulation test method and device
CN113448652A (en) Request processing method and device
CN113779018A (en) Data processing method and device
CN113760487A (en) Service processing method and device
CN112306984A (en) Data source routing method and device
CN112099841A (en) Method and system for generating configuration file
CN113556370A (en) Service calling method and device
CN113472565B (en) Method, apparatus, device and computer readable medium for expanding server function
CN113132480B (en) Data transmission method, device and system
CN108984189B (en) Module parsing method and device
CN113535163A (en) Method and device for generating message
CN114189365A (en) Universal multi-tenant service authorization method and device based on field mapping

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