CN112003788B

CN112003788B - Data request sending method, device, equipment and medium

Info

Publication number: CN112003788B
Application number: CN202010718008.7A
Authority: CN
Inventors: 万登娅
Original assignee: Beijing Dajia Internet Information Technology Co Ltd
Current assignee: Beijing Dajia Internet Information Technology Co Ltd
Priority date: 2020-07-23
Filing date: 2020-07-23
Publication date: 2021-12-14
Anticipated expiration: 2040-07-23
Also published as: CN112003788A

Abstract

The disclosure relates to a data request sending method, a device, equipment and a medium, wherein the method comprises the following steps: before sending a data request to a server, acquiring a first routing address corresponding to the data request; when a preset first separator exists in the first routing address, acquiring a target variable in the first routing address according to the first separator; the first separator is used for separating a target variable in the first routing address and identifying that the target variable can be replaced; replacing a target variable in the first routing address with a first character string configured in advance, and deleting a first separator in the first routing address to obtain a second routing address; and sending the data request to the server according to the second routing address. By using the method disclosed by the invention, the routing address can be automatically converted from dynamic state to static state without manually converting the routing address by developers, so that the processing process of the routing address by the developers is reduced, and the development efficiency is improved.

Description

Data request sending method, device, equipment and medium

Technical Field

The present disclosure relates to the field of network technologies, and in particular, to a data request sending method, apparatus, device, and medium.

Background

In the world wide Web (Web) page development process, an application or page of an electronic device needs to send a data request to a server. Wherein, the data request is sent by the electronic equipment according to the routing address.

In the related art, since routing addresses have similarity, the same part between the routing addresses is reserved, different parts are expressed by using variables, a dynamic routing address is formed, and a data request is sent to a server by using the dynamic routing address. However, before the electronic device sends the data request to the server, the developer needs to manually convert the dynamic routing address into the static routing address, which results in low development efficiency.

Disclosure of Invention

The present disclosure provides a data request sending method, apparatus, device, and medium, to at least solve the problem in the related art that development efficiency is low due to the need of a developer to manually convert a dynamic routing address into a static routing address. The technical scheme of the disclosure is as follows:

according to a first aspect of the embodiments of the present disclosure, a data request sending method is provided, which is applied to an electronic device, and the method includes:

before sending a data request to a server, acquiring a first routing address corresponding to the data request;

when a preset first separator exists in the first routing address, acquiring a target variable in the first routing address according to the first separator; wherein the first delimiter is to separate the target variable in the first routing address and to identify that the target variable can be replaced;

replacing the target variable in the first routing address with a first character string configured in advance, and deleting the first separator in the first routing address to obtain a second routing address;

and sending the data request to the server according to the second routing address.

In one or more embodiments of the present disclosure, the obtaining the first routing address corresponding to the data request includes:

and acquiring the first routing address after the first routing address is transmitted from the data processing layer and before the first routing address is transmitted to the data exchange layer.

In one or more embodiments of the present disclosure, the obtaining a target variable in the first routing address according to the first delimiter includes:

acquiring the target variable in the parentheses from the first routing address under the condition that the first separator is in the parentheses;

acquiring the target variable between the first delimiter and the second delimiter in the first routing address if the first delimiter is a delimiter other than a bracket and a second delimiter positioned after the first delimiter exists in the first routing address;

in a case where the first delimiter is a delimiter other than a bracket and a second delimiter positioned after the first delimiter does not exist in the first routing address, acquiring the target variable in the first routing address, the target variable being all characters after the first delimiter.

In one or more embodiments of the present disclosure, after the obtaining of the target variable in the first routing address according to the first delimiter and before the replacing of the target variable in the first routing address with the preconfigured first character string, the method further includes:

and acquiring the first character string corresponding to the target variable according to the corresponding relation between the preset variable and the character string.

In one or more embodiments of the present disclosure, after obtaining the first routing address corresponding to the data request, the method further includes:

and under the condition that the first separator does not exist in the first routing address, sending the data request to the server according to the first routing address.

According to a second aspect of the embodiments of the present disclosure, there is provided a data request transmitting apparatus applied to an electronic device, the apparatus including:

the address acquisition module is configured to acquire a first routing address corresponding to a data request before sending the data request to a server;

a variable obtaining module configured to obtain a target variable in the first routing address according to a predetermined first separator when the first routing address has the first separator; wherein the first delimiter is to separate the target variable in the first routing address and to identify that the target variable can be replaced;

a variable replacement module configured to replace the target variable in the first routing address with a preconfigured first string;

a deleting module configured to delete the first delimiter in the first routing address to obtain a second routing address;

a first sending module configured to send the data request to the server according to the second routing address.

In one or more embodiments of the present disclosure, the address obtaining module is specifically configured to obtain the first routing address after the first routing address is transmitted from the data processing layer and before the first routing address is transmitted to the data exchange layer.

In one or more embodiments of the present disclosure, the variable acquiring module includes:

a first variable acquiring unit configured to acquire the target variable in a bracket from the first routing address if the first delimiter is the bracket;

a second variable acquiring unit configured to acquire the target variable between the first delimiter and the second delimiter in the first routing address, in a case where the first delimiter is a delimiter other than a bracket and there is a second delimiter positioned after the first delimiter in the first routing address;

a third variable obtaining unit configured to obtain the target variable in the first routing address, where the first delimiter is a delimiter other than a bracket and a second delimiter positioned after the first delimiter does not exist in the first routing address, and the target variable is all characters after the first delimiter.

In one or more embodiments of the present disclosure, the apparatus further comprises:

and the character string acquisition module is configured to acquire the first character string corresponding to the target variable according to a preset corresponding relation between the variable and the character string.

a second sending module configured to send the data request to the server according to the first routing address if the first delimiter does not exist in the first routing address.

According to a third aspect of the embodiments of the present disclosure, there is provided an electronic apparatus including:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the data request sending method of the first aspect.

According to a fourth aspect of the embodiments of the present disclosure, there is provided a storage medium having stored thereon computer program instructions which, when executed by a processor, implement the data request transmitting method of the first aspect.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a computer program product for executing the data request sending method of the first aspect.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

before the electronic equipment sends the data request to the server, a first routing address corresponding to the data request is obtained, when a preset first separator exists in the first routing address, the first routing address is indicated to be a dynamic routing address, then a target variable in the first routing address is obtained according to the first separator, the target variable in the first routing address is replaced by a first character string which is configured in advance, the first separator in the first routing address is deleted, and a static second routing address is obtained. And finally, sending the data request to the server according to the second routing address. Therefore, the electronic equipment can automatically realize the conversion from the dynamic routing address to the static routing address, developers do not need to manually convert the routing address, the processing process of the developers on the routing address is reduced, the labor cost is reduced, and the development efficiency is improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure and are not to be construed as limiting the disclosure.

FIG. 1 is a schematic diagram illustrating an interaction of an electronic device with a server, according to an example embodiment;

FIG. 2 is a flow chart illustrating a method of sending a data request according to an example embodiment;

FIG. 3 is a diagram illustrating a structure of a front end item in accordance with an illustrative embodiment;

FIG. 4 is a schematic diagram illustrating the structure of another front end item in accordance with an exemplary embodiment;

FIG. 5 is a flow chart illustrating another method of data request transmission in accordance with an exemplary embodiment;

FIG. 6 is a flow chart illustrating yet another method of data request transmission in accordance with an exemplary embodiment;

FIG. 7 is a flow chart illustrating yet another method of data request transmission in accordance with an exemplary embodiment;

FIG. 8 is a schematic diagram illustrating the structure of yet another front end item in accordance with an illustrative embodiment;

FIG. 9 is a flow chart illustrating yet another method of data request transmission in accordance with an exemplary embodiment;

FIG. 10 is a block diagram illustrating a data request transmitting device in accordance with an exemplary embodiment;

FIG. 11 is a block diagram illustrating another data request sending device in accordance with an illustrative embodiment;

FIG. 12 is a block diagram illustrating yet another apparatus for sending a data request in accordance with an illustrative embodiment;

FIG. 13 is a block diagram illustrating yet another apparatus for sending a data request in accordance with an illustrative embodiment;

FIG. 14 is a block diagram illustrating yet another data request transmitting device in accordance with an illustrative embodiment;

FIG. 15 is a block diagram illustrating an electronic device in accordance with an example embodiment.

Detailed Description

In order to make the technical solutions of the present disclosure better understood by those of ordinary skill in the art, the technical solutions in 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 above-described drawings 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 disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

In the Web page development process, the front-end project includes multiple pages, for example, the front-end project is a website, and one website includes multiple Web pages. As shown in fig. 1, to implement the page presentation, the developer operates the electronic device 002 to cause the electronic device 002 to transmit a data request to the server 004. Then, the electronic device 002 acquires the target data transmitted by the server 004 based on the data request, and performs page display. The electronic device 002 may be a terminal device used by a developer, and the data request may be a hypertext transfer Protocol (HTTP) request. The electronic device 002 sends the data request to the server 004 according to the routing address corresponding to the data request.

The following description takes the routing address as an Application Programming Interface (API) address as an example.

For example, a user enters a keyword in a search input box of a browser of an electronic device. The browser of the electronic equipment generates an HTTP request according to the key words input by the user. And then the electronic equipment sends the HTTP request to the API of the server according to the API address corresponding to the HTTP request. And the server acquires target source code data related to the keywords according to the HTTP request and sends the target source code data to the electronic equipment. And the browser of the electronic equipment analyzes the requested target source code data and renders the page to realize page display.

Because one data request corresponds to one routing address, if a plurality of data requests need to be sent, developers need to list the routing addresses corresponding to the plurality of data requests one by one, and therefore the developers need to write a plurality of codes to realize one-to-one listing of the routing addresses, and development efficiency is low. In addition, if routing addresses need to be added, developers are required to manually add a new routing address. This approach is very inflexible and results in a low development efficiency.

In order to solve the technical problem of low development efficiency, the routing addresses are analyzed and have similarity. Based on the method, the same part between the routing addresses can be reserved, and different parts are expressed by using variables to form the dynamic routing addresses.

For example, the routing address of the request top navigation bar is/v 3/api/top, and the routing address of the request side bar is/v 3/api/side. It can be seen that both addresses include/v 3/api/, so the same part (i.e.,/v 3/api /) between the two routing addresses can be reserved, with the different part being represented by the variable menumame. Thus, these two routing addresses are written as dynamic routing addresses as follows: v3/api/{ menuName }.

When the dynamic routing address is used for sending a data request of a page, a developer can replace menumame with top or side in a service layer of the page, and then a static routing address is obtained: v3/api/top or v 3/api/side. Then the data request of the page is sent by using/v 3/api/top or/v 3/api/side.

Therefore, by adopting the dynamic routing address, developers are not required to write a plurality of codes to list each routing address one by one, and the processing process of the developers on the routing addresses is reduced. In addition, if the routing address needs to be added, the dynamic routing address is used, and the user does not need to manually and additionally add the routing address, so that the flexibility of the dynamic routing address is higher.

However, the above-mentioned use of dynamic routing addresses still requires developers to manually convert the dynamic routing addresses into static routing addresses, which results in low development efficiency of the developers.

Based on this, in order to solve the technical problem that developers need to manually convert a dynamic routing address into a static routing address, the present disclosure provides a data request sending method. Fig. 2 is a flow chart illustrating a method of data request transmission according to an example embodiment. The data request transmission method may be used for an electronic device. As shown in fig. 2, the method comprises the steps of:

step 102: before sending a data request to a server, acquiring a first routing address corresponding to the data request;

step 104: when a preset first separator exists in the first routing address, acquiring a target variable in the first routing address according to the first separator; the first separator is used for separating a target variable in the first routing address and identifying that the target variable can be replaced;

step 106: replacing a target variable in the first routing address with a first character string configured in advance, and deleting a first separator in the first routing address to obtain a second routing address;

step 108: and sending the data request to the server according to the second routing address.

In the embodiment of the disclosure, before the electronic device sends the data request to the server, a first routing address corresponding to the data request is acquired, and when a predetermined first delimiter exists in the first routing address, it is described that the first routing address is a dynamic routing address, then a target variable in the first routing address is acquired according to the first delimiter, then the target variable in the first routing address is replaced by a first character string configured in advance, and the first delimiter in the first routing address is deleted, so that a static second routing address is obtained. And finally, sending the data request to the server according to the second routing address. Therefore, the electronic equipment can automatically realize the conversion from the dynamic routing address to the static routing address, developers do not need to manually convert the routing address, the processing process of the developers on the routing address is reduced, the labor cost is reduced, and the development efficiency is improved.

Specific implementations of the above steps are described below. Step 102 is first introduced.

In step 102, a first routing address corresponding to the data request is obtained, and the sending of the data request is suspended. It should be noted that, the electronic device may have sent the data request, but the data request is not yet transmitted to the server, and the first routing address corresponding to the data request is obtained.

As one example, step 102 may include intercepting a first routing address corresponding to the data request. For example, the first routing address may be intercepted with an interceptor. An interceptor is the object of a dynamic intercept action (action) call. It provides a mechanism that allows the developer to define the code that is executed before and after an action is executed, and to prevent execution before an action is executed, and also provides a way to extract the reusable parts of the action.

As one example, the interceptor may be an axios or catch's interceptor. Where axios and fetch are the names of Node Package management tools (NPM), respectively. axios is one of the most commonly used Ajax (Ajax is a web page development technology for creating interactive web applications) toolkits in a Visual User Environment (VUE) framework, and can communicate with a background API interface to transmit or receive data. Catch is called next generation Ajax technology, and processes data in a noun (Promise) manner. It should be noted that the interceptor is essentially an API setting of axios or fetch. The first routing address is automatically intercepted by the interceptor, and developers are not required to participate in the interception of the routing address, so that the work of the developers is reduced, and the development efficiency of the developers is improved.

This is the description of step 102, and steps 104 to 108 are described below.

In step 104, the first delimiter includes at least one of a bracket (such as curly brackets { }), a colon, and a diacritic, as one example. The target variables separated by the first separator in the first routing address can be obtained according to the first separator.

In step 106, the target variable in the dynamic first routing address may be replaced with a first character string corresponding to the first separator configured in advance, and the first separator in the first routing address is deleted, so as to obtain a static second routing address.

In step 108, the data request may be sent to the server corresponding to the second routing address.

As one example, the electronic device sends a data request to an API of the server corresponding to the second routing address based on the second routing address. For example, the first routing address is/v 3/API/{ menumame }, and after the first routing address is converted into the second routing address/v 3/API/top, the data request is sent to the API of the server corresponding to/v 3/API/top.

The following describes steps 104 to 108 by way of an example.

Assuming that the first delimiter is { }, and the first routing address is/v 3/api/{ menumame }, then the target variable separated by the first delimiter is menumame. Replacing a target variable menumame in a first routing address/v 3/api/{ menumame } with a first character string top configured in advance, and then deleting a first separator { } in the first routing address to obtain a second routing address: v 3/api/top. Then, the data request is sent to a server corresponding to/v 3/api/top.

In order to improve the development efficiency, the inventors have analyzed as follows: typically, a front-end project includes a plurality of pages, and in order to process a dynamic routing address corresponding to a data request of each page (for example, the process includes interception and dynamic-to-static conversion of the routing address), a developer is required to write code for implementing the process for each page. In the case of a large number of pages, the code written by the developer will be large. This also leads to a technical problem of relatively low development efficiency.

In addition, in the case where one front-end project is developed by a plurality of developers, the routing addresses of different pages are likely to be processed differently by different developers. For example, the code written by the developer a may intercept the routing address and automatically perform dynamic-to-static conversion on the routing address, and the code written by the developer B may intercept the routing address, but the developer B is required to manually perform dynamic-to-static conversion on the routing address. Therefore, the processing modes of the routing addresses by a plurality of developers are not uniform, and further, the front-end project is relatively troublesome to optimize in the later period.

In view of the above technical problem, one or more embodiments of the present disclosure define an interception location of a first routing address. For convenience of describing the embodiments of the present disclosure, the front-end items of the electronic device are described below. The front-end items may include a data processing layer (Controller) and a data exchange layer (service).

The data processing layer and the data exchange layer in the front-end project are explained below with reference to fig. 3. As shown in FIG. 3, the front end item also includes a render layer (view). The flow of data in the rendering layer, data processing layer, and data exchange layer is described below.

Developer input is received by the rendering layer, which then transmits data related to the developer input to the data processing layer. For example, a search input box is displayed on the rendering layer, and a search keyword input in the search input box by a user is received, and then the rendering layer transmits the search keyword to the data processing layer.

The data from the rendering layer is processed by the data processing layer and a data request is generated. For example, the data processing layer processes the space between two search keywords and generates a data request. The data processing layer then transmits the data request to the data exchange layer. In addition, the data processing layer also acquires a routing address corresponding to the data request and transmits the routing address to the data exchange layer.

After the data exchange layer acquires the data request and the corresponding routing address, the data exchange layer sends the data request to the server based on the routing address.

Based on the architecture of the front-end project, in order to solve the above-mentioned technical problems that development efficiency is low and it is inconvenient to optimize the front-end project in a later period due to the fact that a developer needs to write a code for processing a routing address for each page, in one or more embodiments of the present disclosure, the obtaining a first routing address corresponding to the data request in step 102 may include: the first routing address is obtained after transmission from the data processing layer and before transmission to the data exchange layer.

As an example, the first routing address may be any routing address that has been transferred from the data processing layer and not transferred to the data exchange layer.

An embodiment of the present disclosure is described below with reference to fig. 4.

As shown in fig. 4, before sending a data request to a server, a first routing address is obtained between a data processing layer and a data exchange layer; when a predetermined first delimiter exists in the first routing address, it is described that the first routing address is a dynamic routing address, and the dynamic first routing address is converted into a static second routing address, where the specific conversion process includes the above step 104 and step 106, and is not repeated here. Then transmitting the second routing address to a data exchange layer; and the data exchange layer sends a data request to the server according to the second routing address.

