CN112528274A - Data processing method and device, electronic equipment and storage medium - Google Patents
Data processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112528274A CN112528274A CN202011547506.6A CN202011547506A CN112528274A CN 112528274 A CN112528274 A CN 112528274A CN 202011547506 A CN202011547506 A CN 202011547506A CN 112528274 A CN112528274 A CN 112528274A
- Authority
- CN
- China
- Prior art keywords
- target
- request
- page
- data acquisition
- acquisition request
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
- G06F21/54—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by adding security routines or objects to programs
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a data processing method, a data processing device, electronic equipment and a storage medium, wherein the method comprises the following steps: determining a request identifier in a received page data acquisition request, and determining a target white list matched with the request identifier; when the request identification is not included in the target white list, the page data acquisition request is sent to a target server, so that the target server feeds back target data matched with the page data acquisition request; the target server is a server corresponding to each locally deployed target subsystem; and rendering the received target data to obtain a target page, and feeding the target page back to the target terminal equipment. According to the technical scheme of the embodiment of the invention, when the shared data changes, the shared data does not need to be repeatedly backed up to other locally deployed target servers, and the technical effects of universality of data management and convenience of data calling are improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a data processing method and device, electronic equipment and a storage medium.
Background
At present, in order to improve the security of data, data is usually stored locally, for example, in the medical field, users in each area may use services such as online registration, inquiry and the like, and in order to ensure the security and the convenience of calling of data of each user, data may be deployed locally, that is, a server corresponding to each area is established, and basic data of users in the area may be stored in the corresponding server.
When a client corresponding to a corresponding area initiates a page data acquisition request, a schematic diagram of data processing by a system based on localized deployment may be as shown in fig. 1, and if the client corresponding to the local service a initiates a page data acquisition request, the local server a may process the data acquisition request. That is, each area is a set of system, there is no reusability, and each time the localization of one area is added, the whole system needs to be copied once for deployment.
Further, in the actual application process, if there is a change in data common to each area, the corresponding program code in each server needs to be updated, that is, if the server deploys N local areas, N locally deployed codes need to be synchronized, which may cause the technical problems of complicated deployment and inconvenient storage and maintenance.
Disclosure of Invention
The invention provides a data processing method, a data processing device, electronic equipment and a storage medium, and aims to achieve the technical effect of quickly and conveniently acquiring target data corresponding to a page data acquisition request.
In a first aspect, an embodiment of the present invention provides a data processing method, where the method includes:
determining a request identifier in a received page data acquisition request, and determining a target white list matched with the request identifier;
when the request identification is not included in the target white list, the page data acquisition request is sent to a target server, so that the target server feeds back target data matched with the page data acquisition request; the target server is a main server corresponding to each locally deployed target subsystem;
and rendering the received target data to obtain a target page, and feeding the target page back to the target terminal equipment.
In a second aspect, an embodiment of the present invention further provides a data processing apparatus, where the apparatus includes:
the target white list determining module is used for determining a request identifier in the received page data acquisition request and determining a target white list matched with the request identifier;
a data obtaining request sending module, configured to send the page data obtaining request to a target server when the request identifier is not included in the target white list, so that the target server feeds back target data matched with the page data obtaining request; the target server is a server corresponding to each locally deployed target subsystem;
and the data feedback module is used for rendering the received target data to obtain a target page and feeding the target page back to the target terminal equipment.
In a third aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement the data processing method according to any one of the embodiments of the present invention.
In a fourth aspect, the embodiments of the present invention further provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are used for executing the data processing method according to any one of the embodiments of the present invention.
According to the technical scheme, whether data are acquired from a locally deployed server or from a main server is determined by predetermining data requests received by interfaces of the same server, and determining the corresponding interface white list, so that when a page data acquisition request is received, whether the interface of the page data acquisition request is in the white list can be determined, the corresponding server can feed back target data corresponding to the page data acquisition request, the target data can be rendered after the front-end service receives the target data, a target page is obtained, when the shared data changes, the shared data does not need to be repeatedly backed up to other locally deployed target servers, and the technical effects of improving the universality of data management and convenience in data calling are achieved.
Drawings
In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, a brief description is given below of the drawings used in describing the embodiments. It should be clear that the described figures are only views of some of the embodiments of the invention to be described, not all, and that for a person skilled in the art, other figures can be derived from these figures without inventive effort.
FIG. 1 is a flow chart of a data processing method in the prior art;
fig. 2 is a schematic flow chart of a data processing method according to an embodiment of the present invention;
fig. 3 is a schematic flow chart of a data processing method according to a second embodiment of the present invention;
fig. 4 is a schematic structural diagram of a data processing apparatus according to a third embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 2 is a schematic flow chart of a data processing method according to an embodiment of the present invention, where this embodiment is applicable to determining whether an interface corresponding to a page data acquisition request is in a white list when the page data acquisition request is received, and further determining that a server corresponding to the page data acquisition request feeds back corresponding target data.
Before the technical solution of the present embodiment is introduced, a system deployment for implementing the technical solution of the present embodiment may be exemplarily described. Corresponding servers, i.e., target subsystems, may be deployed in the respective regions according to the region division result. For example, the areas such as shandong and henna can be provided with servers for storing medical data or user data, namely, the system data is arranged in the servers of local services. The deployment mode has the advantages that the data in the local area can be stored in the corresponding server, and the technical effect of improving the data storage safety is achieved. Accordingly, in order to avoid the problem that deployment and updating are complicated and complicated because the common data of each system needs to be updated to the servers deployed in each area when the common data of each system changes, the common data can be stored in the main server corresponding to each locally deployed server. The method has the advantages that for common data, such as a certain medical main page, if a certain main page or common page data is updated, only the page code in the main server can be changed, and the problems of resource waste and high labor cost caused by repeatedly deploying the code of the updated page to other servers are avoided.
Further, after the server localization deployment of each region is completed. For the servers corresponding to the regions, which interfaces need to request the server for localized deployment and which interfaces need to request the main server may be determined, and a corresponding interface white list may be generated based on the type configuration of the interfaces, so that when a page data acquisition request is received, whether the interface corresponding to the request is on the interface white list may be determined, and then the corresponding server may execute the corresponding operation.
As shown in fig. 2, the method of this embodiment includes:
s110, determining a request identifier in the received page data acquisition request, and determining a target white list matched with the request identifier.
It should be noted that, if the user performs online inquiry, the corresponding inquiry page may be triggered, or the inquiry page in the application program may be triggered, and when the operation of triggering acquisition of the inquiry page is detected, the data acquisition request for acquiring the inquiry page may be generated.
The page data acquisition request is generated according to an operation of acquiring a certain page triggered by a user on a display interface. The page data obtaining request may carry a request identifier, where the request identifier may be a domain name corresponding to the request, or an interface corresponding to the request, or may determine that the page data obtaining request is sent based on a client corresponding to which region. The white list matched with the page data acquisition request is used as a target white list, for example, if the page data acquisition request is sent based on a client corresponding to the locally deployed service a, the white list a 'corresponding to the service a may be called, and the white list a' is used as the target white list. That is, the target white list is a white list matched according to the page data acquisition request.
It should be noted that, when determining that the page data acquisition request is sent based on which client corresponding to the local deployment service, the determination may be made according to the request domain name in the request identifier.
Specifically, if the mobile terminal or the PC is equipped with a corresponding application, the user may enter the home page of the application after triggering the application. The user can trigger any one control on the main page, and if a certain control corresponds to the acquisition page, a page data acquisition request can be generated. According to the request entry of the page data acquisition request, a request domain corresponding to the request and a corresponding localization deployment server can be determined so as to determine a target subsystem for processing the page data acquisition request, namely, whether the target subsystem needs to be executed by a locally deployed server or a main server corresponding to the local server. If the main server is needed to execute the page data acquisition, a target subsystem corresponding to the page data acquisition request can be determined, and a target white list corresponding to the target subsystem is determined.
In this embodiment, the determining the request identifier in the received page data acquisition request and the determining the target white list matched with the request identifier includes: determining a request identifier carried in the page data acquisition request and a request domain name in the request identifier; determining a target white list matched with the request domain name from a pre-established white list set; the white list set comprises interface white lists corresponding to the target subsystems.
The white list set is pre-established, and comprises white lists corresponding to the target subsystems. And each target subsystem, namely the localized deployed server, is divided into interface white lists according to whether the data acquisition request corresponding to the interface needs to be determined from the localized deployed server or the main server. The interfaces of the data corresponding to the corresponding data acquisition requests can be determined by the servers needing localized deployment, and the interfaces can be stored in an interface white list. The determination of the white lists corresponding to the target subsystems can be determined in this way, and details are not repeated here.
Specifically, a request identifier carried in the page data acquisition request may be extracted, a request domain name in the request identifier may be acquired, and after the domain name is determined, a target subsystem corresponding to the request identifier may be determined, and then a target white list matched with the target subsystem may be determined from a pre-established white list set, so as to determine whether an interface corresponding to the data acquisition request is included in the target white list.
S120, when the request identification is not included in the target white list, the page data acquisition request is sent to a target server, so that the target server feeds back target data matched with the page data acquisition request; the target server is a main server corresponding to each locally deployed target subsystem.
Each target subsystem has a corresponding white list, and the specific content in the white list is determined according to whether the data called by the interface is acquired from the target subsystem or the main server corresponding to each target subsystem. For example, the interface for obtaining data from the target subsystem may be placed in a white list, and the interface for obtaining data from the main server may not be placed in the white list. The white list is set, so that the data which does not need to be locally deployed can be uniformly stored in the main server, and when the data in the main server changes, the data do not need to be updated in each subsystem, and the effect of saving resources is achieved.
Specifically, when it is detected that the target white list includes an interface corresponding to the request identifier, it may be determined that the page data corresponding to the request identifier needs to be acquired from the host server, and at this time, the page data acquisition request may be sent to a target host server, that is, a target server, so that the target server may process the page data acquisition request to obtain target data matched with the page data acquisition request.
It should be noted that, determining whether the page data acquisition request is in the white list may be determined based on a front-end service. Optionally, all the target subsystems and the target servers share one front-end server, when receiving a page data acquisition request initiated by each client, the front-end server may send the page data acquisition request to the front-end service based on a reverse proxy mechanism, and after receiving the page data acquisition request, the front-end service may determine, according to at least one stored white list, a white list corresponding to the page data acquisition request, that is, determine a target white list corresponding to a target subsystem matched with the page data acquisition request, and further determine whether an interface of the page data acquisition request is in the white list.
Optionally, before determining the request identifier in the received page data obtaining request and determining the target white list matched with the request identifier, the method further includes: when detecting that a page data acquisition request is initiated, determining a target front-end service for processing the page data acquisition request based on a reverse proxy mechanism, so that the target front-end service extracts a request identifier in the page data acquisition request.
And the target front-end service is the front-end service corresponding to the target subsystem and the target server. The target front-end service can extract a request identifier carried in the page data acquisition request according to the page data acquisition request, so as to determine whether an interface corresponding to the request identifier is in a white list or not based on the request identifier.
Specifically, when it is detected that the client initiates the page data acquisition request, a front-end service for processing the page data acquisition request may be determined based on a reverse proxy mechanism, and after the front-end service receives the page data acquisition request, a request identifier carried in the page data acquisition request, that is, a request domain name may be extracted, where the reason for determining the request domain name is: one may determine the target subsystem to which the request corresponds and the other may determine whether the interface is in the white list.
In this embodiment, it may also be that a corresponding front-end service is created for each target subsystem. If each target subsystem has the front-end service, the front-end service can process the corresponding page data acquisition request, and at this time, the white list of the target subsystem can be stored in the front-end service corresponding to the white list. If the page data acquisition request is received, whether the interface corresponding to the request is in the white list or not can be determined, and the page data acquisition request can be sent to the target subsystem corresponding to the page data acquisition request without a reverse proxy mechanism.
Optionally, before determining the request identifier in the received page data obtaining request and determining the target white list matched with the request identifier, the method further includes: when a page data acquisition request is detected, according to the domain name of the page data acquisition request, the page data acquisition request is sent to a target front-end service corresponding to the domain name.
For example, if the target subsystem is the subsystem a, the subsystem B … subsystem N, the front-end service a, the front-end service B … front-end service N corresponding to the target subsystem may be created. After detecting the trigger page data acquisition request, it may determine a front-end service corresponding to the request, optionally, the front-end service a, and send the page data acquisition request to the front-end service a. After receiving the page data acquisition request, the front-end service a may determine whether to process the page data acquisition request for the target subsystem a according to a white list in the front-end service, optionally, if the white list includes an interface corresponding to the page data acquisition request, it indicates that the page data acquisition request needs to be processed from a locally deployed service at this time, otherwise, it indicates that the page data acquisition request is public data, and the page data acquisition request may be sent to the main server, so that the main server processes the page data acquisition request to obtain the target data.
S130, rendering the received target data to obtain a target page, and feeding the target page back to the target terminal equipment.
Specifically, when the target server feeds back the target data corresponding to the page data acquisition request, the target data may be rendered to obtain the target page. After the page rendering is completed, the target page may be fed back to the target terminal device.
In this embodiment, the rendering the received target data to obtain a target page, and feeding back the target page to the target terminal device includes: rendering the received target data based on the target front-end service to obtain a target page; and feeding back the target page to the target terminal equipment corresponding to the page data acquisition request.
Specifically, after receiving the target data fed back by the target server or the target subsystem, the front-end service may perform rendering processing on the target data to obtain a target page. After the target page is obtained, the target page may be fed back to the target terminal device corresponding to the page data obtaining request.
On the basis of the technical scheme, the method further comprises the following steps: when the target white list comprises an interface corresponding to the request identifier, determining a target subsystem corresponding to the request identifier; and sending the page data acquisition request to the target subsystem so that the sub-server of the target subsystem processes the page data acquisition request and feeds back corresponding target data.
Specifically, if the white list includes an interface corresponding to the request identifier, it indicates that the page data acquisition request can be fed back to the locally deployed target subsystem corresponding to the page data acquisition request. After the target subsystem receives the page data acquisition request, the target subsystem can process the page data acquisition request to obtain target data, and the target data is rendered and fed back to the client.
According to the technical scheme of the embodiment of the invention, after the page data acquisition request is received, the request identifier in the request can be determined, the target white list matched with the request identifier is determined, and when the target white list does not comprise an interface corresponding to the request identifier, the page data acquisition request can be sent to the target server, so that the target server feeds back corresponding data, the data is rendered to obtain the target page, and the target page is fed back to the target terminal.
Example two
As an alternative embodiment of the foregoing embodiment, fig. 3 is a schematic diagram of a data processing method according to a second embodiment of the present invention. The same or corresponding terms as those in the above embodiments are not described herein again.
As shown in fig. 3, the method includes: the service can be locally deployed according to regions, and the locally deployed service can be a local service A, a local service B and a local service C …. Data needing to be stored locally can be stored in the local service, and data common to all services can be stored in a target server, namely a server corresponding to each local service. If a user in the Shandong area initiates a page data acquisition request, the page data acquisition request can be sent to the front-end service based on a reverse proxy mechanism, and after receiving the page data acquisition request, the front-end service can determine an interface of the page data acquisition request and a corresponding localized service, for example, the localized service corresponding to the Shandong area is localized service B. At this time, the front-end service may call a target white list B 'corresponding to the local service B, may determine whether the target white list B' includes an interface corresponding to the page data acquisition request, and if so, may send the page data acquisition request to the localized service B, so that the localized service B feeds back corresponding target data; if the target white list B' does not include an interface corresponding to the page data obtaining request, the page data obtaining request may be sent to the target server, because the data common to the localization services may be stored in the target server, so that the target server processes the page data obtaining request to obtain corresponding target data. After the target data is determined, the target data can be fed back to the front-end service, so that the front-end service performs rendering processing on the target data to obtain a target page corresponding to the page data acquisition request, and the target page is fed back to the terminal device.
For example, in the first step, the interface service is deployed to the service corresponding to the corresponding localization area, that is, the target subsystem, and the interface white list corresponding to each localization service may be stored in the front-end service. And secondly, when a page data acquisition request initiated by a user is received, forwarding the page data acquisition request to a front-end service corresponding to the target server based on a reverse proxy, wherein an interface configuration white list is stored in the front-end service, a target white list corresponding to the interface configuration white list can be searched, and whether the interface is in the target white list or not is determined. Thirdly, the interface request in the interface white list can correspond to the interface of the localization service, for example, the page data acquisition request comes from the service A and can request the localization interface of the service A; if interfaces which are not in the white list are shared by all locally deployed services, each service can process the data acquisition request and return corresponding data. And fourthly, after the front-end service receives the data corresponding to the page data acquisition request, rendering the page data, and feeding back a rendering result to the client.
According to the technical scheme of the embodiment of the invention, after the page data acquisition request is received, the request identifier in the request can be determined, the target white list matched with the request identifier is determined, and when the target white list does not comprise an interface corresponding to the request identifier, the page data acquisition request can be sent to the target server, so that the target server feeds back corresponding data, the data is rendered to obtain the target page, and the target page is fed back to the target terminal.
EXAMPLE III
Fig. 4 is a schematic structural diagram of a data processing apparatus according to a third embodiment of the present invention, as shown in fig. 4, the apparatus includes: a target white list determination module 310, a data acquisition request sending module 320, and a data feedback module 330.
The target white list determining module 310 is configured to determine a request identifier in a received page data obtaining request, and determine a target white list matched with the request identifier; a data obtaining request sending module 320, configured to send the page data obtaining request to a target server when the request identifier is not included in the target white list, so that the target server feeds back target data matched with the page data obtaining request; the target server is a server corresponding to each locally deployed target subsystem; the data feedback module 330 is configured to perform rendering processing on the received target data to obtain a target page, and feed the target page back to the target terminal device.
According to the technical scheme of the embodiment of the invention, after the page data acquisition request is received, the request identifier in the request can be determined, the target white list matched with the request identifier is determined, and when the target white list does not comprise an interface corresponding to the request identifier, the page data acquisition request can be sent to the target server, so that the target server feeds back corresponding data, the data is rendered to obtain the target page, and the target page is fed back to the target terminal.
On the basis of the above technical solution, the white list determining module, before being configured to determine a request identifier in a received page data obtaining request and determine a target white list matched with the request identifier, is further configured to: when detecting that a page data acquisition request is initiated, determining a target front-end service for processing the page data acquisition request based on a reverse proxy mechanism, so that the target front-end service extracts a request identifier in the page data acquisition request.
On the basis of the above technical solution, the white list determining module, before being configured to determine a request identifier in a received page data obtaining request and determine a target white list matched with the request identifier, is further configured to: when a page data acquisition request is detected, according to the domain name of the page data acquisition request, the page data acquisition request is sent to a target front-end service corresponding to the domain name.
On the basis of the above technical solution, the white list determining module includes:
a request identifier determining unit, configured to determine a request identifier carried in the page data obtaining request and a request domain name in the request identifier; a white list determining module, configured to determine a target white list matched with the request domain name from a pre-established white list set; the white list set comprises interface white lists corresponding to the target subsystems.
On the basis of the above technical solutions, the apparatus further includes:
a target subsystem determining module, configured to determine a target subsystem corresponding to the request identifier when the target white list includes an interface corresponding to the request identifier; and the target data determining module is used for sending the page data acquisition request to the target subsystem so as to enable the sub-server of the target subsystem to process the page data acquisition request and feed back corresponding target data.
On the basis of the above technical solutions, the apparatus further includes:
the judging module is used for determining whether the data acquisition request corresponding to each interface of the current target subsystem acquires data from the locally deployed target subsystem or not aiming at each target subsystem; if yes, generating a white list corresponding to the current target subsystem based on each interface processed by the current target subsystem; the target subsystem is a system deployed to the local.
On the basis of the above technical solutions, the data feedback module includes: the target page generating unit is used for rendering the received target data based on the target front-end service to obtain a target page; and the target data feedback unit is used for feeding the target page back to the target terminal equipment corresponding to the page data acquisition request.
The data processing device provided by the embodiment of the invention can execute the data processing method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
It should be noted that, the units and modules included in the apparatus are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the embodiment of the invention.
Example four
Fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. FIG. 5 illustrates a block diagram of an exemplary electronic device 40 suitable for use in implementing embodiments of the present invention. The electronic device 40 shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 5, electronic device 40 is embodied in the form of a general purpose computing device. The components of electronic device 40 may include, but are not limited to: one or more processors or processing units 401, a system memory 402, and a bus 403 that couples the various system components (including the system memory 402 and the processing unit 401).
The system memory 402 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)404 and/or cache memory 405. The electronic device 40 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 406 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 5, commonly referred to as a "hard drive"). Although not shown in FIG. 5, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 403 by one or more data media interfaces. Memory 402 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 408 having a set (at least one) of program modules 407 may be stored, for example, in memory 402, such program modules 407 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 407 generally perform the functions and/or methods of the described embodiments of the invention.
The electronic device 40 may also communicate with one or more external devices 409 (e.g., keyboard, pointing device, display 410, etc.), with one or more devices that enable a user to interact with the electronic device 40, and/or with any devices (e.g., network card, modem, etc.) that enable the electronic device 40 to communicate with one or more other computing devices. Such communication may be through input/output (I/O) interface 411. Also, the electronic device 40 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 412. As shown, the network adapter 412 communicates with the other modules of the electronic device 40 over the bus 403. It should be appreciated that although not shown in FIG. 5, other hardware and/or software modules may be used in conjunction with electronic device 40, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processing unit 401 executes various functional applications and data processing, for example, implementing a data processing method provided by an embodiment of the present invention, by executing a program stored in the system memory 402.
EXAMPLE five
Fifth, an embodiment of the present invention further provides a storage medium containing computer-executable instructions, which are used to perform a data processing method when executed by a computer processor.
The method comprises the following steps:
determining a request identifier in a received page data acquisition request, and determining a target white list matched with the request identifier;
when the request identification is not included in the target white list, the page data acquisition request is sent to a target server, so that the target server feeds back target data matched with the page data acquisition request; the target server is a main server corresponding to each locally deployed target subsystem;
and rendering the received target data to obtain a target page, and feeding the target page back to the target terminal equipment.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for embodiments of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A data processing method, comprising:
determining a request identifier in a received page data acquisition request, and determining a target white list matched with the request identifier;
when the request identification is not included in the target white list, the page data acquisition request is sent to a target server, so that the target server feeds back target data matched with the page data acquisition request; the target server is a main server corresponding to each locally deployed target subsystem;
and rendering the received target data to obtain a target page, and feeding the target page back to the target terminal equipment.
2. The method of claim 1, prior to determining a request identifier in the received page data acquisition request and determining a target white list matching the request identifier, further comprising:
when detecting that a page data acquisition request is initiated, determining a target front-end service for processing the page data acquisition request based on a reverse proxy mechanism, so that the target front-end service extracts a request identifier in the page data acquisition request.
3. The method of claim 1, prior to determining a request identifier in the received page data acquisition request and determining a target white list matching the request identifier, further comprising:
when a page data acquisition request is detected, according to the domain name of the page data acquisition request, the page data acquisition request is sent to a target front-end service corresponding to the domain name.
4. The method according to claim 2 or 3, wherein the request identifier includes a request domain name, the determining a request identifier in the received page data acquisition request, and determining a target white list matching the request identifier include:
determining a request identifier carried in the page data acquisition request and a request domain name in the request identifier;
determining a target white list matched with the request domain name from a pre-established white list set; the white list set comprises interface white lists corresponding to the target subsystems.
5. The method of claim 1, further comprising:
when the target white list comprises an interface corresponding to the request identifier, determining a target subsystem corresponding to the request identifier;
and sending the page data acquisition request to the target subsystem so that the sub-server of the target subsystem processes the page data acquisition request and feeds back corresponding target data.
6. The method of claim 4, further comprising:
determining whether a data acquisition request corresponding to each interface of the current target subsystem acquires data from a locally deployed target subsystem or not aiming at each target subsystem;
if yes, generating a white list corresponding to the current target subsystem based on each interface processed by the current target subsystem; the target subsystem is a system deployed to the local.
7. The method of claim 1, wherein the rendering the received target data to obtain a target page, and feeding the target page back to the target terminal device comprises:
rendering the received target data based on the target front-end service to obtain a target page;
and feeding back the target page to the target terminal equipment corresponding to the page data acquisition request.
8. A data processing apparatus, comprising:
the target white list determining module is used for determining a request identifier in the received page data acquisition request and determining a target white list matched with the request identifier;
a data obtaining request sending module, configured to send the page data obtaining request to a target server when the request identifier is not included in the target white list, so that the target server feeds back target data matched with the page data obtaining request; the target server is a server corresponding to each locally deployed target subsystem;
and the data feedback module is used for rendering the received target data to obtain a target page and feeding the target page back to the target terminal equipment.
9. An electronic device, characterized in that the electronic device comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a data processing method as claimed in any one of claims 1-7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the data processing method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011547506.6A CN112528274B (en) | 2020-12-24 | 2020-12-24 | Data processing method, device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011547506.6A CN112528274B (en) | 2020-12-24 | 2020-12-24 | Data processing method, device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112528274A true CN112528274A (en) | 2021-03-19 |
| CN112528274B CN112528274B (en) | 2023-09-22 |
Family
ID=74976067
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011547506.6A Active CN112528274B (en) | 2020-12-24 | 2020-12-24 | Data processing method, device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112528274B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112988391A (en) * | 2021-03-30 | 2021-06-18 | 北京字跳网络技术有限公司 | Data processing method, device, equipment and storage medium |
| CN113436056A (en) * | 2021-07-21 | 2021-09-24 | 挂号网（杭州）科技有限公司 | Rendering method, rendering device, electronic equipment and storage medium |
| WO2022262481A1 (en) * | 2021-06-18 | 2022-12-22 | 中国第一汽车股份有限公司 | Calibration data management system, method, apparatus and device for electronic control unit |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130346374A1 (en) * | 2012-06-26 | 2013-12-26 | International Business Machines Corporation | Restoring objects in a client-server environment |
| CN108881396A (en) * | 2018-05-24 | 2018-11-23 | 平安普惠企业管理有限公司 | Loading method, device, equipment and the computer storage medium of network data |
| CN109815430A (en) * | 2018-11-30 | 2019-05-28 | 北京金山云网络技术有限公司 | Request processing method, device, data processing server and readable storage medium storing program for executing |
| CN109902248A (en) * | 2019-02-25 | 2019-06-18 | 百度在线网络技术（北京）有限公司 | Page display method, device, computer equipment and readable storage medium storing program for executing |
| US20190379675A1 (en) * | 2018-06-07 | 2019-12-12 | Sap Se | Web application session security |
| CN110647700A (en) * | 2019-08-13 | 2020-01-03 | 平安普惠企业管理有限公司 | Page resource loading method and device, computer equipment and storage medium |
| CN110795650A (en) * | 2019-09-18 | 2020-02-14 | 平安银行股份有限公司 | Webpage opening method and device and computer readable storage medium |
| US20200169560A1 (en) * | 2018-11-27 | 2020-05-28 | Dell Products L.P. | Systems And Methods To Secure Publicly-Hosted Cloud Applications To Run Only Within The Context Of A Trusted Client Application |
| CN111324843A (en) * | 2020-02-17 | 2020-06-23 | 政采云有限公司 | Front-end request processing method, device, equipment and readable storage medium |
| CN111552897A (en) * | 2019-02-08 | 2020-08-18 | 甲骨文国际公司 | Client-side customization and rendering of web content |
| CN111708594A (en) * | 2020-06-09 | 2020-09-25 | 北京达佳互联信息技术有限公司 | Page rendering method and device, electronic equipment and storage medium |
| CN111708600A (en) * | 2020-08-20 | 2020-09-25 | 腾讯科技（深圳）有限公司 | Page display method, device, equipment and computer readable storage medium |
| CN111800426A (en) * | 2020-07-07 | 2020-10-20 | 腾讯科技（深圳）有限公司 | Method, device, equipment and medium for accessing native code interface in application program |
-
2020
- 2020-12-24 CN CN202011547506.6A patent/CN112528274B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130346374A1 (en) * | 2012-06-26 | 2013-12-26 | International Business Machines Corporation | Restoring objects in a client-server environment |
| CN108881396A (en) * | 2018-05-24 | 2018-11-23 | 平安普惠企业管理有限公司 | Loading method, device, equipment and the computer storage medium of network data |
| US20190379675A1 (en) * | 2018-06-07 | 2019-12-12 | Sap Se | Web application session security |
| US20200169560A1 (en) * | 2018-11-27 | 2020-05-28 | Dell Products L.P. | Systems And Methods To Secure Publicly-Hosted Cloud Applications To Run Only Within The Context Of A Trusted Client Application |
| CN109815430A (en) * | 2018-11-30 | 2019-05-28 | 北京金山云网络技术有限公司 | Request processing method, device, data processing server and readable storage medium storing program for executing |
| CN111552897A (en) * | 2019-02-08 | 2020-08-18 | 甲骨文国际公司 | Client-side customization and rendering of web content |
| CN109902248A (en) * | 2019-02-25 | 2019-06-18 | 百度在线网络技术（北京）有限公司 | Page display method, device, computer equipment and readable storage medium storing program for executing |
| CN110647700A (en) * | 2019-08-13 | 2020-01-03 | 平安普惠企业管理有限公司 | Page resource loading method and device, computer equipment and storage medium |
| CN110795650A (en) * | 2019-09-18 | 2020-02-14 | 平安银行股份有限公司 | Webpage opening method and device and computer readable storage medium |
| CN111324843A (en) * | 2020-02-17 | 2020-06-23 | 政采云有限公司 | Front-end request processing method, device, equipment and readable storage medium |
| CN111708594A (en) * | 2020-06-09 | 2020-09-25 | 北京达佳互联信息技术有限公司 | Page rendering method and device, electronic equipment and storage medium |
| CN111800426A (en) * | 2020-07-07 | 2020-10-20 | 腾讯科技（深圳）有限公司 | Method, device, equipment and medium for accessing native code interface in application program |
| CN111708600A (en) * | 2020-08-20 | 2020-09-25 | 腾讯科技（深圳）有限公司 | Page display method, device, equipment and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 叶小艳 等: "一种改进的MVC框架在ERP***开发中的应用", 计算机技术与发展, no. 09 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112988391A (en) * | 2021-03-30 | 2021-06-18 | 北京字跳网络技术有限公司 | Data processing method, device, equipment and storage medium |
| WO2022262481A1 (en) * | 2021-06-18 | 2022-12-22 | 中国第一汽车股份有限公司 | Calibration data management system, method, apparatus and device for electronic control unit |
| CN113436056A (en) * | 2021-07-21 | 2021-09-24 | 挂号网（杭州）科技有限公司 | Rendering method, rendering device, electronic equipment and storage medium |
| CN113436056B (en) * | 2021-07-21 | 2023-02-17 | 挂号网（杭州）科技有限公司 | Rendering method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112528274B (en) | 2023-09-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112528274B (en) | Data processing method, device, electronic equipment and storage medium | |
| US20040059735A1 (en) | Systems and methods for enabling failover in a distributed-object computing environment | |
| CN109558199B (en) | Information pushing method, device, equipment and storage medium | |
| CN110602270A (en) | Domain name resolution method and device, computer equipment and storage medium | |
| CN113050900B (en) | Screen sharing method, device, equipment and storage medium | |
| CN111737022A (en) | Interface calling method, system, equipment and medium based on micro-service | |
| CN110958127B (en) | Exception handling method, device and equipment and computer storage medium | |
| CN113992382B (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN111818145B (en) | File transmission method, device, system, equipment and storage medium | |
| CN113761412A (en) | Application page display method and device, electronic equipment, medium and application system | |
| CN108540552B (en) | Device interconnection method, apparatus, system, device and storage medium | |
| CN113467895B (en) | Docker operation method, docker operation device, server and storage medium | |
| CN107862035B (en) | Network reading method and device for conference record, intelligent tablet and storage medium | |
| CN114584618A (en) | Information interaction method, device, equipment, storage medium and system | |
| CN109413507B (en) | Method, device, terminal and medium for processing reference relationship between barrage library and live broadcast room | |
| CN109683942B (en) | Script management method, script management device, script management medium and electronic equipment | |
| CN111245944A (en) | Domain name resolution method and device, electronic equipment and storage medium | |
| CN115599669A (en) | Debugging method and device of microservice, electronic equipment and readable storage medium | |
| CN113986995A (en) | Request distribution method and device, storage medium and electronic equipment | |
| CN114238391A (en) | Data paging query method and device, electronic equipment and storage medium | |
| CN104407846B (en) | Information processing method and device | |
| CN113919310A (en) | Short message content determination method and device, electronic equipment and storage medium | |
| CN113761419A (en) | Display method and device of topological information, electronic equipment and storage medium | |
| CN109348303B (en) | Bullet screen message distribution method, bullet screen message distribution device, terminal and storage medium | |
| CN112364268A (en) | Resource acquisition method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |