CN112463404A - Page request processing method and device, electronic equipment and storage medium - Google Patents
Page request processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112463404A CN112463404A CN202011266438.6A CN202011266438A CN112463404A CN 112463404 A CN112463404 A CN 112463404A CN 202011266438 A CN202011266438 A CN 202011266438A CN 112463404 A CN112463404 A CN 112463404A
- Authority
- CN
- China
- Prior art keywords
- page
- identifier
- page request
- processing
- forwarding
- 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 10
- 238000012545 processing Methods 0.000 claims abstract description 64
- 238000000034 method Methods 0.000 claims abstract description 37
- 238000000926 separation method Methods 0.000 claims abstract description 29
- 230000004044 response Effects 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 5
- 230000008569 process Effects 0.000 abstract description 14
- 238000010586 diagram Methods 0.000 description 5
- 239000000126 substance Substances 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 239000002184 metal Substances 0.000 description 4
- 230000005012 migration Effects 0.000 description 3
- 238000013508 migration Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000011218 segmentation Effects 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a page request processing method and device, electronic equipment and a storage medium, which are applied to a front-end and back-end separation process. The method comprises the following steps: receiving a page request sent by a user; determining whether to forward the page request according to a page identifier in the page request and a configured routing rule; if yes, forwarding the page request to an FE for processing; otherwise, processing is carried out locally; wherein the routing rule is: and the corresponding relation between the page identifier and the forwarding identifier. The method can process the page request in the front-end and back-end separation process, and improves the user experience.
Description
Technical Field
The present invention relates to the field of image recognition technologies, and in particular, to a method and an apparatus for processing a page request, an electronic device, and a storage medium.
Background
When the service scale is small, the method is very suitable for development in a mode that front-end (FE) codes and back-end (RD) codes are written in a code warehouse to be mutually coupled, but with the expansion of the service scale, the more complex the service scene comes, FE and RD have appeal of developing to different technical stacks, the original mode no longer meets the application requirement, and the front end and the back end need to be separated.
The existing separation mode is that a page request is sent to a front end FE, when the FE needs data, an Application Program Interface (API) interface of an RD is called to obtain the data, and then the data are spliced into a page and returned to a user.
Disclosure of Invention
In view of this, the present application provides a page request processing method, an apparatus, an electronic device, and a storage medium, which can perform page request processing in a front-end and back-end separation process, so as to improve user experience.
In order to solve the technical problem, the technical scheme of the application is realized as follows:
in one embodiment, a method for processing a page request is provided, which is applied to a front-end and back-end separation process, and the method includes:
receiving a page request sent by a user;
determining whether to forward the page request according to a page identifier in the page request and a configured routing rule; if yes, forwarding the page request to an FE for processing; otherwise, processing is carried out locally;
wherein the routing rule is: and the corresponding relation between the page identifier and the forwarding identifier.
Wherein the content of the first and second substances,
when the front end and the back end of the page corresponding to the page identifier are separated, the corresponding forwarding identifier is yes;
and when the front end and the back end of the page corresponding to the page identifier are not separated, judging whether the corresponding forwarding identifier is negative.
Wherein the method further comprises:
and when the front-end and back-end separation operation is carried out on the page corresponding to the page identifier and the forwarding identifier corresponding to the page identifier is not, updating the forwarding identifier corresponding to the page identifier to be yes.
Wherein, the forwarding the page request to the FE for processing includes:
forwarding the page request to the FE, so that the FE determines whether the RD provides an API for acquiring the data corresponding to the page identifier, if so, calling the API through the FE to acquire the corresponding data and generating a page for responding; otherwise, adding a return identifier to the page request through the FE and returning.
Wherein the method further comprises:
receiving a page request carrying a return identifier returned by the FE;
and acquiring data corresponding to the page identifier in the page request, and outputting the data to the FE in a JSON format so that the FE carries out HTML page response based on the data in the JSON format.
In another embodiment, an embodiment of the present application further provides a page request processing apparatus, which is applied to a front-end and back-end separation process, and the apparatus includes: the device comprises a configuration unit, a receiving unit, a determining unit, a sending unit and a processing unit;
the configuration unit is used for configuring a routing rule; wherein the routing rule is: the corresponding relation between the page identifier and whether the identifier is forwarded or not;
the receiving unit is used for receiving a page request sent by a user;
the determining unit is configured to determine whether to forward the page request according to the page identifier in the page request received by the receiving unit and the routing rule configured by the configuration unit;
the sending unit is configured to forward the page request to the FE for processing when the determining unit determines to forward the page request;
and the processing unit is used for carrying out local processing when the determining unit determines not to forward the page request.
Wherein the content of the first and second substances,
when the front end and the back end of the page corresponding to the page identifier are separated, the corresponding forwarding identifier is yes;
and when the front end and the back end of the page corresponding to the page identifier are not separated, judging whether the corresponding forwarding identifier is negative.
Wherein the content of the first and second substances,
the configuration unit is further configured to update the forwarding identifier corresponding to the page identifier to yes when a front-end and back-end separation operation is performed on the page corresponding to the page identifier and the forwarding identifier corresponding to the page identifier is no.
Wherein the content of the first and second substances,
the sending unit is specifically configured to, when forwarding the page request to an FE for processing, forward the page request to the FE, so that the FE determines whether an RD provides an API for acquiring data corresponding to the page identifier, and otherwise, call the API to acquire corresponding data through the FE and generate a page for responding; and adding a return identifier to the page request through the FE and returning.
Wherein the content of the first and second substances,
the receiving unit is further configured to receive a page request carrying a backhaul identifier and sent back by the FE;
the processing unit is further configured to, when the receiving unit receives a page request carrying a backhaul identifier and sent back by the FE, obtain data corresponding to the page identifier in the page request;
the sending unit is further configured to output the data acquired by the processing unit to an FE in a JSON format, so that the FE performs HTML page response based on the data in the JSON format.
In another embodiment, an electronic device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the page request processing method when executing the program.
In another embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the page request processing method.
According to the technical scheme, in the process of separating the front end from the back end, the embodiment forwards the page request corresponding to the page which is subjected to front-back separation to the FE for processing, and locally processes the page corresponding to the page which is not subjected to front-back separation. According to the scheme, the page request can be processed in the front-end and back-end separation processes, and the user experience is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
FIG. 1 is a schematic diagram illustrating a page request processing flow according to an embodiment of the present application;
FIG. 2 is a schematic view of a page request processing flow in the second embodiment of the present application;
FIG. 3 is a schematic diagram of an apparatus for implementing the above technique in an embodiment of the present application;
fig. 4 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such process, method, article, or apparatus.
The technical solution of the present invention will be described in detail with specific examples. Several of the following embodiments may be combined with each other and some details of the same or similar concepts or processes may not be repeated in some embodiments.
The embodiment of the application provides a page request processing method which is applied to a page request processing device. And in the process of separating the front end from the back end, performing flow horizontal segmentation according to the page path, forwarding the page request corresponding to the page subjected to front-back separation to the FE for processing, and locally processing the page corresponding to the page not subjected to front-back separation. According to the scheme, the page request can be processed in the front-end and back-end separation processes, and the user experience is improved.
In the embodiment of the application, when front and back ends are not separated, the FE code and the RD code are written in one code warehouse, and after the front and back ends are separated, the FE code and the RD code are respectively stored in different code warehouses. In the process of separating the front end from the back end, if the page is not migrated completely, the corresponding back end code is not in the RD and is still in the original code warehouse.
The FE and the RD may be implemented in the page request processing apparatus as an FE function module and an RD function module, or implemented on other devices.
The following describes in detail a page request processing procedure in an embodiment of the present application with reference to the drawings.
Example one
Referring to fig. 1, fig. 1 is a schematic view illustrating a page request processing flow according to an embodiment of the present application. The method comprises the following specific steps:
Wherein the routing rule is: and the corresponding relation between the page identifier and the forwarding identifier.
When the front end and the back end of the page corresponding to the page identifier are separated, the corresponding forwarding identifier is yes;
and when the front end and the back end of the page corresponding to the page identifier are not separated, judging whether the corresponding forwarding identifier is negative.
When the forwarding identifier corresponding to the page identifier is yes, the page request needs to be forwarded; and when the forwarding identifier corresponding to the page identifier is negative, indicating that the front end and the back end are not separated, and processing the page identifier locally.
In the process of separating the front end and the back end, the forwarding identifier corresponding to the page identifier can be updated according to the separation condition, which is specifically as follows:
and when the front-end and back-end separation operation is carried out on the page corresponding to the page identifier and the forwarding identifier corresponding to the page identifier is not, updating the forwarding identifier corresponding to the page identifier to be yes.
In the embodiment of the application, in the process of separating the front end from the back end, the page request corresponding to the page which is subjected to front-back separation is forwarded to the FE for processing, and the page request corresponding to the page which is not subjected to front-back separation is processed locally. According to the scheme, the page request can be processed in the front-end and back-end separation processes, and the user experience is improved.
Example two
Referring to fig. 2, fig. 2 is a schematic view illustrating a page request processing flow in the second embodiment of the present application. The method comprises the following specific steps:
Wherein the routing rule is: and the corresponding relation between the page identifier and the forwarding identifier.
When the front end and the back end of the page corresponding to the page identifier are separated, the corresponding forwarding identifier is yes;
and when the front end and the back end of the page corresponding to the page identifier are not separated, judging whether the corresponding forwarding identifier is negative.
When the forwarding identifier corresponding to the page identifier is yes, the page request needs to be forwarded; and when the forwarding identifier corresponding to the page identifier is negative, indicating that the front end and the back end are not separated, and processing the page identifier locally.
In the process of separating the front end and the back end, the forwarding identifier corresponding to the page identifier can be updated according to the separation condition, which is specifically as follows:
and when the front-end and back-end separation operation is carried out on the page corresponding to the page identifier and the forwarding identifier corresponding to the page identifier is not, updating the forwarding identifier corresponding to the page identifier to be yes.
When the front end and the back end are separated, page migration is needed, and if the page migration is completed, the RD provides an API for acquiring data corresponding to the page identifier; and if the page migration is not finished, the page does not provide an API for acquiring the data corresponding to the page identifier.
And step 204, calling the API through the FE to acquire corresponding data and generate a page to respond. The flow is ended.
And if the RD does not provide the API for acquiring the data corresponding to the page identifier, the page request needs to be transmitted back to the page request processing device for processing.
And if the page request is received by the page request processing device and forwarded to the FE again, the FE adds a forwarding representation in the returned page request to indicate that the page request is a returned page request and does not need to be forwarded again, so as to avoid causing a loop.
The backhaul identifier here is only required to be agreed between the page request processing device and the FE, and is not limited to a specific implementation, for example, the backhaul identifier may be debug ═ FE.
And step 206, when receiving the page request carrying the return identifier returned by the FE, acquiring data corresponding to the page identifier in the page request, and outputting the data to the FE in the JSON format, so that the FE performs HTML page response based on the data in the JSON format. The flow is ended.
When the page request processing device receives the page request carrying the forwarding expression, the routing rule matching is carried out without using the page identification, and the data corresponding to the page identification is directly obtained locally.
When the page request processing device acquires the data corresponding to the page identifier, the data is not directly output in the form of HyperText Markup Language (HTML), but is output in JSON format to the FE for responding to the page request, so that the FE responds in the form of HTML page based on the data in Object Notation (JSON) format.
In such an implementation manner, when the FE reconstructs a page, the FE may switch the page request to the FE for processing without waiting for the RD to complete the corresponding reconstruction.
And in the process of local processing, the data corresponding to the page identifier is obtained locally, and the HTML page directly responds to the page request.
In the embodiment of the application, in the process of separating the front end from the back end, a page request corresponding to a page which is subjected to front-back separation is forwarded to the FE for processing, and if the RD provides a corresponding API in the processing process of the FE, the FE acquires data corresponding to a page identifier and generates a page for responding; otherwise, returning the page request; and processing the page request corresponding to the page which is not subjected to front-back separation locally. According to the scheme, the page request can be processed in the front-end and back-end separation processes, and the user experience is improved.
Based on the same inventive concept, the embodiment of the application also provides a page request processing device, which is applied to the front-end and back-end separation process. Referring to fig. 3, fig. 3 is a schematic structural diagram of an apparatus applied to the above technology in the embodiment of the present application. The device comprises: a configuration unit 301, a receiving unit 302, a determining unit 303, a transmitting unit 304, and a processing unit 305;
a configuration unit 301, configured to configure a routing rule; wherein the routing rule is: the corresponding relation between the page identifier and whether the identifier is forwarded or not;
a receiving unit 302, configured to receive a page request sent by a user;
a determining unit 303, configured to determine whether to forward the page request according to the page identifier in the page request received by the receiving unit 302 and the routing rule configured by the configuration unit 301;
a sending unit 304, configured to forward the page request to the FE for processing when the determining unit 303 determines to forward the page request;
a processing unit 305, configured to perform processing locally when the determining unit 303 determines not to forward the page request.
Preferably, the first and second electrodes are formed of a metal,
when the front end and the back end of the page corresponding to the page identifier are separated, the corresponding forwarding identifier is yes;
and when the front end and the back end of the page corresponding to the page identifier are not separated, judging whether the corresponding forwarding identifier is negative.
Preferably, the first and second electrodes are formed of a metal,
the configuration unit 301 is further configured to, when a front-end separation operation is performed on a page corresponding to a page identifier and a forwarding identifier corresponding to the page identifier is negative, update the forwarding identifier corresponding to the page identifier to be positive.
Preferably, the first and second electrodes are formed of a metal,
a sending unit 304, configured to forward the page request to an FE for processing when the page request is forwarded to the FE, so that the FE determines whether an RD provides an API for acquiring data corresponding to the page identifier, and if so, calls the API to acquire corresponding data through the FE to generate a page and respond; otherwise, adding a return identifier to the page request through the FE and returning.
Preferably, the first and second electrodes are formed of a metal,
a receiving unit 302, further configured to receive a page request carrying a backhaul identifier and sent back by the FE;
the processing unit 305 is further configured to, when the receiving unit 302 receives a page request carrying a backhaul identifier and returned by the FE, obtain data corresponding to the page identifier in the page request;
the sending unit 304 is further configured to output the data acquired by the processing unit 305 to the FE in the JSON format, so that the FE performs an HTML page response based on the data in the JSON format.
The units of the above embodiments may be integrated into one body, or may be separately deployed; may be combined into one unit or further divided into a plurality of sub-units.
In another embodiment, an electronic device is further provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the page request processing method when executing the program.
In another embodiment, a computer readable storage medium is also provided, having stored thereon computer instructions, which when executed by a processor, may implement the steps in the page request processing method.
Fig. 4 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention. As shown in fig. 4, the electronic device may include: a Processor (Processor)410, a communication Interface 420, a Memory (Memory)430 and a communication bus 440, wherein the Processor 410, the communication Interface 420 and the Memory 430 are communicated with each other via the communication bus 440. The processor 410 may call logic instructions in the memory 430 to perform the following method:
receiving a page request sent by a user;
determining whether to forward the page request according to a page identifier in the page request and a configured routing rule; if yes, forwarding the page request to an FE for processing; otherwise, processing is carried out locally;
wherein the routing rule is: and the corresponding relation between the page identifier and the forwarding identifier.
In addition, the logic instructions in the memory 430 may be implemented in the form of software functional units and stored in a computer readable storage medium when the software functional units are sold or used as independent products. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware. With this understanding in mind, the above-described technical solutions may be embodied in the form of a software product, which can be stored in a computer-readable storage medium such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A page request processing method is applied to a front-end and back-end separation process, and is characterized by comprising the following steps:
receiving a page request sent by a user;
determining whether to forward the page request according to a page identifier in the page request and a configured routing rule; if yes, forwarding the page request to a front end FE for processing; otherwise, processing is carried out locally;
wherein the routing rule is: and the corresponding relation between the page identifier and the forwarding identifier.
2. The method of claim 1,
when the front end and the back end of the page corresponding to the page identifier are separated, the corresponding forwarding identifier is yes;
and when the front end and the back end of the page corresponding to the page identifier are not separated, judging whether the corresponding forwarding identifier is negative.
3. The method of claim 2, further comprising:
and when the front-end and back-end separation operation is carried out on the page corresponding to the page identifier and the forwarding identifier corresponding to the page identifier is not, updating the forwarding identifier corresponding to the page identifier to be yes.
4. The method of claim 1, wherein forwarding the page request to the FE for processing comprises:
forwarding the page request to the FE, so that the FE determines whether a back end RD provides an application program interface API for acquiring data corresponding to the page identifier, if so, calling the API through the FE to acquire corresponding data and generating a page for responding; otherwise, adding a return identifier to the page request through the FE and returning.
5. The method of claim 4, further comprising:
receiving a page request carrying a return identifier returned by the FE;
and acquiring data corresponding to the page identifier in the page request, and outputting the data to the FE in an object notation JSON format, so that the FE carries out hypertext markup language (HTML) page response based on the data in the JSON format.
6. A page request processing device applied to a front-end and back-end separation process is characterized by comprising: the device comprises a configuration unit, a receiving unit, a determining unit, a sending unit and a processing unit;
the configuration unit is used for configuring a routing rule; wherein the routing rule is: the corresponding relation between the page identifier and whether the identifier is forwarded or not;
the receiving unit is used for receiving a page request sent by a user;
the determining unit is configured to determine whether to forward the page request according to the page identifier in the page request received by the receiving unit and the routing rule configured by the configuration unit;
the sending unit is configured to forward the page request to a front end FE for processing when the determining unit determines to forward the page request;
and the processing unit is used for carrying out local processing when the determining unit determines not to forward the page request.
7. The apparatus of claim 6,
the sending unit is specifically configured to, when forwarding the page request to an FE for processing, forward the page request to the FE, so that the FE determines whether a back end RD provides an application program interface API for acquiring data corresponding to the page identifier, and if so, invokes the API to acquire corresponding data through the FE and generate a page for responding; otherwise, adding a return identifier to the page request through the FE and returning.
8. The apparatus of claim 7,
the receiving unit is further configured to receive a page request carrying a backhaul identifier and sent back by the FE;
the processing unit is further configured to, when the receiving unit receives a page request carrying a backhaul identifier and sent back by the FE, obtain data corresponding to the page identifier in the page request;
the sending unit is further configured to output the data acquired by the processing unit to an FE in an object notation JSON format, so that the FE performs hypertext markup language HTML page response based on the data in the JSON format.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1-5 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011266438.6A CN112463404A (en) | 2020-11-13 | 2020-11-13 | Page request processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011266438.6A CN112463404A (en) | 2020-11-13 | 2020-11-13 | Page request processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112463404A true CN112463404A (en) | 2021-03-09 |
Family
ID=74825824
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011266438.6A Pending CN112463404A (en) | 2020-11-13 | 2020-11-13 | Page request processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112463404A (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109815430A (en) * | 2018-11-30 | 2019-05-28 | 北京金山云网络技术有限公司 | Request processing method, device, data processing server and readable storage medium storing program for executing |
-
2020
- 2020-11-13 CN CN202011266438.6A patent/CN112463404A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109815430A (en) * | 2018-11-30 | 2019-05-28 | 北京金山云网络技术有限公司 | Request processing method, device, data processing server and readable storage medium storing program for executing |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106020948A (en) | Flow process scheduling method and device | |
| CN107798108A (en) | A kind of asynchronous task querying method and equipment | |
| CN112784989A (en) | Inference system, inference method, electronic device, and computer storage medium | |
| CN109684008A (en) | Card rendering method, device, terminal and computer readable storage medium | |
| CN110609755A (en) | Message processing method, device, equipment and medium for cross-block chain node | |
| CN106454403B (en) | Data display method, equipment and system | |
| CN111582459A (en) | Method, electronic device, apparatus and storage medium for executing operation | |
| CN110209768B (en) | Question processing method and device for automatic question answering | |
| CN114500481A (en) | Service request processing method, system and device | |
| CN112463404A (en) | Page request processing method and device, electronic equipment and storage medium | |
| CN108235281A (en) | Application entity establishing resource and register method, communicating node device and terminal device | |
| CN110275701A (en) | Data processing method, device, medium and calculating equipment | |
| CN105578431A (en) | Reminding message sending device and method | |
| CN104202233A (en) | Information interacting method, terminal, server and system | |
| CN109086145B (en) | Data generation method and device and computer storage medium | |
| CN113691618A (en) | Message notification method, device, message center and storage medium | |
| CN113885753A (en) | Information input method and device, terminal equipment and storage medium | |
| CN113158115A (en) | Configuration page display method and device, electronic equipment and storage medium | |
| CN113852990A (en) | Network element control system and method | |
| CN109508370B (en) | Comment extraction method, comment extraction device and storage medium | |
| CN108076067B (en) | Method and system for authorized crawler configuration simulation login | |
| CN106569915B (en) | A kind of data back up method and data backup server | |
| CN111756935A (en) | Information processing method of intelligent system and intelligent system | |
| CN111078215A (en) | Software product application method and device, storage medium and electronic equipment | |
| CN111194026A (en) | Information sending method and device and electronic equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210309 |