CN111435380A - Page cross-domain interaction method, system, device and storage device - Google Patents
Page cross-domain interaction method, system, device and storage device Download PDFInfo
- Publication number
- CN111435380A CN111435380A CN201910032143.3A CN201910032143A CN111435380A CN 111435380 A CN111435380 A CN 111435380A CN 201910032143 A CN201910032143 A CN 201910032143A CN 111435380 A CN111435380 A CN 111435380A
- Authority
- CN
- China
- Prior art keywords
- data
- domain page
- processed
- server
- identifier
- 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
- 238000000034 method Methods 0.000 title claims abstract description 37
- 230000003993 interaction Effects 0.000 title claims description 21
- 238000004590 computer program Methods 0.000 claims description 12
- 230000001960 triggered effect Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The method comprises the steps that a second domain page receives an access request of the second domain page sent by a user on a first domain page, the access request comprises a uniform resource locator UR L of the second domain page, the UR L carries an identifier of data to be processed in the first domain page, the access request is analyzed to obtain an identifier of the data to be processed, the identifier of the data to be processed is sent to a server of the second domain page, so that the server of the second domain page can obtain the data to be processed from the server of the first domain page according to the identifier of the data to be processed, the data to be processed sent by the server of the second domain page is received and displayed.
Description
Technical Field
The present disclosure relates generally to the field of computer technologies, and in particular, to a method, a system, a device, and a storage device for page cross-domain interaction.
Background
In the background management system, the user operation is facilitated, the working efficiency is improved, the cost of switching between different systems is reduced, and other system pages can be embedded for use. When the association operation is performed between the embedded page and the main page, a data transmission problem is inevitably involved, and a GET request method of a hypertext transfer Protocol (HTTP) is generally adopted, however, in consideration of security and size limitation of data transmission, a POST request method of the HTTP has to be selected. However, cross-domain problems arise because a front-end page of another system is requested across systems.
Therefore, how to solve the cross-domain problem and realize data transmission between different system pages is an urgent problem to be solved.
Disclosure of Invention
In view of the above-mentioned deficiencies or inadequacies in the prior art, it would be desirable to provide a solution that enables data transfer between cross-domain pages.
In a first aspect, an embodiment of the present application provides a page cross-domain interaction method, including:
a second domain page receives an access request of the second domain page sent by a user in a first domain page, wherein the access request comprises a uniform resource locator UR L of the second domain page, and the UR L carries an identifier of data to be processed in the first domain page;
analyzing the access request to obtain the identifier of the data to be processed;
sending the identifier of the data to be processed to a server of the second domain page, so that the server of the second domain page can acquire the data to be processed from the server of the first domain page according to the identifier of the data to be processed;
and receiving and displaying the data to be processed sent by the server of the second domain page.
In a second aspect, an embodiment of the present application further provides a page cross-domain interaction system, including: a first domain page, a server of the first domain page, a second domain page, and a server of the second domain page, wherein:
the second domain page is used for receiving an access request of the second domain page sent by a user in the first domain page, wherein the access request comprises UR L of the second domain page, and UR L carries an identifier of data to be processed in the first domain page;
and the server of the second domain page is used for acquiring the data to be processed from the server of the first domain page according to the identifier of the data to be processed.
In a third aspect, an embodiment of the present application further provides an apparatus, including: at least one processor, at least one memory, and computer program instructions stored in the memory that, when executed by the processor, implement a page cross-domain interaction method as described above.
In a fourth aspect, the present application further provides a computer-readable storage medium, on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the page cross-domain interaction method described above is implemented.
According to the page cross-domain interaction scheme provided by the embodiment of the application, the access request is sent to the second domain page through the first domain page, the access request comprises UR L of the second domain page carrying the identification of the data to be processed in the first domain page, the second domain page analyzes the access request, the identification of the data to be processed is obtained and then sent to the server of the second domain page, the server of the second domain page can obtain the data to be processed from the server of the first domain page according to the identification of the data to be processed and feed the data to the second domain page, and the second domain page displays the received data to be processed.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
FIG. 1 is a flowchart illustrating an exemplary method for page cross-domain interaction according to an embodiment of the present disclosure;
FIG. 2 is a flowchart illustrating an exemplary method for page cross-domain interaction according to an embodiment of the present disclosure;
FIG. 3 is a block diagram illustrating an exemplary structure of a page cross-domain interaction system provided by an embodiment of the present application; and
FIG. 4 illustrates a schematic block diagram of a computer system suitable for use in implementing embodiments of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
As mentioned in the background art, in the background management system, in order to facilitate user operations, improve work efficiency, reduce the cost of switching between different systems for a user, other system pages may be embedded for use. When the association operation is performed between the embedded page and the main page, the problem of data transmission is inevitably involved. However, cross-domain problems arise because a front-end page of another system is requested across systems.
In view of the foregoing defects in the prior art, an embodiment of the present application provides a page cross-domain interaction scheme, where an access request is sent to a second domain page through a first domain page, where the access request includes UR L of the second domain page that carries an identifier of data to be processed in the first domain page, and the second domain page parses the access request, obtains the identifier of the data to be processed, and sends the identifier to a server of the second domain page, so that the server of the second domain page can obtain the data to be processed from the server of the first domain page according to the identifier of the data to be processed and feed the data back to the second domain page, and the second domain page displays the received data to be processed.
The page cross-domain method provided by the embodiment of the application can be embedded into mobile terminals such as WeChat public numbers, WeChat applets, Paibao living numbers, APP and the like and multiple terminals such as a computer browser HTM L5 and the like for use.
The method of the embodiments of the present application will be described below with reference to a flowchart.
Referring to fig. 1, an exemplary flowchart of a page cross-domain interaction method provided by an embodiment of the present application is shown.
The method comprises the following steps:
In the embodiment of the application, when a user operates service data on a first domain page, due to a service reason, the service data needs to be synchronously processed on a second domain page, at this time, the user may call the second domain page on the first domain page, and send an access request to the second domain page, where the access request needs to carry UR L of the second domain page and also carries an identifier of data to be processed, where the data to be processed refers to the service data of the second domain page that needs to be synchronously processed.
And step 120, the second domain page analyzes the access request to obtain the identifier of the data to be processed.
Specifically, after receiving the access request, the second domain page parses the identifier of the to-be-processed data carried by the second domain page from the UR L in the access request.
Specifically, the second domain page sends the identifier of the data to be processed to a server of the second domain page;
after receiving the identifier of the data to be processed, the server of the second domain page can send the identifier of the data to be processed to the server of the first domain page in a POST request mode;
and the server of the first domain page searches the data to be processed corresponding to the identifier of the data to be processed from the database of the server according to the identifier of the data to be processed, and sends the searched data to be processed to the server of the second domain page.
And step 140, receiving and displaying the data to be processed sent by the server of the second domain page.
Optionally, when the first domain page sends an access request to the second domain page, the UR L included in the access request may also carry a first domain page identifier, where the first domain page identifier is used to characterize a data source.
Thus, after the second domain page parses the parameters (including the identifier of the data to be processed and the identifier of the first domain page) in the UR L from the access request and sends the parameters to the server of the second domain page, the server of the second domain page may determine the data source according to the identifier of the first domain page, and then send the identifier of the data to be processed to the determined data source, that is, the server of the first domain page, to obtain the data to be processed.
Optionally, the UR L included in the access request may also carry an identifier of all data in the first domain page and a current data index.
Thus, when the second domain page parses out the parameters (including the identifier of the to-be-processed data, the identifiers of all the data in the first domain page and the current data index) in the UR L from the access request and the second domain page receives an operation request of the previous or next piece of data to be processed triggered by a user, the identifier of the new to-be-processed data is determined according to the identifiers of all the data in the first domain page and the current data index, and the identifier of the new to-be-processed data is sent to the server of the second domain page, so that the server of the second domain page obtains the new to-be-processed data from the server of the first domain page according to the identifier of the new to-be-processed data.
According to the page cross-domain interaction scheme provided by the embodiment of the application, the access request is sent to the second domain page through the first domain page, the access request comprises UR L of the second domain page carrying the identification of the data to be processed in the first domain page, the second domain page analyzes the access request, the identification of the data to be processed is obtained and then sent to the server of the second domain page, the server of the second domain page can obtain the data to be processed from the server of the first domain page according to the identification of the data to be processed and feed the data to the second domain page, and the second domain page displays the received data to be processed.
The page cross-domain interaction method provided by the embodiment of the present application will be described in detail below with reference to a flowchart, and as shown in fig. 2, the page cross-domain interaction method provided by the embodiment of the present application is a flowchart. The method is applied to a scene that the system A and the system B are nested with each other. The method comprises the following steps:
step 210, the user clicks the front page of system a and sends an access request to the front page of system B.
The access request may be sent by a GET request, and the following parameters are carried in UR L of the front-end page of the system B for sending:
1. all data identification of the front page of System A (id1, id2
2. Current data index (indexNUm: id) of front-end page of system A
3. Identification of data to be processed of front-end page of System A (selectedId: id)
4. Data source identification (sourceFrom)
Assembling the above parameters, the obtained UR L may be, for example:
"http://127.0.0.1:8000/static/B.html？cdmData＝{"indexNUm":0,"selectedId":"37","dataList":[{"id":"37"},{"id":"43045"}],"sourceFrom":"listPage"}"
step 220, the front-end page of the system B parses the received access request to obtain all data identifiers, the current data index, the identifier of the data to be processed, and the data source identifier of the front-end page of the system a, which are carried in the access request, and sends the identifier of the data to be processed to the back-end server of the system B.
Step 230, the back-end server of system B sends the identifier of the data to be processed to the back-end server of system a by way of POST request.
And 240, the back-end server of the system A returns the data to be processed to the back-end server of the system B according to the identification of the data to be processed.
Specifically, the back-end server of the system a searches the to-be-processed data corresponding to the identifier of the to-be-processed data from its own database according to the identifier of the to-be-processed data, and sends the searched to-be-processed data to the back-end server of the system B.
And step 250, the back-end server of the system B returns the received data to be processed to the front-end page of the system B, and the front-end page of the system B renders and loads the data to be processed to complete the user association operation.
By adopting the page cross-domain interaction scheme provided by the embodiment of the application, the following technical effects can be realized:
1. the method and the system have the advantages that seamless butt joint can be achieved among the multiple system pages, system diversity is improved, user experience is enhanced, and cost of back-and-forth switching among multiple systems is reduced.
2. Batch data transmission under the scene of mutual nesting of cross-system pages is realized.
3. The cost increased by the repeated development of the page is reduced.
It should be noted that while the operations of the method of the present invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Rather, the steps depicted in the flowcharts may change the order of execution. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
With further reference to fig. 3, it shows an exemplary structural block diagram of a page cross-domain interaction system provided by the embodiment of the present application.
The system comprises a first domain page 31, a server for the first domain page 32, a second domain page 33 and a server for the second domain page 34, wherein:
the second domain page 33 is configured to receive an access request of the second domain page 33 sent by a user from the first domain page 31, where the access request includes the UR L of the second domain page 33, and the UR L carries an identifier of data to be processed in the first domain page 31;
the server 34 of the second domain page is configured to obtain the to-be-processed data from the server 32 of the first domain page according to the identifier of the to-be-processed data.
Optionally, the server 34 of the second domain page is specifically configured to:
sending the identifier of the data to be processed to the server 32 of the first domain page; receiving the data to be processed sent by the server 32 of the first domain page;
the server 32 of the first domain page is configured to:
and searching the data to be processed corresponding to the identifier of the data to be processed from the database of the server according to the identifier of the data to be processed, and sending the searched data to be processed to the server 34 of the second domain page.
The UR L also carries the first domain page mark
The second domain page 33 is also used for:
analyzing the access request to obtain the first domain page identifier, and sending the first domain page identifier to the server 34 of the second domain page;
the server 34 of the second domain page is specifically configured to:
and sending the identifier of the data to be processed to the server 32 of the first domain page corresponding to the first domain page identifier according to the first domain page identifier.
Optionally, the UR L also carries the identifiers of all data in the first domain page and the current data index, and then
The second domain page 33 is also used for:
analyzing the access request to obtain the identifiers of all data in the first domain page 31 and the current data index; when receiving an operation request for the previous or next data of the to-be-processed data triggered by a user, determining an identifier of new to-be-processed data according to the identifiers of all data in the first domain page 31 and the current data index, and sending the identifier of the new to-be-processed data to the server 34 of the second domain page;
the server 34 of the second domain page is further configured to:
and acquiring the new data to be processed from the server 32 of the first domain page according to the identifier of the new data to be processed.
It should be understood that the subsystems or units described in the system correspond to the various steps in the method described with reference to fig. 1 and 2. Thus, the operations and features described above for the method are equally applicable to the system and the units comprised therein and will not be described in further detail here.
Referring now to FIG. 4, a block diagram of a computer system 400 suitable for use in implementing a server according to embodiments of the present application is shown.
As shown in fig. 4, the computer system includes a Central Processing Unit (CPU)401 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)402 or a program loaded from a storage section into a Random Access Memory (RAM) 403. In the RAM403, various programs and data necessary for system operation are also stored. The CPU 401, ROM 402, and RAM403 are connected to each other via a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.
To the I/O interface 405, AN input section 406 including a keyboard, a mouse, and the like, AN output section including AN input section such as a Cathode Ray Tube (CRT), a liquid crystal display (L CD), and the like, a speaker, and the like, a storage section 408 including a hard disk, and the like, and a communication section 409 including a network interface card such as a L AN card, a modem, and the like, the communication section 409 performs communication processing via a network such as the internet, a drive is also connected to the I/O interface 405 as necessary, a removable medium 411 such as a magnetic disk, AN optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 410 as necessary, so that a computer program read out therefrom is mounted into the storage section 408 as necessary.
In particular, the processes described above with reference to flowcharts 1-2 may be implemented as computer software programs, according to embodiments of the present invention. For example, embodiments of the invention include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication section, and/or installed from a removable medium. The above-described functions defined in the system of the present application are executed when the computer program is executed by a Central Processing Unit (CPU) 401.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. 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 of the computer readable storage medium may include, but are not limited to: 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 present invention, 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. In the present invention, however, 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, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present invention may be implemented by software, or may be implemented by hardware, and the described units may also be disposed in a processor. Wherein the names of the elements do not in some way constitute a limitation on the elements themselves. The described units or modules may also be provided in a processor.
As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device is enabled to implement the page cross-domain interaction method in the embodiment.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware.
Claims (10)
1. A page cross-domain interaction method is characterized by comprising the following steps:
a second domain page receives an access request of the second domain page sent by a user in a first domain page, wherein the access request comprises a uniform resource locator UR L of the second domain page, and the UR L carries an identifier of data to be processed in the first domain page;
analyzing the access request to obtain the identifier of the data to be processed;
sending the identifier of the data to be processed to a server of the second domain page, so that the server of the second domain page can acquire the data to be processed from the server of the first domain page according to the identifier of the data to be processed;
and receiving and displaying the data to be processed sent by the server of the second domain page.
2. The method according to claim 1, wherein sending the identifier of the to-be-processed data to the server of the second domain page, so that the server of the second domain page obtains the to-be-processed data from the server of the first domain page according to the identifier of the to-be-processed data, comprises:
the second domain page sends the identifier of the data to be processed to a server of the second domain page;
the server of the second domain page sends the identifier of the data to be processed to the server of the first domain page;
and the server of the first domain page searches the data to be processed corresponding to the identifier of the data to be processed from the database of the server according to the identifier of the data to be processed, and sends the searched data to be processed to the server of the second domain page.
3. The method of claim 2 wherein the UR L further carries a first domain page identifier
The method further comprises the following steps:
the second domain page analyzes the access request to obtain the first domain page identifier and sends the first domain page identifier to a server of the second domain page; and
the step of sending the identifier of the data to be processed to the server of the first domain page by the server of the second domain page comprises the following steps:
and the server of the second domain page sends the identifier of the data to be processed to the server of the first domain page corresponding to the identifier of the first domain page according to the identifier of the first domain page.
4. The method of claim 1, wherein the UR L also carries therein an identification of all data in the first domain page and a current data index;
the method further comprises the following steps:
the second domain page analyzes the access request to obtain the identification of all data in the first domain page and the current data index;
when the second domain page receives an operation request for the previous or next data of the to-be-processed data triggered by a user, determining an identifier of new to-be-processed data according to the identifiers of all data in the first domain page and the current data index, and sending the identifier of the new to-be-processed data to the server of the second domain page, so that the server of the second domain page can obtain the new to-be-processed data from the server of the first domain page according to the identifier of the new to-be-processed data.
5. A page cross-domain interaction system is characterized in that the system comprises a first domain page, a server of the first domain page, a second domain page and a server of the second domain page, wherein:
the second domain page is used for receiving an access request of the second domain page sent by a user in the first domain page, wherein the access request comprises UR L of the second domain page, and UR L carries an identifier of data to be processed in the first domain page;
and the server of the second domain page is used for acquiring the data to be processed from the server of the first domain page according to the identifier of the data to be processed.
6. The system of claim 5, wherein the server of the second domain page is specifically configured to:
sending the identifier of the data to be processed to a server of the first domain page; receiving the data to be processed sent by the server of the first domain page;
the server of the first domain page is configured to:
and searching the data to be processed corresponding to the identifier of the data to be processed from the database of the server according to the identifier of the data to be processed, and sending the searched data to be processed to the server of the second domain page.
7. The system of claim 5, wherein the UR L further carries a first domain page identifier
The second domain page is further to:
analyzing the access request to obtain the first domain page identifier, and sending the first domain page identifier to a server of the second domain page;
the server of the second domain page is specifically configured to:
and sending the identifier of the data to be processed to a server of a first domain page corresponding to the first domain page identifier according to the first domain page identifier.
8. The system of claim 5, wherein the UR L also carries the identification of all data in the first domain page and the current data index, then
The second domain page is further to:
analyzing the access request to obtain the identifications of all data in the first domain page and the current data index; when receiving an operation request for the previous or next data of the to-be-processed data triggered by a user, determining an identifier of new to-be-processed data according to the identifiers of all data in the first domain page and the current data index, and sending the identifier of the new to-be-processed data to a server of the second domain page;
the server of the second domain page is further configured to:
and acquiring the new data to be processed from the server of the first domain page according to the identifier of the new data to be processed.
9. An apparatus, comprising: at least one processor, at least one memory, and computer program instructions stored in the memory that, when executed by the processor, implement the method of any of claims 1-4.
10. A computer-readable storage medium having computer program instructions stored thereon, which when executed by a processor implement the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910032143.3A CN111435380B (en) | 2019-01-14 | 2019-01-14 | Page cross-domain interaction method, system, device and storage device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910032143.3A CN111435380B (en) | 2019-01-14 | 2019-01-14 | Page cross-domain interaction method, system, device and storage device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111435380A true CN111435380A (en) | 2020-07-21 |
| CN111435380B CN111435380B (en) | 2024-04-16 |
Family
ID=71580461
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910032143.3A Active CN111435380B (en) | 2019-01-14 | 2019-01-14 | Page cross-domain interaction method, system, device and storage device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111435380B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112818270A (en) * | 2021-01-25 | 2021-05-18 | 上海哔哩哔哩科技有限公司 | Data cross-domain transfer method and device and computer equipment |
| CN113010610A (en) * | 2021-04-15 | 2021-06-22 | 上海绚显科技有限公司 | Data synchronization method and device |
| CN113377420A (en) * | 2021-06-08 | 2021-09-10 | 中国工商银行股份有限公司 | Data interfacing method, device, equipment and storage medium between systems |
| CN115622999A (en) * | 2022-09-28 | 2023-01-17 | 江苏谷科软件有限公司 | Safe front-end cross-domain request data interaction method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859170A (en) * | 2005-12-02 | 2006-11-08 | 华为技术有限公司 | Method for realizing cross-domain route separation |
| US20170149934A1 (en) * | 2015-11-24 | 2017-05-25 | Le Holdings (Beijing) Co., Ltd. | Method, device and system for data cross-domain request |
| CN107580013A (en) * | 2017-07-25 | 2018-01-12 | 阿里巴巴集团控股有限公司 | The method and device of cross-domain request data |
| CN108964975A (en) * | 2018-05-30 | 2018-12-07 | 北京五八信息技术有限公司 | Cross-domain access processing method and device |
-
2019
- 2019-01-14 CN CN201910032143.3A patent/CN111435380B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859170A (en) * | 2005-12-02 | 2006-11-08 | 华为技术有限公司 | Method for realizing cross-domain route separation |
| US20170149934A1 (en) * | 2015-11-24 | 2017-05-25 | Le Holdings (Beijing) Co., Ltd. | Method, device and system for data cross-domain request |
| CN107580013A (en) * | 2017-07-25 | 2018-01-12 | 阿里巴巴集团控股有限公司 | The method and device of cross-domain request data |
| CN108964975A (en) * | 2018-05-30 | 2018-12-07 | 北京五八信息技术有限公司 | Cross-domain access processing method and device |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112818270A (en) * | 2021-01-25 | 2021-05-18 | 上海哔哩哔哩科技有限公司 | Data cross-domain transfer method and device and computer equipment |
| CN112818270B (en) * | 2021-01-25 | 2023-07-25 | 上海哔哩哔哩科技有限公司 | Data cross-domain transfer method and device and computer equipment |
| CN113010610A (en) * | 2021-04-15 | 2021-06-22 | 上海绚显科技有限公司 | Data synchronization method and device |
| CN113377420A (en) * | 2021-06-08 | 2021-09-10 | 中国工商银行股份有限公司 | Data interfacing method, device, equipment and storage medium between systems |
| CN115622999A (en) * | 2022-09-28 | 2023-01-17 | 江苏谷科软件有限公司 | Safe front-end cross-domain request data interaction method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111435380B (en) | 2024-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111435380A (en) | Page cross-domain interaction method, system, device and storage device | |
| CN110708346B (en) | Information processing system and method | |
| CN110377440B (en) | Information processing method and device | |
| CN108810047B (en) | Method and device for determining information push accuracy rate and server | |
| CN109218041B (en) | Request processing method and device for server system | |
| CN113014681A (en) | Network card binding method and device of multi-network card server, electronic equipment and storage medium | |
| CN113050942A (en) | Page generation method and device, readable medium and electronic equipment | |
| CN111125503B (en) | Method and apparatus for generating information | |
| CN109981546B (en) | Method and device for acquiring remote call relation between application modules | |
| CN109471713B (en) | Method and device for inquiring information | |
| CN112558933A (en) | Component rendering method and device, readable medium and electronic equipment | |
| CN109144864B (en) | Method and device for testing window | |
| CN111953666A (en) | Data transmitting and receiving method and device and data transmitting and receiving system | |
| CN111756953A (en) | Video processing method, device, equipment and computer readable medium | |
| CN113742426B (en) | Data synchronization method, device, equipment, server and storage medium | |
| CN112948138A (en) | Method and device for processing message | |
| CN113590985B (en) | Page jump configuration method and device, electronic equipment and computer readable medium | |
| CN113283991B (en) | Processing method and device for transaction data on blockchain | |
| CN110858240A (en) | Front-end module loading method and device | |
| CN111338928A (en) | Chrome-based browser testing method and device | |
| CN113590986B (en) | Page link configuration method and device, electronic equipment and computer readable medium | |
| CN111367500A (en) | Data processing method and device | |
| CN115022266A (en) | Group member adding method, device, equipment and medium | |
| CN112783754B (en) | Method and device for testing page | |
| CN113568907A (en) | Method, device, server and storage medium for processing station information message |
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 |