CN113467855B - Webpage request processing method and device, electronic equipment and storage medium - Google Patents
Webpage request processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113467855B CN113467855B CN202110703353.8A CN202110703353A CN113467855B CN 113467855 B CN113467855 B CN 113467855B CN 202110703353 A CN202110703353 A CN 202110703353A CN 113467855 B CN113467855 B CN 113467855B
- Authority
- CN
- China
- Prior art keywords
- request
- parameter information
- target
- web page
- webpage
- 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.)
- Active
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 26
- 230000004044 response Effects 0.000 claims abstract description 48
- 238000012545 processing Methods 0.000 claims abstract description 43
- 238000000034 method Methods 0.000 claims abstract description 27
- 238000012795 verification Methods 0.000 claims abstract description 11
- 238000012360 testing method Methods 0.000 claims description 33
- 238000004806 packaging method and process Methods 0.000 claims description 18
- 238000005538 encapsulation Methods 0.000 claims description 11
- 230000006870 function Effects 0.000 claims description 11
- 238000006243 chemical reaction Methods 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 13
- 238000004590 computer program Methods 0.000 description 9
- 238000012423 maintenance Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000009469 supplementation Effects 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
- G06F9/4451—User profiles; Roaming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure relates to a webpage request processing method, a webpage request processing device, electronic equipment and a storage medium. The method comprises the following steps: responding to the webpage request triggering instruction, and acquiring parameter information, service type identification and interface identification in the webpage request triggering instruction; acquiring a target configuration file matched with a service type identifier and an interface identifier, wherein the target configuration file comprises a target naming space and target parameter information, and the target naming space is obtained based on field division of the service; under the condition that the parameter information is matched with the target parameter information, the target name space, the interface identifier and the parameter information are packaged in a first request format to obtain a first webpage request; and converting the first webpage request into a second webpage request in a second request format to be sent to the server, and displaying response data of the server. According to the technical scheme provided by the disclosure, the interface can be convenient to find and maintain, and strong verification of parameters in the webpage request can be realized.
Description
Technical Field
The disclosure relates to the technical field of data processing, and in particular relates to a webpage request processing method, a webpage request processing device, electronic equipment and a storage medium.
Background
In the web page request in the front-end domain, there are various request modes, such as axios, fetch, etc. The request modes can realize web page requests by calling different interfaces. In the related art, a large number of interfaces of the webpage request are put into one file, so that the management and maintenance are not easy, and the requirement of the webpage request in a big data scene cannot be met; and the interface must learn the required parameters after the call so that the parameters cannot be checked before the call.
Disclosure of Invention
The disclosure provides a webpage request processing method, a webpage request processing device, electronic equipment and a storage medium, so as to at least solve the problems of how to enable an interface to be easy to maintain and manage and how to realize strong verification of parameters in a webpage request in the related art. The technical scheme of the present disclosure is as follows:
according to a first aspect of an embodiment of the present disclosure, there is provided a web page request processing method, including:
responding to a webpage request triggering instruction, and acquiring parameter information, a service type identifier and an interface identifier in the webpage request triggering instruction;
acquiring a target configuration file matched with the service type identifier and the interface identifier, wherein the target configuration file is used for packaging a webpage request, the target configuration file comprises a target naming space and target parameter information, the target naming space is one of a plurality of naming spaces, the plurality of naming spaces correspond to a plurality of service types, and the plurality of service types are obtained based on field division of the service;
Under the condition that the parameter information is matched with the target parameter information, packaging the target name space, the interface identifier and the parameter information in a first request format to obtain a first webpage request;
converting the first webpage request into a second webpage request with a second request format, wherein the second request format corresponds to a request mode of a server;
and sending the second webpage request to the server, and displaying response data of the second webpage request sent by the server.
In one possible implementation manner, the target configuration file further includes path information, and when the parameter information matches the target parameter information, the encapsulating, in a first request format, the target namespace, the interface identifier, and the parameter information, and the obtaining a first web page request step includes:
and under the condition that the parameter information is matched with the target parameter information, packaging the target name space, the interface identifier, the parameter information and the path information in the first request format to obtain the first webpage request.
In one possible implementation manner, the path information includes test path information and target path information, and the encapsulating, in the first request format, the target namespace, the interface identifier, the parameter information, and the path information when the parameter information matches the target parameter information, and the obtaining the first web page request step includes:
Under the condition that the test path state is opened, the target name space, the interface identifier, the parameter information and the test path information are packaged in the first request format, so that the first webpage request is obtained;
and under the condition that the test path state is closed, packaging the target name space, the interface identifier, the parameter information and the target path information in the first request format to obtain the first webpage request.
In a possible implementation manner, in a case where the parameter information matches the target parameter information, the target namespace, the interface identifier, and the parameter information are encapsulated in a first request format, and before the step of obtaining the first web page request, the method further includes:
acquiring public parameter information corresponding to the target configuration file;
and under the condition that the parameter information is matched with the target parameter information, packaging the target name space, the interface identifier and the parameter information in the first request format to obtain a first webpage request, wherein the first webpage request comprises:
and under the condition that the parameter information is matched with the target parameter information, packaging the target name space, the interface identifier, the parameter information and the public parameter information in the first request format to obtain the first webpage request.
In one possible implementation, after the step of obtaining the target profile matching the service type identifier and the interface identifier, the method further includes:
displaying alarm information under the condition that the parameter information is not matched with the target parameter information, and generating a third webpage request based on the target name space, the interface identifier, the parameter information, the target parameter information and the public parameter information;
the step of converting the first web page request into a second web page request format includes:
and converting the third webpage request into a second webpage request in a second request format.
In one possible implementation manner, the generating the third web page request step includes:
combining the parameter information, the target parameter information and the public parameter information to obtain request parameter information;
and packaging the target name space, the interface identifier and the request parameter information in the first request format to obtain the third webpage request.
In one possible implementation manner, the step of displaying response data of the second web page request sent by the server includes:
processing the response data according to a preset data processing function to obtain target response data;
and displaying the target response data.
According to a second aspect of the embodiments of the present disclosure, there is provided a web page request processing apparatus, including:
the instruction response module is configured to execute a trigger instruction responding to a webpage request, and acquire parameter information, a service type identifier and an interface identifier in the webpage request trigger instruction;
a target configuration file obtaining module, configured to perform obtaining a target configuration file matched with the service type identifier and the interface identifier, where the target configuration file is used to encapsulate a web page request, and the target configuration file includes a target namespace and target parameter information, where the target namespace is one of multiple namespaces, the multiple namespaces correspond to multiple service types, and the multiple service types are obtained based on domain division of the service;
the first webpage request acquisition module is configured to execute the packaging of the target name space, the interface identifier and the parameter information in a first request format under the condition that the parameter information is matched with the target parameter information, so as to obtain a first webpage request;
The webpage request conversion module is configured to execute a second webpage request for converting the first webpage request into a second request format, and the second request format corresponds to a request mode of the server;
and the sending and displaying module is configured to send the second webpage request to the server and display response data of the second webpage request sent by the server.
In one possible implementation manner, the target configuration file further includes path information, and the first web page request obtaining module includes:
and the first webpage request acquisition unit is configured to execute encapsulation of the target name space, the interface identifier, the parameter information and the path information in the first request format under the condition that the parameter information is matched with the target parameter information, so as to obtain the first webpage request.
In one possible implementation manner, the path information includes test path information and target path information, and the first web page request acquiring unit includes:
the first webpage request acquisition subunit is configured to execute the encapsulation of the target name space, the interface identifier, the parameter information and the test path information in the first request format under the condition that the test path state is opened, so as to obtain the first webpage request;
And the second webpage request acquisition subunit encapsulates the target name space, the interface identifier, the parameter information and the target path information in the first request format under the condition that the test path state is closed, so as to obtain the first webpage request.
In one possible implementation, the apparatus further includes:
a common parameter information acquisition module configured to perform acquisition of common parameter information corresponding to the target profile;
the first webpage request acquisition module comprises:
and the first webpage request acquisition unit is configured to execute encapsulation of the target name space, the interface identifier, the parameter information and the public parameter information in the first request format under the condition that the parameter information is matched with the target parameter information, so as to obtain the first webpage request.
In one possible implementation, the apparatus further includes:
the verification module is configured to display alarm information under the condition that the parameter information is not matched with the target parameter information, and generate a third webpage request based on the target name space, the interface identifier, the parameter information, the target parameter information and the public parameter information;
The web page request conversion module comprises:
and a web page request conversion unit configured to perform conversion of the third web page request into a second web page request of a second request format.
In one possible implementation, the verification module includes:
a parameter merging unit configured to perform merging processing on the parameter information, the target parameter information and the common parameter information to obtain request parameter information;
and the third webpage request acquisition unit is configured to perform encapsulation on the target name space, the interface identifier and the request parameter information in the first request format to obtain the third webpage request.
In one possible implementation, the sending and displaying module includes:
the target response data acquisition unit is configured to execute processing on the response data according to a preset data processing function to obtain target response data;
and a presentation unit configured to perform presentation of the target response data.
According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the method of any of the first aspects above.
According to a fourth aspect of the disclosed embodiments, there is provided a computer readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the method of any of the first aspects of the disclosed embodiments.
According to a fifth aspect of embodiments of the present disclosure, there is provided a computer program product comprising computer instructions which, when executed by a processor, cause the computer to perform the method of any one of the first aspects of embodiments of the present disclosure.
The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:
by using the configuration file to declare the name space, the interface identification and the parameter information, different interfaces can correspond to different files, so that the search, the management and the maintenance are convenient, and the requirements of big data scenes can be met; the target parameter information can be obtained directly according to the target configuration file without calling an interface, so that strong parameter verification can be realized, and the efficiency and the safety of the webpage request can be improved;
in addition, the interfaces are belonged to the namespaces, the namespaces correspond to the service types, the problem that redundant interfaces occur for the same service type is avoided, the number of the interfaces can be reduced, the cost for calling the interfaces is reduced, the front-end code quantity can be reduced, and further, the webpage request efficiency can be improved, and the resource consumption can be reduced; on the basis, the second request format is packaged by the first request format, so that the front end can save code quantity, is compatible with each http (Hypertext Transfer Protocol ) request, and does not need to change the back end processing process, and the expandability and the applicability of the webpage request processing method are better.
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 accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure and do not constitute an undue limitation on the disclosure.
FIG. 1 is a schematic diagram of an application environment, shown in accordance with an exemplary embodiment.
FIG. 2 is a flowchart illustrating a web page request processing method according to an exemplary embodiment.
Fig. 3 is a schematic diagram of a preset business structure file according to an exemplary embodiment.
FIG. 4 is a flowchart illustrating a method of exposing response data of a second web page request sent by a server, according to an example embodiment.
Fig. 5 is a flowchart illustrating a web page request processing method according to an exemplary embodiment.
Fig. 6 is a flowchart illustrating a web page request processing method according to an exemplary embodiment.
FIG. 7 is a block diagram of a web page request processing apparatus according to an example embodiment.
FIG. 8 is a block diagram illustrating an electronic device for web page request processing, according to an example embodiment.
FIG. 9 is a block diagram of an electronic device for web page request processing, according to an example embodiment.
Detailed Description
In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the technical solutions of the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
Referring to fig. 1, fig. 1 is a schematic diagram illustrating an application environment according to an exemplary embodiment, and as shown in fig. 1, the application environment may include a server 01 and a terminal 02.
In an alternative embodiment, the terminal 02 may be configured to perform web page request processing, and as an example, a web page request plug-in may be configured in the terminal 02 to implement the web page request processing. Specifically, the terminal 02 may include, but is not limited to, a smart phone, a desktop computer, a tablet computer, a notebook computer, a smart speaker, a digital assistant, an augmented reality (augmented reality, AR)/Virtual Reality (VR) device, a smart wearable device, and other types of electronic devices. Alternatively, the operating system running on the electronic device may include, but is not limited to, an android system, an IOS system, linux, windows, and the like.
In an alternative embodiment, the server 01 may be configured to respond to a web page request and return response data to the terminal 02. Specifically, the server 01 may be an independent physical server, or may be a server cluster or a distributed system formed by a plurality of physical servers, or may be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs (Content Delivery Network, content delivery networks), basic cloud computing services such as big data and artificial intelligence platforms, and the like.
In addition, it should be noted that fig. 1 is only one application environment of the image processing method provided by the present disclosure.
In the embodiment of the present disclosure, the server 01 and the terminal 02 may be directly or indirectly connected through a wired or wireless communication method, which is not limited herein.
It should be noted that, a possible sequence of steps is shown in the following figures, and is not limited to the strict order of the sequence. Some steps may be performed in parallel without mutual dependency. User information (including but not limited to user device information, user personal information, user behavior information, etc.) and data (including but not limited to data for presentation, training, etc.) referred to by this disclosure are both information and data that is authorized by the user or sufficiently authorized by the parties.
FIG. 2 is a flowchart illustrating a web page request processing method according to an exemplary embodiment. As shown in fig. 2, the following steps may be included.
In step S201, in response to the web page request trigger instruction, parameter information, service type identifier, and interface identifier in the web page request trigger instruction are acquired.
In practical application, the operation control in the webpage can be subjected to preset operation, so that the webpage request triggering instruction can be triggered, for example, the operation control can comprise a search button, a query button and the like; the preset operation may include clicking, hovering for a preset duration, etc. In one example, a search button may be clicked, a terminal may use keywords or the like to be searched as parameter information, and may acquire attribute information corresponding to the search button, where the attribute information may include a service type identifier and an interface identifier. Therefore, the webpage request triggering instruction can be generated based on the parameter information, the service type identifier and the interface identifier.
Further, in response to the webpage request triggering instruction, parameter information, service type identification and interface identification in the webpage request triggering instruction can be obtained.
In step S203, a target profile matching the service type identifier and the interface identifier is acquired.
In the embodiment of the present specification, the target configuration file may be used to encapsulate the web page request. The object configuration file may include an object namespace, an object interface identification, and object parameter information, where the object namespace may be one of a plurality of namespaces that may correspond to a plurality of service types that are based on domain partitioning of the service. The target interface identification may be one of the interface identifications.
In one example, the matching relationship of the service type identifier and the interface identifier with the target configuration file may be as shown in table 1 below:
TABLE 1
| Service type identification | Interface identification | Target configuration file |
| Service type Y1 | Interface identifier A1 | Target profile M1 |
| …… | …… | …… |
| Service type YN | Interface identifier AN | Target profile MN |
The target configuration file matched with the service type identifier and the interface identifier can be obtained through the above table 1. It should be noted that table 1 is merely an example, and is not intended to limit the present disclosure.
In one example, the target profile may be pre-built, and the matching relationship of the target profile with the service type identifier and the interface identifier shown in table 1 may be built. The target configuration file is one of the configuration files, based on which, taking one configuration file as an example, the configuration file and the matching relationship between the configuration file and the service type identifier and the interface identifier can be constructed based on the following steps:
acquiring a preset service structured file, wherein the preset service structured file can comprise a plurality of service types;
a corresponding plurality of namespaces may be constructed based on the plurality of service types;
obtaining a plurality of interfaces associated with each namespace;
packaging one name space, one interface associated with the name space and parameter information corresponding to the one interface into a configuration file; wherein the interface may be represented by an interface identifier.
And constructing a matching relation between the service profile and the service type identifier and the interface identifier, wherein the service profile can be represented by using the service profile identifier, such as a target profile M1 and a target profile MN.
In this embodiment of the present disclosure, the preset service structured file may be as shown in fig. 3, and may include multiple service types, for example, a user service, an order service order, and goods types, which is not limited in this disclosure. The plurality of service types may be obtained based on domain division of the service, for example, may be obtained based on domain-driven design (DDD) to domain division of the service, which is not limited in this disclosure, and may be divided according to actual requirements.
Wherein, a plurality of interfaces can be preset, and after a plurality of namespaces are constructed, the interfaces can be attributed to the associated namespaces. The plurality of interfaces associated with each namespace may herein refer to a plurality of interfaces that match the service type of the namespace, that is, the service information requested by the associated plurality of interfaces matches the service type of the namespace. So that one namespace, one interface corresponding to the one namespace, and parameter information corresponding to the one interface can be packaged into one configuration file. Further, a matching relationship between the configuration file and the service type identifier and the interface identifier may be constructed, for example, as shown in table 1.
In step S205, when the parameter information matches the target parameter information, the target namespace, the interface identifier, and the parameter information are encapsulated in the first request format, so as to obtain a first web page request.
In the embodiment of the present disclosure, when the parameter information is matched with the target parameter information, the target namespace, the interface identifier, and the parameter information may be encapsulated in a first request format to obtain a first web page request. As one example, the first request format may be: the namespace/interface identification corresponds to the parameter information. Wherein the parameter information may include a parameter identification and a corresponding parameter value. For example, the first web page request may be: and [ 'user/userInfo' ] ({ c:6, d:4 }) wherein user may be a namespace, userInfo may be an interface identifier, c and d may be parameter identifiers, and 6 and 4 may be parameter values corresponding to the parameter identifiers.
In step S207, the first web page request is converted into a second web page request in a second request format, and the second request format corresponds to the request mode of the server.
In practical application, the code amount can be reduced by generating the first web page request in the first request format by using the modes of the steps S201 to S205; on this basis, the first web page request may be converted into a second web page request in a second request format, for example, the second request format may be an axios request format, a fetch request format, which is not limited in this disclosure. In this way, compatibility with various http requests can be achieved without changing the background request-response procedure.
In step S209, the second web page request is sent to the server, and response data of the second web page request sent by the server is displayed.
In practical application, the second webpage request may be sent to the server, and response data of the second webpage request sent by the server may be received, and the response data may be displayed.
By using the configuration file to declare the name space, the interface identification and the parameter information, different interfaces can correspond to different files, so that the search, the management and the maintenance are convenient, and the requirements of big data scenes can be met; the target parameter information can be obtained directly according to the target configuration file without calling an interface, so that strong parameter verification can be realized, and the efficiency and the safety of the webpage request can be improved;
In addition, the interfaces are belonged to the namespaces, the namespaces correspond to the service types, the problem that redundant interfaces occur for the same service type is avoided, the number of the interfaces can be reduced, the cost for calling the interfaces is reduced, the front-end code quantity can be reduced, and further, the webpage request efficiency can be improved, and the resource consumption can be reduced; on the basis, the first request format is packaged for the second request format, so that the front end can save code quantity, is compatible with each http request, does not need to change a back-end processing process, and the expandability and the applicability of the webpage request processing method are good.
FIG. 4 is a flowchart illustrating a method of exposing response data of a second web page request sent by a server, according to an example embodiment. In one possible implementation, the step 209 may include:
in step S401, processing the response data according to a preset data processing function to obtain target response data;
in step S403, target response data is displayed.
In practical applications, in the case that the target configuration file includes a preset data processing function, for example, a requestDataCallback function, as shown in table 2, response data may be processed according to the preset data processing function, so as to obtain target response data, and further the target response data may be displayed.
Alternatively, the first web page request may be generated according to the parameters shown in table 2, e.g., the content in apiConfig may be consistent with the content in the target profile; or the separator can be customized, and the separator can be defined as a default value "/", under the sep parameter; or common parameters may refer to common parameter information; the parameter staticnode may refer to the strong check described above; mock may refer to switching of the test path from the real path, e.g., a default value of "false" may indicate that the test path is not on.
TABLE 2
By including the preset data processing function in the target configuration file, the response data can be flexibly processed, so that flexible display of the response data is realized.
TABLE 3 Table 3
| Parameters (parameters) | Description of the invention | Default value |
| desc | Description information | “” |
| method | Calling mode | Must transmit |
| name | Name of the product. Namespace lookup | Must transmit |
| params | Parameters. Parameters to be transferred by the interface | {} |
| path | Interface address | Must transmit |
| postQuery | POST request supplementation with query | {} |
| requestExtraOption | Requesting instance additional parameter configuration, such as axios instance, etc | {} |
In one possible implementation, the target profile may also include path information, as shown in table 3. In this case, the step S205 may include: and under the condition that the parameter information is matched with the target parameter information, the target name space, the interface identifier, the parameter information and the path information are packaged in a first request format, so that a first webpage request is obtained. I.e. the first web page request may contain the requested path information, whereby an indication of the response data retrieval path may be achieved.
Table 3 is merely an example of interface corresponding parameters and is not limiting of the present disclosure. The call modes may include get and post call modes. The name may refer to an interface identifier and an interface name that are used to identify an interface for ease of invocation.
As an example, the path information may include test path information and target path information, and in the case that the parameter information matches the target parameter information, the target namespace, the interface identifier, the parameter information, and the path information are encapsulated in a first request format, and the obtaining the first web page request step may include the steps of:
under the condition that the test path state is opened, the target name space, the interface identifier, the parameter information and the test path information are packaged in a first request format, so that the first webpage request is obtained;
and under the condition that the test path state is closed, the target name space, the interface identifier, the parameter information and the target path information are packaged in a first request format, so that the first webpage request is obtained.
In practical application, the path information may be set to include test path information and target path information (real path information), so that switching of paths is achieved by testing whether the path mock is opened. Alternatively, the plug-in may select a prefix of the path according to the test path state, for example, in the case that the test path state is on, the prefix may be selected as test, which is not limited in this disclosure.
By setting at least two kinds of path information and setting the test path state, the test path state can be dynamically adjusted to realize the switching of the path information.
Fig. 5 is a flowchart illustrating a web page request processing method according to an exemplary embodiment. As shown in fig. 5, in a possible implementation manner, before step S205, the method may further include:
in step S501, common parameter information corresponding to the target profile is acquired;
accordingly, step S205 may include:
in step S503, when the parameter information matches the target parameter information, the target namespace, the interface identifier, the parameter information, and the common parameter information are encapsulated in the first request format, so as to obtain a first web page request.
In the embodiment of the present disclosure, the common parameter information of different interfaces may be stored separately, that is, the common parameter information corresponding to different target configuration files may be stored separately, where the disclosure parameter information may refer to common parameters in table 2. When the target configuration file has corresponding public parameter information, the public parameter information corresponding to the target configuration file can be obtained, so that under the condition that the parameter information is matched with the target parameter information, the target naming space, the interface identifier, the parameter information and the public parameter information are packaged in a first request format, and a first webpage request is obtained. For example, the parameter information and the public parameter information may be combined to obtain the full-size parameter information, so that the target namespace, the interface identifier, and the full-size parameter information are encapsulated in the first request format to obtain the first web page request.
By storing the common parameter information independent of the interfaces, the same common parameter information is prevented from being repeated in different interfaces, and storage resources can be saved.
Fig. 6 is a flowchart illustrating a web page request processing method according to an exemplary embodiment. As shown in fig. 6, in a possible implementation manner, after step S203, the method may further include:
in step S601, in case the parameter information does not match the target parameter information, the alert information is displayed, and a third web page request is generated based on the target namespace, the interface identification, the parameter information, the target parameter information, and the common parameter information.
Accordingly, S207 may include:
in step S603, the third web page request is converted into a second web page request in a second request format. The specific implementation of this step can be referred to S207, and will not be described herein.
In the embodiment of the present specification, the parameter information may include the number of parameters and parameter values, and the target parameter information may include the number of target parameters and target parameter values. The parameter information not matching the target parameter information may include: the number of parameters is not consistent with the number of target parameters, or the number of parameters is consistent with the number of target parameters, but there is at least one parameter value that is not valid. In this case, alarm information may be displayed to prompt the user.
Alternatively, the parameter information may include a parameter identification and a parameter value, and the target parameter information may include a target parameter identification and a target parameter value. The parameter information not matching the target parameter information may mean that the parameter identification does not match the target parameter identification, or that the parameter value does not match the target parameter value.
In one possible implementation, step S601 may include the steps of: combining the parameter information, the target parameter information and the public parameter information to obtain request parameter information; and encapsulating the target name space, the interface identifier and the request parameter information in a first request format to obtain a third webpage request.
In one example, in the event that the number of parameters corresponds to the number of target parameters, but there is at least one parameter value that is invalid, the corresponding target parameter value may be utilized instead to effect the population of parameter values. Further, the filled parameter information may be combined with the common parameter information, thereby obtaining the requested parameter information.
In another example, in the case where the number of parameters does not coincide with the number of target parameters, first parameter information that does not coincide with the parameter information may be determined from the target parameter information, that is, the first parameter information may be missing parameter information in the parameter information; and taking the parameter information in the webpage request triggering instruction as second parameter information, so that the first parameter information, the second parameter information and the public parameter information can be combined to obtain request parameter information.
The above are just two examples and do not limit the present disclosure. Through the step, the integration of the actual input parameters (parameter information), the target parameter information and the public parameter information can be realized, so that the request can be continued, and the user experience is good.
By displaying the alert information in case the parameter information does not match the target parameter information, a third web page request may be generated based on the target namespace, the interface identification, the parameter information, the target parameter information, and the common parameter information. The method not only can carry out alarm prompt on the parameter information, but also can continue webpage request.
FIG. 7 is a block diagram of a web page request processing apparatus according to an example embodiment. Referring to fig. 7, the apparatus may include:
the instruction response module 701 is configured to execute a trigger instruction in response to a web page request, and acquire parameter information, a service type identifier and an interface identifier in the web page request trigger instruction;
a target profile obtaining module 703, configured to perform obtaining a target profile matching the service type identifier and the interface identifier, where the target profile may be used to encapsulate the web page request, and the target profile may include a target namespace and target parameter information, where the target namespace is one of multiple namespaces, the multiple namespaces correspond to multiple service types, and the multiple service types are obtained by performing domain division on the service;
The first web page request obtaining module 705 is configured to perform encapsulation of the target namespace, the interface identifier, and the parameter information in a first request format under the condition that the parameter information is matched with the target parameter information, so as to obtain a first web page request;
a web page request conversion module 707 configured to execute a second web page request that converts the first web page request into a second request format, the second request format corresponding to a request manner of the server;
the sending and displaying module 709 is configured to send the second web page request to the server and display the response data of the second web page request sent by the server.
By using the configuration file to declare the name space, the interface identification and the parameter information, different interfaces can correspond to different files, so that the search, the management and the maintenance are convenient, and the requirements of big data scenes can be met; the target parameter information can be obtained directly according to the target configuration file without calling an interface, so that strong parameter verification can be realized, and the efficiency and the safety of the webpage request can be improved;
in addition, the interfaces are belonged to the namespaces, the namespaces correspond to the service types, the problem that redundant interfaces occur for the same service type is avoided, the number of the interfaces can be reduced, the cost for calling the interfaces is reduced, the front-end code quantity can be reduced, and further, the webpage request efficiency can be improved, and the resource consumption can be reduced; on the basis, the first request format is packaged for the second request format, so that the front end can save code quantity, is compatible with each http request, does not need to change a back-end processing process, and the expandability and the applicability of the webpage request processing method are good.
In one possible implementation, the target configuration file may further include path information, and the first web page request obtaining module 705 may include:
the first webpage request acquisition unit is configured to execute the packaging of the target name space, the interface identifier, the parameter information and the path information in a first request format under the condition that the parameter information is matched with the target parameter information, so as to obtain a first webpage request.
In one possible implementation, the path information includes test path information and target path information, and the first web page request acquiring unit may include:
the first webpage request acquisition subunit is configured to execute the process of packaging the target name space, the interface identifier, the parameter information and the test path information in a first request format under the condition that the test path state is opened to obtain a first webpage request;
and the second webpage request acquisition subunit encapsulates the target name space, the interface identifier, the parameter information and the target path information in a first request format under the condition that the test path state is closed, so as to obtain a first webpage request.
In one possible implementation, the apparatus may further include:
The public parameter information acquisition module is configured to acquire public parameter information corresponding to the target configuration file;
the first webpage request acquisition module comprises:
the first webpage request acquisition unit is configured to execute encapsulation of the target name space, the interface identifier, the parameter information and the public parameter information in a first request format under the condition that the parameter information is matched with the target parameter information, so as to obtain a first webpage request.
In one possible implementation, the apparatus may further include:
the verification module is configured to display alarm information under the condition that the parameter information is not matched with the target parameter information, and generate a third webpage request based on the target name space, the interface identifier, the parameter information, the target parameter information and the public parameter information;
the webpage request conversion module comprises:
and a web page request converting unit configured to execute a second web page request converting the third web page request into a second request format.
In one possible implementation, the verification module may include:
the parameter merging unit is configured to perform merging processing on the parameter information, the target parameter information and the public parameter information to obtain request parameter information;
And the third webpage request acquisition unit is configured to perform encapsulation on the target name space, the interface identifier and the request parameter information in the first request format to obtain a third webpage request.
In one possible implementation, the sending and exposing module 709 may include:
the target response data acquisition unit is configured to execute the processing of response data according to a preset data processing function to obtain target response data;
and a presentation unit configured to execute presentation of the target response data.
The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.
Fig. 8 is a block diagram illustrating an electronic device for web page request processing, which may be a terminal, according to an exemplary embodiment, and an internal structure diagram thereof may be as shown in fig. 8. The electronic device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the electronic device includes a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the electronic device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a method of web page request processing. The display screen of the electronic equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic equipment can be a touch layer covered on the display screen, can also be keys, a track ball or a touch pad arranged on the shell of the electronic equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 8 is merely a block diagram of a portion of the structure associated with the disclosed aspects and is not limiting of the electronic device to which the disclosed aspects apply, and that a particular electronic device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
Fig. 9 is a block diagram illustrating an electronic device for web page request processing, which may be a server, according to an exemplary embodiment, and an internal structure diagram thereof may be as shown in fig. 9. The electronic device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the electronic device is configured to provide computing and control capabilities. The memory of the electronic device includes a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the electronic device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a method of web page request processing.
It will be appreciated by those skilled in the art that the structure shown in fig. 9 is merely a block diagram of a portion of the structure associated with the disclosed aspects and is not limiting of the electronic device to which the disclosed aspects apply, and that a particular electronic device may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
In an exemplary embodiment, there is also provided an electronic device including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement a web page request processing method as in the embodiments of the present disclosure.
In an exemplary embodiment, a computer-readable storage medium is also provided, which when executed by a processor of an electronic device, causes the electronic device to perform the web page request processing method in the embodiments of the present disclosure. The computer readable storage medium may be ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In an exemplary embodiment, a computer program product containing instructions that, when run on a computer, cause the computer to perform the method of web page request processing in the embodiments of the present disclosure is also provided.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (14)
1. A web page request processing method, comprising:
responding to a webpage request triggering instruction, and acquiring parameter information, a service type identifier and an interface identifier in the webpage request triggering instruction;
acquiring a target configuration file matched with the service type identifier and the interface identifier, wherein the target configuration file is used for packaging a webpage request, the target configuration file comprises a target naming space and target parameter information, the target naming space is one of a plurality of naming spaces, the plurality of naming spaces correspond to a plurality of service types, and the plurality of service types are obtained based on field division of the service;
Under the condition that the parameter information is matched with the target parameter information, packaging the target name space, the interface identifier and the parameter information in a first request format to obtain a first webpage request;
converting the first webpage request into a second webpage request with a second request format, wherein the second request format corresponds to a request mode of a server;
transmitting the second webpage request to the server, and displaying response data of the second webpage request transmitted by the server;
wherein the method further comprises: acquiring public parameter information corresponding to the target configuration file;
correspondingly, the step of obtaining the first webpage request includes: and under the condition that the parameter information is matched with the target parameter information, packaging the target name space, the interface identifier, the parameter information and the public parameter information in the first request format to obtain the first webpage request.
2. The web page request processing method according to claim 1, wherein the target configuration file further includes path information, and the encapsulating the target namespace, the interface identifier, and the parameter information in a first request format in a case that the parameter information matches the target parameter information, the obtaining a first web page request step includes:
And under the condition that the parameter information is matched with the target parameter information, packaging the target name space, the interface identifier, the parameter information and the path information in the first request format to obtain the first webpage request.
3. The web page request processing method according to claim 2, wherein the path information includes test path information and target path information, and wherein the encapsulating the target namespace, the interface identifier, the parameter information, and the path information in the first request format in the case where the parameter information matches the target parameter information, the obtaining the first web page request step includes:
under the condition that the test path state is opened, the target name space, the interface identifier, the parameter information and the test path information are packaged in the first request format, so that the first webpage request is obtained;
and under the condition that the test path state is closed, packaging the target name space, the interface identifier, the parameter information and the target path information in the first request format to obtain the first webpage request.
4. The web page request processing method of claim 1, wherein after the step of obtaining a target profile matching the service type identifier and the interface identifier, the method further comprises:
displaying alarm information under the condition that the parameter information is not matched with the target parameter information, and generating a third webpage request based on the target name space, the interface identifier, the parameter information, the target parameter information and the public parameter information;
the step of converting the first web page request into a second web page request format includes:
and converting the third webpage request into a second webpage request in a second request format.
5. The web page request processing method as recited in claim 4, wherein the generating a third web page request step based on the target namespace, the interface identification, the parameter information, the target parameter information, and the common parameter information comprises:
combining the parameter information, the target parameter information and the public parameter information to obtain request parameter information;
and packaging the target name space, the interface identifier and the request parameter information in the first request format to obtain the third webpage request.
6. The web page request processing method as recited in claim 1, wherein the step of displaying response data of the second web page request transmitted by the server comprises:
processing the response data according to a preset data processing function to obtain target response data;
and displaying the target response data.
7. A web page request processing apparatus, comprising:
the instruction response module is configured to execute a trigger instruction responding to a webpage request, and acquire parameter information, a service type identifier and an interface identifier in the webpage request trigger instruction;
a target configuration file obtaining module, configured to perform obtaining a target configuration file matched with the service type identifier and the interface identifier, where the target configuration file is used to encapsulate a web page request, and the target configuration file includes a target namespace and target parameter information, where the target namespace is one of multiple namespaces, the multiple namespaces correspond to multiple service types, and the multiple service types are obtained based on domain division of the service;
the first webpage request acquisition module is configured to execute the packaging of the target name space, the interface identifier and the parameter information in a first request format under the condition that the parameter information is matched with the target parameter information, so as to obtain a first webpage request;
The webpage request conversion module is configured to execute a second webpage request for converting the first webpage request into a second request format, and the second request format corresponds to a request mode of the server;
a sending and displaying module configured to send the second web page request to the server and display response data of the second web page request sent by the server;
the apparatus further comprises: a common parameter information acquisition module configured to perform acquisition of common parameter information corresponding to the target profile;
the first webpage request acquisition module comprises: and the first webpage request acquisition unit is configured to execute encapsulation of the target name space, the interface identifier, the parameter information and the public parameter information in the first request format under the condition that the parameter information is matched with the target parameter information, so as to obtain the first webpage request.
8. The web page request processing apparatus of claim 7, wherein the target profile further comprises path information, and wherein the first web page request acquisition module comprises:
and the first webpage request acquisition unit is configured to execute encapsulation of the target name space, the interface identifier, the parameter information and the path information in the first request format under the condition that the parameter information is matched with the target parameter information, so as to obtain the first webpage request.
9. The web page request processing apparatus according to claim 8, wherein the path information includes test path information and target path information, and the first web page request acquiring unit includes:
the first webpage request acquisition subunit is configured to execute the encapsulation of the target name space, the interface identifier, the parameter information and the test path information in the first request format under the condition that the test path state is opened, so as to obtain the first webpage request;
and the second webpage request acquisition subunit encapsulates the target name space, the interface identifier, the parameter information and the target path information in the first request format under the condition that the test path state is closed, so as to obtain the first webpage request.
10. The web page request processing apparatus of claim 7, wherein the apparatus further comprises:
the verification module is configured to display alarm information under the condition that the parameter information is not matched with the target parameter information, and generate a third webpage request based on the target name space, the interface identifier, the parameter information, the target parameter information and the public parameter information;
The web page request conversion module comprises:
and a web page request conversion unit configured to perform conversion of the third web page request into a second web page request of a second request format.
11. The web page request processing apparatus of claim 10, wherein the verification module comprises:
a parameter merging unit configured to perform merging processing on the parameter information, the target parameter information and the common parameter information to obtain request parameter information;
and the third webpage request acquisition unit is configured to perform encapsulation on the target name space, the interface identifier and the request parameter information in the first request format to obtain the third webpage request.
12. The web page request processing apparatus of claim 7, wherein the transmitting and displaying module comprises:
the target response data acquisition unit is configured to execute processing on the response data according to a preset data processing function to obtain target response data;
and a presentation unit configured to perform presentation of the target response data.
13. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
Wherein the processor is configured to execute the instructions to implement the web page request processing method of any one of claims 1 to 6.
14. A computer readable storage medium, wherein instructions in the computer readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the web page request processing method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110703353.8A CN113467855B (en) | 2021-06-24 | 2021-06-24 | Webpage request processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110703353.8A CN113467855B (en) | 2021-06-24 | 2021-06-24 | Webpage request processing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113467855A CN113467855A (en) | 2021-10-01 |
| CN113467855B true CN113467855B (en) | 2024-03-19 |
Family
ID=77872600
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110703353.8A Active CN113467855B (en) | 2021-06-24 | 2021-06-24 | Webpage request processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113467855B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115185717B (en) * | 2022-09-14 | 2023-01-20 | 北京达佳互联信息技术有限公司 | Interface calling method and device, electronic equipment and storage medium |
| CN117389659A (en) * | 2023-09-06 | 2024-01-12 | 苏州数设科技有限公司 | Method library management method and device for industrial software |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106293688A (en) * | 2015-06-26 | 2017-01-04 | 阿里巴巴集团控股有限公司 | The processing method of a kind of web-page requests, device and system |
| CN110413423A (en) * | 2019-07-23 | 2019-11-05 | 腾讯科技（深圳）有限公司 | Data processing method, relevant apparatus, equipment and storage medium |
| CN111240763A (en) * | 2020-01-13 | 2020-06-05 | 广州虎牙科技有限公司 | Configuration updating method, device, equipment and storage medium |
| WO2020181839A1 (en) * | 2019-03-13 | 2020-09-17 | 深圳壹账通智能科技有限公司 | Page data testing method, apparatus, computer device, and storage medium |
| CN112445851A (en) * | 2019-09-02 | 2021-03-05 | 北京神州泰岳软件股份有限公司 | Plug-in ORM framework implementation method and device, electronic equipment and storage medium |
| CN112689003A (en) * | 2020-12-18 | 2021-04-20 | 平安普惠企业管理有限公司 | Service request forwarding method, device, equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110795195B (en) * | 2019-10-31 | 2023-09-26 | 百度在线网络技术（北京）有限公司 | Webpage rendering method and device, electronic equipment and storage medium |
-
2021
- 2021-06-24 CN CN202110703353.8A patent/CN113467855B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106293688A (en) * | 2015-06-26 | 2017-01-04 | 阿里巴巴集团控股有限公司 | The processing method of a kind of web-page requests, device and system |
| WO2020181839A1 (en) * | 2019-03-13 | 2020-09-17 | 深圳壹账通智能科技有限公司 | Page data testing method, apparatus, computer device, and storage medium |
| CN110413423A (en) * | 2019-07-23 | 2019-11-05 | 腾讯科技（深圳）有限公司 | Data processing method, relevant apparatus, equipment and storage medium |
| CN112445851A (en) * | 2019-09-02 | 2021-03-05 | 北京神州泰岳软件股份有限公司 | Plug-in ORM framework implementation method and device, electronic equipment and storage medium |
| CN111240763A (en) * | 2020-01-13 | 2020-06-05 | 广州虎牙科技有限公司 | Configuration updating method, device, equipment and storage medium |
| CN112689003A (en) * | 2020-12-18 | 2021-04-20 | 平安普惠企业管理有限公司 | Service request forwarding method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113467855A (en) | 2021-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113467855B (en) | Webpage request processing method and device, electronic equipment and storage medium | |
| US10776179B2 (en) | Multi-application-oriented user data management method and system | |
| CN113238756B (en) | Live broadcast service processing method and device, electronic equipment and storage medium | |
| CN113626512A (en) | Data processing method, device, equipment and readable storage medium | |
| CN114218156A (en) | Data export method, data export device, computer equipment and storage medium | |
| CN116776030A (en) | Gray release method, device, computer equipment and storage medium | |
| CN113630612B (en) | Data processing and data displaying method and device, electronic equipment and medium | |
| CN116578984A (en) | Risk management and control method, system, equipment and medium for business data | |
| CN116233253A (en) | Service processing method, device, computer equipment and storage medium | |
| CN113672829B (en) | Page display method and device, electronic equipment and storage medium | |
| CN112835573B (en) | Data query method and device, electronic equipment and storage medium | |
| CN113836428A (en) | Business pushing method and device, computer equipment and storage medium | |
| CN114840574A (en) | Data query method, server, node and storage medium | |
| CN115017538A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN112788077B (en) | Data acquisition method and device, computer equipment and computer-readable storage medium | |
| CN115905274A (en) | Data processing method and device, electronic equipment and medium | |
| CN113806652A (en) | Page generation method and device, computer equipment and storage medium | |
| CN112000313A (en) | Request response method, device, equipment and storage medium | |
| CN112714148A (en) | Interface configuration method, device, equipment and medium | |
| CN113204477B (en) | Application testing method and device, electronic equipment and storage medium | |
| CN113469735B (en) | Resource processing method and device, electronic equipment and storage medium | |
| CN113645064B (en) | Task issuing method and device, electronic equipment and storage medium | |
| CN116723002B (en) | Intelligent encryption method for power report based on situation awareness | |
| CN113656434B (en) | Data query method and device, computer equipment and storage medium | |
| CN116166350A (en) | Module hot plug method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |