CN110826004A - Front-end request data processing method and related device - Google Patents
Front-end request data processing method and related device Download PDFInfo
- Publication number
- CN110826004A CN110826004A CN201911071487.1A CN201911071487A CN110826004A CN 110826004 A CN110826004 A CN 110826004A CN 201911071487 A CN201911071487 A CN 201911071487A CN 110826004 A CN110826004 A CN 110826004A
- Authority
- CN
- China
- Prior art keywords
- request data
- interface
- field
- end interface
- interface definition
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- 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
Abstract
The application discloses a method for processing front-end request data, which comprises the following steps: constructing a front-end interface mapping list according to a rear-end interface definition field, a front-end interface definition field and unique identifiers corresponding to the rear-end interface definition field and the front-end interface definition field; performing interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data; and sending the target request data to back-end equipment so that the back-end equipment can send return data according to the target request data. The back-end interface definition field and the front-end interface definition field are adapted through the constructed front-end and back-end interface mapping list, so that the cost of matching the front end and the back end is reduced, and the cost of adaptation is avoided. The application also discloses a processing device of the front-end request data, computer equipment and a computer readable storage medium, which have the beneficial effects.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method, a device, a computer apparatus, and a computer-readable storage medium for processing front-end request data.
Background
With the continuous development of internet technology, different development modes of internet services appear. The development mode of separating the front end from the back end improves the mutual separation of the two technical stacks, improves the special precision degree of developers, reduces the development time to a certain extent and improves the development efficiency.
Generally, in the front-end and back-end separation technology, the front end is responsible for functions such as page display, and the back end is responsible for functions such as data storage and data processing. Data communication between the front-end and the back-end is typically performed by an interface provided by the back-end. That is, in the prior art, the front-end device and the back-end device determine the manner of implementation in the respective functions by fixed interface names. I.e. the front end and the back end are connected by a fixed interface name.
Therefore, after the front-end and back-end separation technique is adopted, if the interface mode is modified or changed, different interface definitions need to be modified in the front end so as to enable the front end to be adapted to the interface of the back end. It can be seen that, in the prior art, as long as the interface is modified, the information of the interface needs to be checked and modified one by one in the front end by manual means. The modification process is not only a manual operation process, which requires a large amount of labor cost and time cost, but also is prone to subjective errors in the modification process, resulting in more cost input.
Therefore, how to reduce the cost of front-end and back-end adaptation is a key issue to those skilled in the art.
Disclosure of Invention
The application aims to provide a front-end request data processing method, a front-end request data processing device, a computer device and a computer readable storage medium.
In order to solve the above technical problem, the present application provides a method for processing front-end request data, including:
constructing a front-end interface mapping list according to a rear-end interface definition field, a front-end interface definition field and unique identifiers corresponding to the rear-end interface definition field and the front-end interface definition field;
performing interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data;
and sending the target request data to back-end equipment so that the back-end equipment can send return data according to the target request data.
Optionally, performing interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data, including:
matching the front-end interface definition fields of the front-end request data according to the front-end and back-end interface mapping list to obtain corresponding back-end interface definition fields;
and assigning a value corresponding to the front-end interface definition field of the front-end request data to the corresponding rear-end interface definition field to obtain the target request data.
Optionally, performing interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data, including:
judging whether a request interception flag bit in the front-end request data is in an interception state;
if yes, performing interface field conversion processing on the front-end request data according to the front-end and back-end interface mapping list to obtain the target request data;
and if not, taking the front-end request data as the target request data.
Optionally, the method further includes:
and when the return data is received, performing interface field conversion processing on the return data according to the front-end and back-end interface mapping list to obtain target return data.
The present application further provides a device for processing front-end request data, including:
the mapping list construction module is used for constructing a front-end and back-end interface mapping list according to a rear-end interface definition field, a front-end interface definition field and unique identifiers corresponding to the rear-end interface definition field and the front-end interface definition field;
the request data conversion module is used for carrying out interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data;
and the request data sending module is used for sending the target request data to the back-end equipment so that the back-end equipment can send return data according to the target request data.
Optionally, the request data conversion module includes:
an interface field matching unit, configured to match a front-end interface definition field of the front-end request data according to the front-end and back-end interface mapping list, so as to obtain a corresponding back-end interface definition field;
and the attribute value conversion unit is used for assigning the value corresponding to the front-end interface definition field of the front-end request data to the corresponding rear-end interface definition field to obtain the target request data.
Optionally, the request data conversion module includes:
the request interception judging unit is used for judging whether a request interception flag bit in the front-end request data is in an interception state;
the interception processing unit is used for performing interface field conversion processing on the front-end request data according to the front-end and back-end interface mapping list to obtain the target request data when the request interception flag bit is in an interception state;
and the release processing unit is used for taking the front-end request data as the target request data when the request interception flag bit is not in an interception state.
Optionally, the method further includes:
and the return data processing module is used for carrying out interface field conversion processing on the return data according to the front-end and back-end interface mapping list when the return data is received to obtain target return data.
The present application further provides a computer device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the processing method as described above when executing the computer program.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the processing method as described above.
The application provides a method for processing front-end request data, which comprises the following steps: constructing a front-end interface mapping list according to a rear-end interface definition field, a front-end interface definition field and unique identifiers corresponding to the rear-end interface definition field and the front-end interface definition field; performing interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data; and sending the target request data to back-end equipment so that the back-end equipment can send return data according to the target request data.
The method comprises the steps of constructing a front-back interface mapping list by a rear-end interface definition field, a front-end interface definition field and a unique mark corresponding to the rear-end interface definition field and the front-end interface definition field, namely forming a corresponding relation between different rear-end interface definition fields and different front-end interface definition fields by the unique mark, namely the front-back interface mapping list, carrying out interface field conversion processing on front-end request data according to the front-back interface mapping list when the front-end request data is received to obtain target request data, converting the interface field in the target request data into an interface field matched with a rear end at the moment, transmitting the target request data to rear-end equipment, carrying out request processing on the target request data by the rear-end equipment, and finally transmitting return data to realize mutual adaptation among different interface fields, and the adaptation operation is realized without manual modification, so that the cost of the adaptation of the front and rear end interfaces is reduced, and the problem of the field non-adaptation of the front and rear end interfaces is avoided.
The present application further provides a processing apparatus, a computer device, and a computer-readable storage medium for front-end request data, which have the above beneficial effects, and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for processing front-end request data according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a front-end data request processing apparatus according to an embodiment of the present disclosure.
Detailed Description
The core of the application is to provide a processing method, a processing device, computer equipment and a computer readable storage medium for front-end request data, and the back-end interface definition field and the front-end interface definition field are adapted through a constructed front-end and back-end interface mapping list, so that the front-end and back-end matching cost is reduced, and the adaptation cost is avoided.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the front-end and back-end separation technology in the prior art, the front end is responsible for functions such as page display and the like, and the back end is responsible for functions such as data storage, data processing and the like. Data communication between the front-end and the back-end is typically performed by an interface provided by the back-end. That is, in the prior art, the front-end device and the back-end device determine the manner of implementation in the respective functions by fixed interface names. I.e. the front end and the back end are connected by a fixed interface name. Therefore, after the front-end and back-end separation technique is adopted, if the interface mode is modified or changed, different interface definitions need to be modified in the front end so as to enable the front end to be adapted to the interface of the back end. It can be seen that, in the prior art, as long as the interface is modified, the information of the interface needs to be checked and modified one by one in the front end by manual means. The modification process is not only a manual operation process, which requires a large amount of labor cost and time cost, but also is prone to subjective errors in the modification process, resulting in more cost input.
Therefore, the application provides a method for processing front-end request data, which constructs a front-end and back-end interface mapping list by a back-end interface definition field, a front-end interface definition field and a unique mark corresponding to the back-end interface definition field and the front-end interface definition field, namely, a corresponding relation can be formed between different back-end interface definition fields and front-end interface definition fields by the unique mark, namely, the front-end and back-end interface mapping list, when receiving front-end request data, interface field conversion processing is carried out on the front-end request data according to the front-end and back-end interface mapping list to obtain target request data, at the moment, the interface field in the target request data is converted into an interface field matched with the back end, the target request data can be sent to back-end equipment, and the back-end equipment realizes the request processing of the target request data, and finally, sending the returned data to realize mutual adaptation among different interface fields without manually modifying to realize adaptation operation, thereby reducing the cost of front-end and back-end interface adaptation and avoiding the problem of non-adaptation of the front-end and back-end interface fields.
Referring to fig. 1, fig. 1 is a flowchart illustrating a method for processing front-end request data according to an embodiment of the present disclosure.
In this embodiment, the method may include:
s101, constructing a front-end and back-end interface mapping list according to a rear-end interface definition field, a front-end interface definition field and unique identifiers corresponding to the rear-end interface definition field and the front-end interface definition field;
the step is intended to establish a corresponding relationship between the back-end interface definition field, the front-end interface definition field and the unique identifier corresponding to the back-end interface definition field and the front-end interface definition field, specifically, the corresponding relationship between the back-end interface definition field and the unique identifier, and the corresponding relationship between the front-end interface definition field and the unique identifier. I.e. each unique identifier corresponds to an interface definition field used in the back-end and also to an interface definition field used in the front-end.
It is conceivable that, after the correspondence relationship is determined, that is, the front-end and back-end interface mapping list is determined, a unique front-end interface definition field may be uniquely determined by any front-end interface definition field, and may also be determined by any back-end interface definition field. When the definition field of the back-end interface or the definition field of the front-end interface changes, only the definition field of the interface at one side needs to be modified and then the corresponding relation is established, and the definition field of the front-end interface and the definition field of the back-end interface do not need to be modified simultaneously.
Specifically, when the above correspondence is presented as a front-end and back-end interface mapping list, the corresponding fields in the mapping list may be directly modified.
In terms of distance, the unique identifier representing the user name information exists in the mapping list of the front-end interface and the back-end interface and is 'UserInfo', the field defined by the back-end interface is 'name', and the field defined by the front-end interface is 'userName'.
S102, performing interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping lists to obtain target request data;
on the basis of S101, this step aims to perform interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list acquired in the previous step, so as to obtain target request data. That is, the corresponding backend interface definition field is searched in the front-end and backend interface mapping list according to the interface definition field in the front-end request data, and then the front-end interface definition field in the front-end request data is replaced by the corresponding backend interface definition field to obtain the final target request data.
In addition, in this step, the interface field in the front-end request data may also be converted in other manners, which is not described herein.
Optionally, the step may include:
matching front-end interface definition fields of front-end request data according to a front-end and back-end interface mapping list to obtain corresponding back-end interface definition fields;
and step two, assigning the value corresponding to the front-end interface definition field of the front-end request data to the corresponding rear-end interface definition field to obtain the target request data.
It can be seen that, this alternative scheme is mainly to match out the corresponding backend interface definition field first, and then assign the value in the corresponding frontend interface definition field to the backend interface definition field that is matched out. That is, the interface definition field in the original front-end request data is replaced with the backend interface definition field.
In addition, in this step, it can also be determined whether the front-end request data needs to be intercepted, and then the corresponding operation is performed. Thus, it may include: judging whether a request interception flag bit in front-end request data is in an interception state; if so, performing interface field conversion processing on the front-end request data according to the front-end and back-end interface mapping lists to obtain target request data; and if not, taking the front-end request data as target request data.
S103, the target request data is sent to the back-end equipment, so that the back-end equipment sends return data according to the target request data.
On the basis of S102, this step is intended to transmit the converted target request data to the backend apparatus, so that the backend apparatus transmits return data according to the target request data. That is, the back-end device receives the target request data, processes the target request data to obtain the return data, and sends the return data back to the front-end device.
In addition, the present embodiment may further include:
and when receiving the return data, performing interface field conversion processing on the return data according to the front-end and back-end interface mapping list to obtain target return data.
That is, the return data returned by the back-end device is converted according to the corresponding relation recorded in the mapping list of the front-end and back-end interfaces, so as to obtain the target return data adapted to the front end. For a specific conversion process, reference may be made to step S102, which is not described herein again.
To sum up, in this embodiment, a backend interface definition field, a frontend interface definition field, and a unique identifier corresponding to the backend interface definition field and the frontend interface definition field are first used to construct a backend-interface mapping list, that is, a corresponding relationship between different backend-interface definition fields and different frontend interface definition fields can be formed by the unique identifier, that is, the backend-interface mapping list, when receiving frontend request data, interface field conversion processing is performed on the frontend request data according to the backend-interface mapping list to obtain target request data, at this time, an interface field in the target request data has been converted into an interface field matched with the backend, and then the target request data can be sent to a backend device, and the backend device implements request processing on the target request data and finally sends back data to implement mutual adaptation between different interface fields, and the adaptation operation is realized without manual modification, so that the cost of the adaptation of the front and rear end interfaces is reduced, and the problem of the field non-adaptation of the front and rear end interfaces is avoided.
The following further describes a method for processing front-end request data provided by the present application by using a specific embodiment.
In this embodiment, all the interfaces required by each project are agreed in an online or offline manner, and a unique identification key capable of expressing the approximate function of each interface is defined for each interface.
And then establishing a project middle layer, wherein the middle layer needs to realize the input of the support interface information, the interface list is imported into the middle layer after the agreement of the interface list is completed, and the search can be carried out according to the unique identifier key of the interface.
On the basis of the middle layer, the front-end and back-end developers can add, modify and define required fields of a certain interface according to the requirements of the front-end and back-end developers, and the fields can be the same or different if the other end is added and the other end can add the required fields on the basis. For example, the unique identifier key is "UserInfo" to indicate user name information, the interface field of the user name is added at the back end and named as "name", the front end is named as "userName", and the correspondence between the "UserInfo" and the "name" or "userName" is only required to be formed.
Because some request parameters and acquisition parameters are in simple formats and do not need to be intercepted, the parameters of the front-end request need to be expanded, and two optional additional parameters (whether a request interceptor flag bit is enabled and whether a return value interceptor flag bit is enabled) are added for judging whether to execute the intercepting operation.
Before a request is initiated, if the flag bit of the request interceptor is enabled to be true, the middle layer needs to be firstly accessed to obtain a front-end and back-end interface mapping list of the interface, the structure is of an Object type, wherein the key value is a field defined by the back end, and the value is defined by the front end, so that the efficiency of traversing all fields can be improved. After the mapping relation object requestMapObject is obtained, an object queryObject which is the same as the requestMapObject is newly established as a request parameter sent to the back end, the queryObject is circularly traversed to find the value of each attribute of the queryObject from the parameter sent from the front end according to the value of each attribute of the queryObject, the value is assigned to the value of the named attribute of the queryObject, finally the queryObject is really converted into a parameter needed by the back end, and the parameter is attached to the request and sent to the back end.
After the request is successful, if the flag bit of the request starting return value interceptor is true, the obtained parameters returned by the server cannot be used directly, a front-end and back-end interface mapping list needs to be obtained in the middle layer, the structure is of an Object type, and the obtained parameters are different from those obtained during the request, and are sent to the front end for use, so that the key value is a field defined by the front end, the value is a field defined by the back end, after the mapping relation Object responseMapObject is obtained, an Object responseObject which is the same as the responseMapObject is newly created as data used by the front end, the responseObject is circularly traversed to find the value of each attribute of the responseObject from the value of the attribute in the back end, and the value is set to the value of the attribute which is changed by the name of the responseObject, so that the responseObject is changed into the real value of the attribute which is changed, and the data is rendered as the front end page which is assigned.
It can be seen that, in this embodiment, a front-end interface mapping list is first constructed by a rear-end interface definition field, a front-end interface definition field, and a unique identifier corresponding to the rear-end interface definition field and the front-end interface definition field, that is, a corresponding relationship between different rear-end interface definition fields and different front-end interface definition fields, that is, the front-end and rear-end interface mapping list, when receiving front-end request data, interface field conversion processing is performed on the front-end request data according to the front-end and rear-end interface mapping list to obtain target request data, at this time, an interface field in the target request data has been converted into an interface field matched with the rear end, and then the target request data can be sent to the rear-end device, the rear-end device implements request processing on the target request data, and finally sends back data to implement mutual adaptation between different interface fields, and the adaptation operation is realized without manual modification, so that the cost of the adaptation of the front and rear end interfaces is reduced, and the problem of the field non-adaptation of the front and rear end interfaces is avoided.
The following describes a processing apparatus for front-end request data provided in an embodiment of the present application, and a processing apparatus for front-end request data described below and a processing method for front-end request data described above are referred to correspondingly.
Referring to fig. 2, fig. 2 is a schematic structural diagram of a front-end data request processing device according to an embodiment of the present disclosure.
In this embodiment, the apparatus may include:
the mapping list construction module 100 is configured to construct a front-back interface mapping list according to the back-end interface definition field, the front-end interface definition field, and the unique identifier corresponding to the back-end interface definition field and the front-end interface definition field;
the request data conversion module 200 is configured to perform interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping lists to obtain target request data;
the request data sending module 300 is configured to send the target request data to the backend device, so that the backend device sends the return data according to the target request data.
Optionally, the request data conversion module 200 may include:
the interface field matching unit is used for matching the front-end interface definition field of the front-end request data according to the front-end and back-end interface mapping list to obtain the corresponding back-end interface definition field;
and the attribute value conversion unit is used for assigning the value corresponding to the front-end interface definition field of the front-end request data to the corresponding rear-end interface definition field to obtain the target request data.
Optionally, the request data conversion module 200 may include:
the request interception judging unit is used for judging whether a request interception flag bit in the front-end request data is in an interception state;
the interception processing unit is used for carrying out interface field conversion processing on the front-end request data according to the front-end and back-end interface mapping list to obtain target request data when the request interception flag bit is in an interception state;
and the release processing unit is used for taking the front-end request data as the target request data when the request interception flag bit is not in an interception state.
Optionally, the apparatus may include:
and the return data processing module is used for carrying out interface field conversion processing on the return data according to the front-end and back-end interface mapping list when the return data are received to obtain target return data.
An embodiment of the present application further provides a computer device, including:
a memory for storing a computer program;
a processor for implementing the steps of the processing method as described in the above embodiments when executing the computer program.
The present application further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the steps of the processing method according to the above embodiments.
The computer-readable storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The foregoing detailed description describes a method, an apparatus, a computer device, and a computer-readable storage medium for processing front-end request data provided in the present application. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. A method for processing front-end request data is characterized by comprising the following steps:
constructing a front-end interface mapping list according to a rear-end interface definition field, a front-end interface definition field and unique identifiers corresponding to the rear-end interface definition field and the front-end interface definition field;
performing interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data;
and sending the target request data to back-end equipment so that the back-end equipment can send return data according to the target request data.
2. The processing method according to claim 1, wherein performing interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data, comprises:
matching the front-end interface definition fields of the front-end request data according to the front-end and back-end interface mapping list to obtain corresponding back-end interface definition fields;
and assigning a value corresponding to the front-end interface definition field of the front-end request data to the corresponding rear-end interface definition field to obtain the target request data.
3. The processing method according to claim 1, wherein performing interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data, comprises:
judging whether a request interception flag bit in the front-end request data is in an interception state;
if yes, performing interface field conversion processing on the front-end request data according to the front-end and back-end interface mapping list to obtain the target request data;
and if not, taking the front-end request data as the target request data.
4. The processing method of claim 1, further comprising:
and when the return data is received, performing interface field conversion processing on the return data according to the front-end and back-end interface mapping list to obtain target return data.
5. A device for processing front-end request data, comprising:
the mapping list construction module is used for constructing a front-end and back-end interface mapping list according to a rear-end interface definition field, a front-end interface definition field and unique identifiers corresponding to the rear-end interface definition field and the front-end interface definition field;
the request data conversion module is used for carrying out interface field conversion processing on the received front-end request data according to the front-end and back-end interface mapping list to obtain target request data;
and the request data sending module is used for sending the target request data to the back-end equipment so that the back-end equipment can send return data according to the target request data.
6. The processing apparatus as claimed in claim 5, wherein the request data conversion module comprises:
an interface field matching unit, configured to match a front-end interface definition field of the front-end request data according to the front-end and back-end interface mapping list, so as to obtain a corresponding back-end interface definition field;
and the attribute value conversion unit is used for assigning the value corresponding to the front-end interface definition field of the front-end request data to the corresponding rear-end interface definition field to obtain the target request data.
7. The processing apparatus as claimed in claim 5, wherein the request data conversion module comprises:
the request interception judging unit is used for judging whether a request interception flag bit in the front-end request data is in an interception state;
the interception processing unit is used for performing interface field conversion processing on the front-end request data according to the front-end and back-end interface mapping list to obtain the target request data when the request interception flag bit is in an interception state;
and the release processing unit is used for taking the front-end request data as the target request data when the request interception flag bit is not in an interception state.
8. The processing apparatus as in claim 5, further comprising:
and the return data processing module is used for carrying out interface field conversion processing on the return data according to the front-end and back-end interface mapping list when the return data is received to obtain target return data.
9. A computer device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the processing method of any one of claims 1 to 4 when executing the computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the processing method of one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911071487.1A CN110826004A (en) | 2019-11-05 | 2019-11-05 | Front-end request data processing method and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911071487.1A CN110826004A (en) | 2019-11-05 | 2019-11-05 | Front-end request data processing method and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110826004A true CN110826004A (en) | 2020-02-21 |
Family
ID=69552489
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911071487.1A Pending CN110826004A (en) | 2019-11-05 | 2019-11-05 | Front-end request data processing method and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110826004A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111427568A (en) * | 2020-03-30 | 2020-07-17 | 山东浪潮通软信息科技有限公司 | Interface configuration method and device |
| CN111596902A (en) * | 2020-05-26 | 2020-08-28 | 牛津(海南)区块链研究院有限公司 | Method, device, equipment and storage medium for building front-end and back-end development framework |
| CN113434228A (en) * | 2021-06-21 | 2021-09-24 | 青岛海尔科技有限公司 | Page request method and device, storage medium and electronic device |
| WO2021218063A1 (en) * | 2020-04-27 | 2021-11-04 | 平安科技（深圳）有限公司 | Method and apparatus for assigning parameter with value on the basis of name mapping, and computer device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102082992A (en) * | 2009-11-30 | 2011-06-01 | 中国移动通信集团山西有限公司 | Mobile office system and implementation method thereof |
| CN105373626A (en) * | 2015-12-09 | 2016-03-02 | 深圳融合永道科技有限公司 | Distributed face recognition track search system and method |
| CN108572823A (en) * | 2018-04-23 | 2018-09-25 | 武汉斗鱼网络科技有限公司 | Front and back end development management method and system based on interface engine |
| CN108920140A (en) * | 2018-07-19 | 2018-11-30 | 河北中科恒运软件科技股份有限公司 | Method of calibration is unified in a kind of front and back end |
| CN110348239A (en) * | 2019-06-13 | 2019-10-18 | 平安普惠企业管理有限公司 | Desensitize regular configuration method and data desensitization method, system, computer equipment |
-
2019
- 2019-11-05 CN CN201911071487.1A patent/CN110826004A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102082992A (en) * | 2009-11-30 | 2011-06-01 | 中国移动通信集团山西有限公司 | Mobile office system and implementation method thereof |
| CN105373626A (en) * | 2015-12-09 | 2016-03-02 | 深圳融合永道科技有限公司 | Distributed face recognition track search system and method |
| CN108572823A (en) * | 2018-04-23 | 2018-09-25 | 武汉斗鱼网络科技有限公司 | Front and back end development management method and system based on interface engine |
| CN108920140A (en) * | 2018-07-19 | 2018-11-30 | 河北中科恒运软件科技股份有限公司 | Method of calibration is unified in a kind of front and back end |
| CN110348239A (en) * | 2019-06-13 | 2019-10-18 | 平安普惠企业管理有限公司 | Desensitize regular configuration method and data desensitization method, system, computer equipment |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111427568A (en) * | 2020-03-30 | 2020-07-17 | 山东浪潮通软信息科技有限公司 | Interface configuration method and device |
| WO2021218063A1 (en) * | 2020-04-27 | 2021-11-04 | 平安科技（深圳）有限公司 | Method and apparatus for assigning parameter with value on the basis of name mapping, and computer device |
| CN111596902A (en) * | 2020-05-26 | 2020-08-28 | 牛津(海南)区块链研究院有限公司 | Method, device, equipment and storage medium for building front-end and back-end development framework |
| CN111596902B (en) * | 2020-05-26 | 2023-03-28 | 牛津(海南)区块链研究院有限公司 | Method, device, equipment and storage medium for building front-end and back-end development framework |
| CN113434228A (en) * | 2021-06-21 | 2021-09-24 | 青岛海尔科技有限公司 | Page request method and device, storage medium and electronic device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110826004A (en) | Front-end request data processing method and related device | |
| CN108462758B (en) | Bank-enterprise direct connection communication method, device, equipment and computer readable storage medium | |
| CN106657149B (en) | Communication protocol conversion method and device | |
| CN106850789B (en) | System and method for dynamically allocating game players based on server load detection | |
| CN103038788A (en) | Provisioning multiple network resources | |
| CN112671950B (en) | Domain name processing method and device based on block chain, electronic equipment and storage medium | |
| CN110569036A (en) | data verification system and method under front-end and back-end separation architecture | |
| CN113067866B (en) | Batch file transmission method and device between heterogeneous systems | |
| KR20230153448A (en) | Federated learning methods, devices, electronic devices and storage media | |
| CN111190970A (en) | Data mapping method, device and computer readable storage medium | |
| JP5550385B2 (en) | Image processing apparatus, control method therefor, and storage medium | |
| CN108959278B (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN110175833B (en) | Computer device, method, system and medium for binding bank card information | |
| CN106412000B (en) | A kind of processing method of inquiry of the domain name | |
| CN111628956B (en) | Format conversion method, device and system for network request transmission data | |
| CN111835824B (en) | Binding method, migration method, binding device, migration device, computing equipment and storage medium | |
| CN108197090B (en) | Method and system for processing default value in file format conversion process | |
| CN113806104A (en) | Interface access request processing method, API gateway, server and system | |
| CN112242909B (en) | Method and device for generating management template, electronic equipment and storage medium | |
| CN111400266B (en) | Data processing method and system, and diagnosis processing method and device for operation event | |
| CN108776665B (en) | Data processing method and device | |
| CN108255955B (en) | Data processing method and device | |
| CN108491283A (en) | A kind of data transmission method, device, computer and storage medium | |
| CN111489212A (en) | Order billing method, device, equipment and medium based on big data | |
| CN115150388B (en) | File uploading and file uploading state query method and equipment and storage medium thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200221 |
|
| RJ01 | Rejection of invention patent application after publication |