In the embodiment of the present disclosure, because the routing addresses corresponding to the data requests of the pages of the front-end item all need to be transmitted from the data processing layer to the data exchange layer, the first routing address is obtained between the data processing layer and the data exchange layer with the front-end item as a whole, so that the obtaining and the conversion of the routing addresses are realized from the item level of the front-end item. Therefore, developers can write codes once from the project level of the front-end project to realize the interception and conversion processing of the routing address, and the developers do not need to write codes for each page, so that the work of the developers is reduced, and the development efficiency is improved.

In addition, in the embodiment of the disclosure, the first routing address is uniformly acquired between the data processing layer and the data exchange layer, and the first routing address is dynamically and statically converted, so that a processing mode of uniformly processing the routing address on the project level of the front-end project is realized, different developers are prevented from adopting different routing address processing modes, and the front-end project is conveniently optimized in the later stage.

In one or more embodiments of the present application, obtaining the target variable in the first routing address according to the first delimiter may include:

under the condition that the first separator is in parentheses, acquiring a target variable in the parentheses from the first routing address;

in the case where the first delimiter is a delimiter other than a bracket and a second delimiter following the first delimiter exists in the first routing address, acquiring a target variable between the first delimiter and the second delimiter in the first routing address;

in the case where the first delimiter is a delimiter other than a bracket and there is no second delimiter located after the first delimiter in the first routing address, a target variable in the first routing address is obtained, the target variable being all characters after the first delimiter.

The following describes a case where the first separator is in parentheses.

As an example, the parentheses may be small, medium, curly, title, or double quotation marks.

Suppose the first delimiter is curly brace { }, and the first routing address is/v 3/api/{ menumame }. In this case, a string menumame in { } in the first routing address is a target variable.

The following describes a case where the first delimiter is a delimiter other than a bracket, and a second delimiter following the first delimiter exists in the first routing address.

As an example, the second delimiter is that there is a delimiter which is located after the first delimiter and is closest to the first delimiter in the first routing address.

Assuming the first delimiter is a colon, the first routing address is/v 3/api/: menuName/r 1. Since the colon is followed by the second delimiter (i.e., the adjacent/, left side of r 1) in the first routing address, the string menyname between the first delimiter (colon) and the second delimiter (left slash) in the first routing address is the target variable.

The following describes a case where the first delimiter is a delimiter other than a bracket, and a second delimiter following the first delimiter does not exist in the first routing address.

Assuming the first delimiter is a colon, the first routing address is/v 3/api/: menumame. Since there is no arbitrary delimiter after the colon in the first routing address, all the character strings menumame after the colon in the first routing address are target variables.

In combination with the above manner of acquiring the target variable, the data request transmission method according to the embodiment of the present disclosure is described below by way of an example.

Fig. 5 is a flow chart illustrating another method of data request transmission according to an example embodiment. The data request transmission method may be used for an electronic device. As shown in fig. 5, the method comprises the steps of:

step 202: before sending a data request to a server, acquiring a first routing address corresponding to the data request;

step 204: determining that a predetermined first delimiter exists in the first routing address;

step 206: under the condition that the first separator is in parentheses, acquiring a target variable in the parentheses from the first routing address;

step 208: in the case where the first delimiter is a delimiter other than a bracket and a second delimiter following the first delimiter exists in the first routing address, acquiring a target variable between the first delimiter and the second delimiter in the first routing address;

step 210: under the condition that the first delimiter is a delimiter except for brackets and a second delimiter positioned after the first delimiter does not exist in the first routing address, acquiring a target variable in the first routing address, wherein the target variable is all characters after the first delimiter;

step 212: replacing a target variable in the first routing address with a first character string configured in advance, and deleting a first separator in the first routing address to obtain a second routing address;

step 214: and sending the data request to the server according to the second routing address.

In this embodiment, step 202 is similar to step 102, step 212 is similar to step 106, and step 214 is similar to step 108, which are not repeated herein. Steps 206 to 210 in the present embodiment are three parallel examples of obtaining the target variable in step 104, respectively. Of course, the example of obtaining the target variable in step 104 is not limited to step 206 to step 210.

In one or more embodiments of the present application, as shown in fig. 6, after step 104 and before step 106, the data request sending method may further include:

step 110: and acquiring a first character string corresponding to the target variable according to the corresponding relation between the preset variable and the character string.

The following describes a data request transmission method according to an embodiment of the present disclosure, taking as an example the correspondence between the variable and the character string as the correspondence shown in table 1.

TABLE 1

Variables of	Character string
		menuName	top
abc	side

Firstly, before sending a data request to a server, the electronic equipment acquires a first routing address/v 3/api/{ menumame }; and secondly, acquiring a target variable menuName in the first routing address according to a first separator { } in the first routing address. And searching a first character string top corresponding to the target variable menuName in the table 1 according to the target variable menuName. And then deleting a first separator in the first routing address { }, and replacing a target variable menuName in the first routing address with a first character string top to obtain a second routing address/v 3/api/top. Finally, the data request is sent to the server according to the second routing address/v 3/api/top.

In the embodiment of the disclosure, according to a preset correspondence between a variable and a character string, a first character string corresponding to a target variable in a first routing address is obtained, then the target variable in the first routing address is replaced by the first character string, and a first separator is deleted to obtain a second routing address. Therefore, the dynamic first routing address is automatically converted into the static second routing address, developers do not need to manually convert the routing addresses, the work of the developers is reduced, and the development efficiency is improved.

The present disclosure provides another data request transmission method, and fig. 7 is a flowchart illustrating another data request transmission method according to an example embodiment.

As shown in fig. 7, the data request transmitting method may include:

step 302: before sending a data request to a server, acquiring a first routing address corresponding to the data request;

step 304: determining whether a first delimiter exists in the first routing address, performing step 306 if it is determined that the first delimiter exists in the first routing address, and performing step 312 if it is determined that the first delimiter does not exist in the first routing address;

step 306: acquiring a target variable in the first routing address according to the first separator;

step 308: replacing a target variable in the first routing address with a first character string, and deleting the first separator to obtain a second routing address;

step 310: sending the data request to the server according to the second routing address;

step 312: and sending the data request to the server according to the first routing address.

Step 302 shown in fig. 7 is similar to step 102 shown in fig. 2, and steps 306 to 310 shown in fig. 7 are similar to steps 204 to 208 shown in fig. 2, and are not repeated herein.

The acquired first routing address may be a dynamic routing address or a static routing address. Assuming that the acquired first routing address is/v 3/api/top or/v 3/api/side, since there is no first delimiter { } in/v 3/api/top or/v 3/api/side, the first address is a static routing address. Furthermore, the static routing address does not require address translation, and the first routing address is used to send a data request to the server.

In order to implement displaying of data requested from the server, in one or more embodiments of the present disclosure, after the data request is sent to the server according to the second routing address, or after the data request is sent to the server according to the first routing address, the data request sending method may further include:

receiving first target data sent by a server based on a data request;

processing the first target data into second target data meeting a preset rendering condition; for example, the first target data includes source code, and the first target data is processed into data of a table type;

and rendering the second target data to display the second target data in the page.

An embodiment of the present disclosure is described below with reference to fig. 8. Referring to fig. 8, there are two cases of data flow among the rendering layer, the data processing layer, and the data exchange layer in the front-end item.

The first case is that data passes through a rendering layer, a data processing layer, a data exchange layer and a server in sequence. The first case is a process of sending a data request to the server by the front-end item, and since the data flow in the first case is already described by the above corresponding text in fig. 3, repeated description is omitted here.

The second case is that the data passes through the server, the data exchange layer, the data processing layer and the rendering layer in sequence. The data flow in the second case will be specifically described below.

After the data exchange layer sends the data request to the server, the data exchange layer receives first target data sent by the server based on the data request.

The data exchange layer sends the first target data to the data processing layer.

The data processing layer processes the first target data into second target data satisfying a predetermined rendering condition. And then, the data processing layer transmits the second target data to the rendering layer, and the rendering layer renders the second target data to realize page display. Thus, the developer can view the results of the page display.

To further describe the data request sending method provided by the embodiment of the present disclosure, a routing address is taken as an API address as an example for description.

Fig. 9 is a flowchart illustrating yet another data request transmission method according to an example embodiment. The data request transmitting method may be applied to an electronic device, as shown in fig. 9, and the method may include the steps of:

step 402, intercepting a first API address by an interceptor before sending a data request to a server, after the first API address corresponding to the data request is transmitted from a data processing layer, and before the first API address is transmitted to a data exchange layer;

step 404, determining whether a first delimiter exists in the first API address, and if the first delimiter exists in the first API address, executing step 406; in the absence of the first delimiter in the first API address, the first API address may traverse the interceptor and perform step 412;

step 406, obtaining a target variable in the first API address according to the first delimiter;

step 408, acquiring a first character string corresponding to the target variable according to the corresponding relation between the variables and the character strings which are configured in advance in the interceptor;

step 410, replacing a target variable in the first API address with a first character string, and deleting a first separator in the first API address to obtain a second API address;

step 412, sending a data request to the API of the server corresponding to the second API address according to the second API address;

and step 414, sending a data request to the API of the server corresponding to the first API address according to the first API address.

Step 302 is similar to step 102 in the embodiment shown in fig. 2, step 306 is similar to step 206 in the embodiment shown in fig. 5, and step 310 is similar to step 104 in the embodiment shown in fig. 2, and is not repeated here.

In the embodiment of the present disclosure, by intercepting the first API address, in the case that the first API address is a dynamic API address, the dynamic first API address is converted into a static second API address. Due to the adoption of the dynamic API address, developers are not required to write a plurality of codes to list each API address one by one, and the processing process of the developers to the API addresses is reduced. In addition, because the conversion of the API address from dynamic state to static state is automatically realized, developers do not need to manually convert the API address, the developers do not need to pay attention to the processing of the API address, and the corresponding relation between the preset variables and the character strings is transmitted, so that the processing process of the developers on the API address is reduced, and the development efficiency is improved.

Because the API addresses corresponding to the data requests of the pages of the front-end project all need to be transmitted from the data processing layer to the data exchange layer, the first API address is intercepted between the data processing layer and the data exchange layer by taking the front-end project as a whole, and the interception and conversion processing of the API addresses from the project level of the front-end project is realized. Therefore, developers can write codes once from the project level of the front-end project to realize the interception and conversion processing of the API address, and the developers do not need to write codes for each page, so that the work of the developers is reduced, and the development efficiency is improved.

In addition, in the embodiment of the disclosure, the first API address is intercepted uniformly between the data processing layer and the data exchange layer, and the first API address is converted dynamically to statically, so that a processing mode of unifying the API addresses on the project level of the front-end project is realized, different developers are prevented from adopting different API address processing modes, and the front-end project is optimized in the later stage.

Application scenarios of the embodiments of the present disclosure are explained below.

As an example, any of the embodiments of the present disclosure may be applied to a scenario of website development. In this scenario, during development of a front-end project of a website, if a data request of a website page needs to be sent to a server, before the data request is sent to the server, the electronic device intercepts a first routing address corresponding to the page request; and then, under the condition that the first routing address is a dynamic routing address, converting the first routing address into a static second routing address, and sending the data request of the website page to the server by using the second routing address.

As an example, any of the embodiments of the present disclosure may be applied to a scenario of Application development (App). In this scenario, during development of a front-end project of an application program, if a data request of a page of the application program needs to be sent to a server, before the data request of the page of the application program is sent to the server, an electronic device intercepts a first routing address corresponding to the data request; and then, under the condition that the first routing address is a dynamic routing address, converting the first routing address into a static second routing address, and sending the data request to the server by using the second routing address.

It should be noted that the embodiments of the present disclosure are not limited to the application in the above two scenarios, and may also be applied in other scenarios, which are not limited herein.

Based on the data request sending method provided by the above embodiment, correspondingly, the application also provides a specific implementation manner of the data request device. Please see the examples below. FIG. 10 is a block diagram illustrating a data request device in accordance with an exemplary embodiment. Referring to fig. 10, the data request apparatus 500 includes:

an address obtaining module 502 configured to obtain a first routing address corresponding to the data request before sending the data request to the server;

a variable obtaining module 504, configured to, when a predetermined first delimiter exists in the first routing address, obtain a target variable in the first routing address according to the first delimiter; the first separator is used for separating a target variable in the first routing address and identifying that the target variable can be replaced;

a variable replacement module 506 configured to replace a target variable in the first routing address with a preconfigured first string;

a deleting module 508 configured to delete the first delimiter in the first routing address to obtain a second routing address;

a first sending module 510 configured to send the data request to the server according to the second routing address.

In one or more embodiments of the present disclosure, the address acquisition module 502 is specifically configured to: the first routing address is obtained after transmission from the data processing layer and before transmission to the data exchange layer.

In another data request device provided in the disclosed embodiment, fig. 11 is a block diagram of another data request device according to an exemplary embodiment. Referring to fig. 11, the main difference between fig. 11 and fig. 10 is that the variable acquiring module 504 includes:

a first variable acquiring unit configured to acquire a target variable in parentheses in the first routing address in a case where the first delimiter is in parentheses;

a second variable acquiring unit configured to acquire a target variable between the first delimiter and the second delimiter in the first routing address, in a case where the first delimiter is a delimiter other than a bracket and a second delimiter positioned after the first delimiter exists in the first routing address;

and a third variable acquiring unit configured to acquire a target variable in the first routing address in a case where the first delimiter is a delimiter other than a bracket and a second delimiter positioned after the first delimiter does not exist in the first routing address, the target variable being all characters after the first delimiter.

In another data request device provided in the disclosed embodiment, fig. 12 is a block diagram of another data request device according to an exemplary embodiment. Referring to fig. 12, the main difference between fig. 12 and fig. 10 is that the data request apparatus 500 may further include:

the character string obtaining module 512 is configured to obtain a first character string corresponding to the target variable according to a preset correspondence between the variable and the character string.

In an embodiment of the present disclosure, a further data request device is provided, and fig. 13 is a block diagram of another data request device according to an exemplary embodiment. Referring to fig. 13, the main difference between fig. 13 and fig. 10 is that the data request apparatus 500 may further include:

a second sending module 514 configured to send the data request to the server according to the first routing address in case that the first delimiter does not exist in the first routing address.

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

An embodiment of the present disclosure provides an electronic device, and fig. 14 is a block diagram illustrating a data request transmitting apparatus according to an exemplary embodiment. For example, the apparatus may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.

Referring to fig. 14, the apparatus 600 may include one or more of the following components: processing component 602, memory 604, power component 606, multimedia component 608, audio component 610, input/output interface (i.e., I/O interface) 612, sensor component 614, and communication component 616.

The processing component 602 generally controls overall operation of the device 600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 602 may include one or more processors 618 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 602 can include one or more modules that facilitate interaction between the processing component 602 and other components. For example, the processing component 602 can include a multimedia module to facilitate interaction between the multimedia component 608 and the processing component 602.

The memory 604 is configured to store various types of data to support operations at the apparatus 600. Examples of such data include instructions for any application or method operating on device 600, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 604 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

Power supply component 606 provides power to the various components of device 600. The power components 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the apparatus 600.

The multimedia component 608 includes a screen that provides an output interface between the device 600 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 600 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 610 is configured to output and/or input audio signals. For example, audio component 610 includes a Microphone (MIC) configured to receive external audio signals when apparatus 600 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in the memory 604 or transmitted via the communication component 616. In some embodiments, audio component 610 further includes a speaker for outputting audio signals.

The I/O interface 612 provides an interface between the processing component 602 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor component 614 includes one or more sensors for providing status assessment of various aspects of the apparatus 600. For example, the sensor component 614 may detect an open/closed state of the device 600, the relative positioning of components, such as a display and keypad of the device 600, the sensor component 614 may also detect a change in position of the device 600 or a component of the device 600, the presence or absence of user contact with the device 600, orientation or acceleration/deceleration of the device 600, and a change in temperature of the device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 616 is configured to facilitate communications between the apparatus 600 and other devices in a wired or wireless manner. The apparatus 600 may access a wireless network based on a communication standard, such as WiFi, an operator network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 616 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the apparatus 600 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described method of determining a speech recognition model.

An electronic device is also provided in the disclosed embodiments, and fig. 15 is a block diagram of an electronic device shown according to an exemplary embodiment. As shown in fig. 15, the electronic apparatus includes: a processor 702; a memory 704 for storing instructions executable by the processor 702; wherein the processor 702 is configured to execute the instructions to implement the data request sending method of any of the above.

In an exemplary embodiment, there is also provided a storage medium comprising instructions, such as a memory comprising instructions, executable by a processor of an apparatus to perform the above method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, a computer program product is also provided for executing the data request sending method.

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 disclosure is intended to cover any variations, 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 will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A data request sending method is applied to electronic equipment and is characterized by comprising the following steps:

2. The method according to claim 1, wherein the obtaining the first routing address corresponding to the data request includes:

3. The method of claim 1, wherein obtaining the target variable in the first routing address according to the first delimiter comprises:

obtaining the target variable in the first routing address in the case that the first delimiter is a delimiter other than a bracket and a second delimiter positioned after the first delimiter does not exist in the first routing address, wherein the target variable is all characters after the first delimiter;

and the second separator is a separator which is positioned after the first separator and is closest to the first separator in the first routing address.

4. The method of claim 1, wherein after the obtaining of the target variable in the first routing address according to the first delimiter and before the replacing of the target variable in the first routing address with the preconfigured first string, the method further comprises:

5. The method according to claim 1, wherein after obtaining the first routing address corresponding to the data request, the method further comprises:

6. A data request transmission apparatus applied to an electronic device, the apparatus comprising:

7. The apparatus according to claim 6, wherein the address obtaining module is specifically configured to obtain the first routing address after transmission from the data processing layer and before transmission to the data exchange layer.

8. The apparatus of claim 6, wherein the variable acquisition module comprises:

a third variable acquiring unit configured to acquire the target variable in the first routing address, the target variable being all characters after the first delimiter, in a case where the first delimiter is a delimiter other than a bracket and a second delimiter positioned after the first delimiter does not exist in the first routing address;

9. The apparatus of claim 6, further comprising:

10. The apparatus of claim 6, further comprising:

11. An electronic device, characterized in that the electronic device comprises:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the data request transmission method of any one of claims 1 to 5.

12. A storage medium having stored thereon computer program instructions which, when executed by a processor, implement a data request transmission method according to any one of claims 1 to 5.