CN107688570B - Webpage information processing method and system - Google Patents
Webpage information processing method and system Download PDFInfo
- Publication number
- CN107688570B CN107688570B CN201610629808.5A CN201610629808A CN107688570B CN 107688570 B CN107688570 B CN 107688570B CN 201610629808 A CN201610629808 A CN 201610629808A CN 107688570 B CN107688570 B CN 107688570B
- Authority
- CN
- China
- Prior art keywords
- page
- service
- information
- application page
- inline
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Abstract
The embodiment of the invention discloses a method and a system for processing webpage information, wherein the method comprises the following steps: the method comprises the steps that a webpage application page detects a trigger event aiming at a target service, an inline page aiming at the target service is established according to the trigger event, and a message event monitoring task is established, wherein the inline page is a front-end page of a login server of the webpage application page; the inline page acquires user account information of the webpage application page from the login server, and sends service request information to a service server corresponding to a target service according to the acquired user account information of the webpage application page; the inline page receives service callback information returned by the service server according to the service request, and transmits the service callback information to the webpage application page; and the webpage application page receives the service callback information through the message event monitoring task. The invention can realize the initiation of external business processing through the webpage application page.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a webpage information processing method and a webpage information processing system.
Background
With the development of internet technology, more and more applications are developed based on HTML5 (Hyper Text Mark-up Language), i.e., the services and contents carried by applications are provided to users through web pages. Since the front-end content of the web application is usually very light (more content is put in the background server), and thus can be easily integrated into the third-party platform, today, one way of integrating the web application with the third-party platform is: the webpage application provides services and contents of the application, and the third-party platform provides functions of user login and the like in a centralized manner, so that the development process of the webpage application and the contents of the application front end are further simplified, and the popularization and development of the webpage application are facilitated.
The integration mode of the webpage application and the third-party platform has the problems that the webpage application is not in charge of user login, user login information is managed by the third-party platform, and the webpage application page does not store the user login information, so that a user cannot directly initiate services such as payment and sharing through the webpage application page.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and a system for processing web page information, which can implement initiating external service processing through a web application page.
In order to solve the above technical problem, an embodiment of the present invention provides a method for processing web page information, where the method includes:
the method comprises the steps that a webpage application page detects a trigger event aiming at a target service, an inline page aiming at the target service is established according to the trigger event, and a message event monitoring task is established, wherein the webpage application page is a page under a first domain name, the inline page is a front-end page of a login server of the webpage application page, and the front-end page of the login server is a page under a second domain name;
the inline page acquires user account information of the webpage application page from the login server, and sends service request information to a service server corresponding to a target service according to the acquired user account information of the webpage application page;
the inline page receives service callback information returned by the service server according to the service request, and transmits the service callback information to the webpage application page;
and the webpage application page receives the service callback information through the message event monitoring task.
Correspondingly, the embodiment of the invention also provides a webpage information processing system, which comprises a webpage application page and at least one inline page created by the webpage application page, wherein:
the webpage application page is used for creating an inline page aiming at a target service according to a trigger event and creating a message event monitoring task when the trigger event aiming at the target service is detected, wherein the webpage application page is a page under a first domain name, the inline page is a front-end page of a login server of the webpage application page, and the front-end page of the login server is a page under a second domain name;
the inline page is used for acquiring user account information of the webpage application page from the login server and sending service request information to a service server corresponding to a target service according to the acquired user account information of the webpage application page;
the inline page is further configured to receive service callback information returned by the service server according to the service request, and transmit the service callback information to the web application page;
and the webpage application page is also used for receiving the service callback information through the message event monitoring task.
The webpage application page acquires user account information by creating an inline page under a domain name corresponding to a login server of the webpage application page, the inline page initiates a service request according to the acquired user account information and transmits service callback information to the webpage application page, and the webpage application page receives the service callback information through a created message event monitoring task, so that a service flow is completed, and the loss of application process information caused by page jump of the webpage application page for initiating external services is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram of a network architecture of a web page information processing system according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a method for processing web page information according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating a method for processing web page information according to another embodiment of the present invention;
fig. 4 is a flowchart illustrating a method for processing web page information in a payment scenario according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic diagram of a network architecture where a web page information processing system is located in an embodiment of the present invention, as shown in the figure, the web page information processing system in the embodiment of the present invention may include a web page application page and at least one inline page created by the web page application page, the web page information processing system may be supported in user equipment shown in fig. 1, the user equipment may include a personal computer, a notebook computer, a tablet computer, a smart phone, a wearable smart device, a vehicle-mounted terminal, an electronic reader, or the like, and the user equipment may communicate with a network backend server through a network, such as the web page application server, a login server, and a service server shown in the figure.
The webpage application server is a background server of the webpage application page and provides the content of the webpage application page for the user equipment part.
The login server provides user account login service for the web application page in a centralized manner, the user account information of the web application page is stored in the login server, and the user account information of the web application page can be acquired by accessing the page under the domain name corresponding to the login server. In an optional embodiment, the login server provides a user account login service for the web application page in a centralized manner, and may also be responsible for other business services, such as information sharing, data cloud storage, payment initiation, and the like. For example, it may be an SDK (software development kit) platform server.
The business server provides other business services for the web application page, such as data transfer, data processing, data sharing, data storage business and the like, and different business servers can provide corresponding business for the web application page, such as a payment server, a social server, a storage server and the like.
The web application page may be a web page based on HTML5, and the page content may include a web application, such as a social application, a communication application, a game application, a multimedia application, etc., and the application interface and the corresponding content may be presented to the user in the user equipment, and the instructions input by the user may be obtained through an input device (such as a touch screen, a mouse, a keyboard, a microphone, etc.) of the user equipment.
The inline page, that is, a page of an inline frame in a web page, may be, for example, a page of an iframe frame, which is referred to as an iframe page for short, and is a page created when the web application page needs to access page content under other domain names in the web application page through the page of the inline frame. An iframe is an HTML tag that identifies a document, or floating FRAME (FRAME), in a document with which an inline FRAME object (i.e., inline FRAME object) contained in a document can be created. The web application page may create 1 or more of the inline pages as needed, for example, different inline pages are respectively corresponding to different services or created according to different service processing manners.
In the embodiment of the present invention, the web application page is configured to, when a trigger event for a target service is detected, create an inline page for the target service according to the trigger event, and create a message event monitoring task, where the web application page is a page under a first domain name, the inline page is a front-end page of a login server of the web application page, and the front-end page of the login server is a page under a second domain name, that is, in the embodiment of the present invention, a domain name of the web application page is different from a domain name of the login server.
The trigger event for the target service may be that the web application page detects that a user clicks a trigger button of the target service in the web application page, or the web application page detects that a trigger condition of the target service is met so as to automatically trigger the target service, for example, a game video saving service is automatically triggered after a game for game is completed, or a service for saving a conference summary is automatically triggered after a three-party online conference is completed, and the like.
The message event monitoring task may be a window. For example, the web application page may create a window, addeventlistener ("message", messageEvent) monitor, and when there is a postmessage, the web application page receives the message.
The inline page is used for acquiring the user account information of the webpage application page from the login server and sending service request information to a service server corresponding to a target service according to the acquired user account information of the webpage application page.
In a specific embodiment, after the inline page is opened, the user account information of the web application page may be acquired from the login server by using user cache data (cookie) corresponding to the domain name corresponding to the login server and stored in the user device. The user account information of the web application page may include user login information or user authority information, the user login information may include a user identifier, a login state, a login token (token), and the like of a user account, and the user authority information may represent code information of a user authority, such as a skey.
The inline page sends service request information to a service server corresponding to a target service according to the obtained user account information of the web application page, and specifically, the inline page sends the service request information for the target service to the service server, and the user account information of the web application page is carried to represent the identity of a service requester.
The inline page is further configured to receive service callback information returned by the service server according to the service request, and transmit the service callback information to the web application page;
the service callback information may be a result of the service server performing service processing on the service request, for example, if the service request is a request for the service server to create a payment order, the service callback information may include the payment order created according to the service request, and if the service request is a request for storing target data, the service callback information may include a corresponding data storage path and the like.
For example, the inline page may transmit the service callback information to the web application page through a postMessage. The postMessage is a common function in a Windows API (application program interface), and is used to place (send) a message into a contact message queue of a thread corresponding to a designated window, and return the message without waiting for the thread to process the message, and is in an asynchronous message mode.
The webpage application page is also used for receiving the service callback information through the message event monitoring task, and further the webpage application page can feed back a processing result of a target service to a user according to the service callback information.
In an optional embodiment, before the inline page sends the service request information to the service server corresponding to the target service according to the obtained user account information of the web application page, the inline page may first obtain the service information of the target service from the web application page, that is, the web application page first transmits the service information of the target service to the inline page, and the inline page may thus send the service request information to the service server corresponding to the target service according to the service information of the target service, where the service request information carries the user account information of the web application page. The service information of the target service may include a service identifier, a service parameter, a service object identifier, and the like, and for example, the service information may include a purchase object name, a purchase amount, a payment method, and the like. The transmission mode of the web application page first transmitting the service information of the target service to the inline page may optionally refer to a mode of transmitting data to the web application page by the above inline page, that is, an inline page creates a message event monitoring task (e.g., window.
According to the webpage information processing system in the embodiment of the invention, the webpage application page acquires the user account information by creating the inline page under the corresponding domain name of the login server, the inline page initiates the service request according to the acquired user account information and transmits the service callback information to the webpage application page, and the webpage application page receives the service callback information through the created message event monitoring task, so that the service flow is completed, and the problem that the webpage application page jumps to initiate external services to cause the loss of application process information, for example, the webpage application page needs to jump to the page under the corresponding domain name of the login server to acquire the user account information, and the loss of the application process information is likely to occur in the process of page jump to cause troubles for users is avoided.
Fig. 2 is a schematic flowchart of a method for processing web page information in an embodiment of the present invention, where as shown in the figure, the method for processing web page information in the embodiment includes:
s101, the webpage application page detects a trigger event aiming at the target service.
The trigger event for the target service may be that the web application page detects that a user clicks a trigger button of the target service in the web application page, or the web application page detects that a trigger condition of the target service is met so as to automatically trigger the target service, for example, a game video saving service is automatically triggered after a game for game is completed, or a service for saving a conference summary is automatically triggered after a three-party online conference is completed, and the like.
S102, a webpage application page creates an inline page aiming at the target service according to the trigger event, wherein the webpage application page is a page under a first domain name, the inline page is a front-end page of a login server of the webpage application page, and the front-end page of the login server is a page under a second domain name.
The inline page, that is, a page of an inline frame in a web page, may be, for example, a page of an iframe frame, which is referred to as an iframe page for short, and is a page created when the web application page needs to access page content under other domain names in the web application page through the page of the inline frame. An iframe is an HTML tag that identifies a document, or floating FRAME (FRAME), in a document with which an inline FRAME object (i.e., inline FRAME object) contained in a document can be created. The web application page may create 1 or more of the inline pages as needed, for example, different inline pages are respectively corresponding to different services or created according to different service processing manners.
The login server provides user account login service for the web application page in a centralized manner, the user account information of the web application page is stored in the login server, and the user account information of the web application page can be acquired by accessing the page under the domain name corresponding to the login server. In an optional embodiment, the login server provides a user account login service for the web application page in a centralized manner, and may also be responsible for other business services, such as information sharing, data cloud storage, payment initiation, and the like. For example, it may be an SDK (software development kit) platform server.
S103, the webpage application page creates a message event monitoring task.
The message event monitoring task may be a window. For example, the web application page may create a window, addeventlistener ("message", messageEvent) monitor, and when there is a postmessage, the web application page receives the message.
S104, the inline page acquires the user account information of the webpage application page from the login server.
In a specific embodiment, after the inline page is opened, the user account information of the web application page may be acquired from the login server by using user cache data (cookie) corresponding to the domain name corresponding to the login server and stored in the user device. The user account information of the web application page may include user login information or user authority information, the user login information may include a user identifier, a login state, a login token (token), and the like of a user account, and the user authority information may represent code information of a user authority, such as a skey.
And S105, the inline page sends service request information to a service server corresponding to the target service according to the acquired user account information of the webpage application page.
The business server provides other business services for the web application page, such as data transfer, data processing, data sharing, data storage business and the like, and different business servers can provide corresponding business for the web application page, such as a payment server, a social server, a storage server and the like.
The inline page sends service request information to a service server corresponding to a target service according to the obtained user account information of the web application page, and specifically, the inline page sends the service request information for the target service to the service server, and the user account information of the web application page is carried to represent the identity of a service requester.
And S106, the inline page receives the service callback information returned by the service server according to the service request.
The service callback information may be a result of the service server performing service processing on the service request, for example, if the service request is a request for the service server to create a payment order, the service callback information may include the payment order created according to the service request, and if the service request is a request for storing target data, the service callback information may include a corresponding data storage path and the like.
And S107, the inline page transmits the service callback information to the webpage application page.
For example, the inline page may transmit the service callback information to the web application page through a postMessage. The postMessage is a common function in a Windows API (application program interface), and is used to place (send) a message into a contact message queue of a thread corresponding to a designated window, and return the message without waiting for the thread to process the message, and is in an asynchronous message mode.
And S108, the webpage application page receives the service callback information through the message event monitoring task.
The webpage application page acquires user account information by creating an inline page under a domain name corresponding to a login server of the webpage application page, the inline page initiates a service request according to the acquired user account information and transmits service callback information to the webpage application page, and the webpage application page receives the service callback information through a created message event monitoring task, so that a service flow is completed, and the loss of application process information caused by page jump of the webpage application page for initiating external services is avoided.
Fig. 3 is a schematic flow chart of a web page information processing method in another embodiment of the present invention, and as shown in the figure, the web page information processing method in the embodiment may include the following flows:
s201, the webpage application page detects a trigger event aiming at the target service.
The trigger event for the target service may be that the web application page detects that a user clicks a trigger button of the target service in the web application page, or the web application page detects that a trigger condition of the target service is met so as to automatically trigger the target service, for example, a game video saving service is automatically triggered after a game for game is completed, or a service for saving a conference summary is automatically triggered after a three-party online conference is completed, and the like.
S202, the webpage application page creates an inline page aiming at the target service according to the trigger event, wherein the webpage application page is a page under a first domain name, the inline page is a front-end page of a login server of the webpage application page, and the front-end page of the login server is a page under a second domain name.
S203, the webpage application page transmits the service information of the target service to the inline page.
In an alternative embodiment, the inline page may create a message event monitoring task (e.g., window. addeventlistener ("message"), for monitoring a message sent by the web application page, and the web application page may transmit the service information of the target service to the inline page through the postMessage, and the inline page may receive the service information of the target service through the message event monitoring task. In other optional embodiments, the web application page may also transfer the service information of the target service to the inline page while creating the inline page, and the inline page may obtain (inherit) the service information of the target service of the parent page as a child page.
And S204, the webpage application page creates a message event monitoring task.
The message event monitoring task may be a window. For example, the web application page may create a window, addeventlistener ("message", messageEvent) monitor, and when there is a postmessage, the web application page receives the message.
S205, the user account information of the webpage application page is obtained from the login server by the inline page.
In a specific embodiment, after the inline page is opened, the user account information of the web application page may be acquired from the login server by using user cache data (cookie) corresponding to the domain name corresponding to the login server and stored in the user device. The user account information of the web application page may include user login information or user authority information, the user login information may include a user identifier, a login state, a login token (token), and the like of a user account, and the user authority information may represent code information of a user authority, such as a skey.
S206, the inline page sends service request information to a service server corresponding to the target service according to the service information of the target service, wherein the service request information carries the user account information of the webpage application page.
And S207, receiving the service callback information returned by the service server according to the service request by the inline page.
The service callback information may be a result of the service server performing service processing on the service request, for example, if the service request is a request for the service server to create a payment order, the service callback information may include the payment order created according to the service request, and if the service request is a request for storing target data, the service callback information may include a corresponding data storage path and the like.
And S208, the inline page transmits the service callback information to the webpage application page.
For example, the inline page may transmit the service callback information to the web application page through a postMessage. The postMessage is a common function in a Windows API (application program interface), and is used to place (send) a message into a contact message queue of a thread corresponding to a designated window, and return the message without waiting for the thread to process the message, and is in an asynchronous message mode.
S209, the webpage application page receives the service callback information through the message event monitoring task.
And S210, the webpage application page feeds back the processing result of the target service to the user according to the service callback information.
The webpage application page acquires user account information by creating an inline page under a domain name corresponding to a login server of the webpage application page, initiates a service request according to the acquired user account information after acquiring service information of a target service by the inline page through data transmission between the webpage application page and the inline page, and transmits service callback information to the webpage application page, so that a service flow is completed, and application process information loss caused by page jump of the webpage application page for initiating an external service is avoided.
Fig. 4 is a schematic flow chart of a method for processing web page information in a payment scenario of the present invention, and how to implement web page information processing in the present embodiment according to the present invention in a specific payment scenario, as shown in the figure, the method for processing web page information in the embodiment includes:
s301, the webpage application page detects that the user triggers payment.
In particular, the web application page may detect that the user has clicked a payment button in the page to trigger payment processing logic. Optionally, the payment amount input by the user may be obtained in this step, or the payment amount may not be input in other optional embodiments, for example, if the user selects to purchase a certain object in the web application page, only the object identifier of the purchased object needs to be obtained.
S302, the web application page requests the SDK server to create an initial payment order.
In this embodiment, the SDK server collectively provides user account login service and payment initiation service for the web application page. The optional web application page may carry the amount of money input by the user when requesting the SDK server to create the initial payment order, or may carry an object identifier of a purchase object selected by the user, so that the SDK server generates the corresponding initial payment order according to the request.
S303, the webpage application page receives the initial payment order returned by the SDK server.
The initial payment order is used to confirm the user for initiating payment.
S304, displaying the initial payment order by the webpage application page, and acquiring a confirmation instruction of the user for the initial payment order.
S305, establishing a first iframe by the webpage application page, wherein the first iframe is used for initiating and establishing a third-party payment order according to the acquired user account information after the user account information is acquired.
In this embodiment, the domain name of the first iframe is a corresponding domain name of the SDK server, that is, the first iframe is a front-end webpage of the SDK server, so that the first iframe can acquire the user account information of the webpage application page from the SDK server.
S306, the webpage application page transmits the initial payment order information to the first iframe.
In an alternative embodiment, the first iframe may create a message event listening task (e.g., window. addeventlistener ("message"), etc.) to listen for messages sent by the web application page, and the web application page may transmit the initial payment order information to the first iframe through the postMessage, and the first iframe may thus receive the initial payment order information through the message event listening task. In other optional embodiments, the web application page may also pass the initial payment order information to the first iframe while creating the first iframe, where the first iframe may obtain (inherit) the initial payment order information of the parent page as a child page.
S307, the webpage application page creates a message event monitoring task.
The message event monitoring task may be a window. For example, the web application page may create a window, addeventlistener ("message", messageEvent) monitor, and when there is a postmessage, the web application page receives the message. In an optional embodiment, the web application page may create different message event monitoring tasks for different iframes, so as to independently monitor messages sent by different iframes, or may implement monitoring of messages sent by multiple iframes by the same message event monitoring task.
S308, the first iframe acquires the user account information of the webpage application page.
In a specific embodiment, after the first iframe is created, the user account information of the web application page may be acquired from the SDK server by using user cache data (cookie) corresponding to the domain name of the SDK server and stored in the user equipment. The user account information of the web application page may include user login information or user authority information, the user login information may include a user identifier, a login state, a login token (token), and the like of a user account, and the user authority information may represent code information of a user authority, such as a skey.
S309, the first iframe sends a service request to the SDK server, requesting the SDK server to create a third party payment order, where the service request may carry the user account information and the service information of the current payment, such as the payment amount or the object identifier of the purchase object.
S310, the SDK server creates and returns a third party payment order to the first iframe.
S311, the first iframe transmits the third party payment order, which is service callback information returned by the SDK server in this embodiment, to the web application page.
In this embodiment, the first iframe may transmit the service callback information to the web application page through a postMessage.
S312, the webpage application page receives the third party payment order through the message event monitoring task.
S313, the webpage application page displays the third-party payment order and acquires a confirmation instruction of the user for the third-party payment order.
Compared with the initial payment order, the third-party payment order may carry more payment order contents, such as a payer name or a payer account identifier, a payment amount, a payee name or a payee account identifier, and may further include a name or channel information of a provider of the third-party payment service.
S314, the webpage application page creates a second iframe.
In this embodiment, the second iframe is used to initiate a payment request to a payment server of a third party.
In an alternative embodiment, the first iframe and the second iframe may also be the same iframe, and this step may be omitted.
S315, the webpage application page sends the third party payment order to the second iframe.
In an alternative embodiment, the second iframe may create a message event listening task (e.g., window. addeventlistener ("message"), etc.) to listen for messages sent by the web application page, and the web application page may transmit the third party payment order to the second iframe through the postMessage, and the second iframe may receive the third party payment order through the message event listening task. In other optional embodiments, the web application page may also pass the third party payment order to the second iframe while creating the second iframe, where the third party payment order for the parent page is available (inherited) by the second iframe as a child page.
And S316, the second iframe sends a payment service request to the third-party payment server, and the payment service request carries the third-party payment order.
The third party payment server is used for providing third party payment services, such as unionpay, Payment treasures, financial and payment services and the like.
And S317, the second iframe receives the payment service callback information returned by the third-party payment server.
The payment service callback information in this embodiment is a processing result of the third-party payment server on the third-party payment order.
And S318, the second iframe transmits the payment service callback information to the webpage application page.
In this embodiment, the second iframe may transmit the payment service callback information to the web application page through a postMessage.
And S319, the webpage application page receives the payment service callback information through the message event monitoring task.
Specifically, the message event monitoring task for monitoring and receiving the payment service callback information by the web application page may be the same as or different from the message event monitoring task in S312, that is, after the second iframe is created, the message event monitoring task for the second iframe is also correspondingly created, and is used to monitor the message sent by the second iframe.
And S320, the webpage application page feeds back the processing result of the payment service to the user according to the payment service callback information.
The webpage application page acquires user account information by creating an iframe under a domain name corresponding to the SDK server, initiates a payment service request according to the acquired user account information after acquiring a payment order of a payment service by the iframe through data transmission between the webpage application page and the iframe, and transmits payment service callback information to the webpage application page, so that the whole payment service process is completed, and the loss of application process information caused by page jump of the webpage application page for initiating the payment service is avoided.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.
The above disclosure is only for the purpose of illustrating the preferred embodiments of the present invention, and it is therefore to be understood that the invention is not limited by the scope of the appended claims.
Claims (11)
1. A method for processing web page information, the method comprising:
detecting a trigger event aiming at a target service by a webpage application page, creating an inline page aiming at the target service according to the trigger event, transmitting service information of the target service to the inline page, and creating a message event monitoring task, wherein the webpage application page is a page under a first domain name, the inline page is a front-end page of a login server of the webpage application page, and the front-end page of the login server is a page under a second domain name;
the inline page acquires user account information of the web application page from the login server by using user cache data corresponding to the login server;
the inline page sends service request information to a service server corresponding to the target service according to the service information of the target service, wherein the service request information carries user account information of the webpage application page;
the inline page receives service callback information returned by the service server according to the service request, and transmits the service callback information to the webpage application page;
and the webpage application page receives the service callback information through the message event monitoring task.
2. The web page information processing method of claim 1, wherein the inline page transmitting the service callback information to the web application page comprises:
and the inline page transmits the service callback information to the webpage application page through a postMessage.
3. The web page information processing method according to claim 1, wherein the message event listening task is window.addeventlistener;
the step of receiving the service callback information by the web application page through the message event monitoring task comprises the following steps:
and the webpage application page receives the service callback information through a window.
4. A web page information processing method according to claim 1, wherein the user account information includes user login information or user authority information.
5. The web page information processing method according to any one of claims 1 to 4, wherein the method further comprises:
and the webpage application page feeds back a processing result of the target service to the user according to the service callback information.
6. A web information processing system comprising a web application page and at least one inline page created from the web application page, wherein:
the webpage application page is used for creating an inline page aiming at a target service according to a trigger event when the trigger event aiming at the target service is detected, transmitting service information of the target service to the inline page and creating a message event monitoring task, wherein the webpage application page is a page under a first domain name, the inline page is a front-end page of a login server of the webpage application page, and the front-end page of the login server is a page under a second domain name;
the inline page is used for acquiring user account information of the webpage application page from the login server by using user cache data corresponding to the login server, and sending service request information to a service server corresponding to a target service according to the service information of the target service, wherein the service request information carries the user account information of the webpage application page;
the inline page is further configured to receive service callback information returned by the service server according to the service request, and transmit the service callback information to the web application page;
and the webpage application page is also used for receiving the service callback information through the message event monitoring task.
7. The web page information processing system of claim 6,
the transmitting, by the inline page, the service callback information to the web application page includes:
and the inline page transmits the service callback information to the webpage application page through a postMessage.
8. The web page information processing system according to claim 6, wherein the message event listening task is window.addeventlistener;
the step of receiving the service callback information by the web application page through the message event monitoring task comprises the following steps:
and the webpage application page receives the service callback information through a window.
9. A web page information processing system according to claim 6, wherein the user account information includes user login information or user authority information.
10. The web page information processing system according to any one of claims 6 to 9,
and the webpage application page is also used for feeding back a processing result of the target service to the user according to the service callback information.
11. A computer-readable storage medium, characterized in that the computer-readable storage medium is used for storing a computer program, which is executed by a processor for performing the method according to any of the claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610629808.5A CN107688570B (en) | 2016-08-03 | 2016-08-03 | Webpage information processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610629808.5A CN107688570B (en) | 2016-08-03 | 2016-08-03 | Webpage information processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107688570A CN107688570A (en) | 2018-02-13 |
| CN107688570B true CN107688570B (en) | 2021-04-30 |
Family
ID=61151360
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610629808.5A Active CN107688570B (en) | 2016-08-03 | 2016-08-03 | Webpage information processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107688570B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109684047A (en) * | 2018-08-21 | 2019-04-26 | 平安普惠企业管理有限公司 | Event-handling method, device, equipment and computer storage medium |
| CN110942289B (en) * | 2018-09-21 | 2021-06-04 | 亿度慧达教育科技（北京）有限公司 | Payment method and computer storage medium |
| CN110096372A (en) * | 2019-03-13 | 2019-08-06 | 平安普惠企业管理有限公司 | Information transferring method, device, computer equipment and computer readable storage medium |
| CN110348859A (en) * | 2019-06-17 | 2019-10-18 | 阿里巴巴集团控股有限公司 | A kind of complaint processing method and system |
| CN110633443B (en) * | 2019-08-30 | 2023-08-08 | 腾讯科技（深圳）有限公司 | Method, device, equipment and medium for intra-page data communication |
| CN112905168B (en) * | 2021-02-08 | 2024-04-26 | 中国工商银行股份有限公司 | Method and device for generating visual front-end page based on block |
| CN113051511B (en) * | 2021-03-08 | 2024-03-12 | 北京百度网讯科技有限公司 | Page message distribution method, device, equipment and storage medium |
| CN113238881B (en) * | 2021-05-28 | 2024-01-30 | 北京达佳互联信息技术有限公司 | Page communication method and device |
| CN113282863B (en) * | 2021-06-11 | 2023-04-21 | 上海哔哩哔哩科技有限公司 | Service page generation method and device |
| CN113190367B (en) * | 2021-07-02 | 2021-10-01 | 成都数联铭品科技有限公司 | Cross-system data interaction method and device based on browser and electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102710759A (en) * | 2012-05-22 | 2012-10-03 | 中国联合网络通信集团有限公司 | Web server, business logging method and system |
| CN104965690A (en) * | 2014-04-18 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Method and apparatus for processing data |
| CN105610938A (en) * | 2015-12-24 | 2016-05-25 | 广州爱九游信息技术有限公司 | Logging status synchronization method and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160110766A1 (en) * | 2014-10-16 | 2016-04-21 | Oracle International Corporation | System and method of displaying social ads along with organic or paid search results |
-
2016
- 2016-08-03 CN CN201610629808.5A patent/CN107688570B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102710759A (en) * | 2012-05-22 | 2012-10-03 | 中国联合网络通信集团有限公司 | Web server, business logging method and system |
| CN104965690A (en) * | 2014-04-18 | 2015-10-07 | 腾讯科技（深圳）有限公司 | Method and apparatus for processing data |
| CN105610938A (en) * | 2015-12-24 | 2016-05-25 | 广州爱九游信息技术有限公司 | Logging status synchronization method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107688570A (en) | 2018-02-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107688570B (en) | Webpage information processing method and system | |
| US10699301B2 (en) | Data-processing method and apparatus, and computer storage medium for electronic resource transfer | |
| KR102237912B1 (en) | Methods and devices to implement service functions | |
| US10623353B2 (en) | Method and system for controlling message dissemination from public accounts to user accounts | |
| CN105530175B (en) | Message processing method, device and system | |
| US10326715B2 (en) | System and method for updating information in an instant messaging application | |
| CN111160845B (en) | Service processing method and device | |
| JP6306187B2 (en) | Dynamic telephone number assignment | |
| US9807044B2 (en) | Selective communication of messages | |
| CN107979632B (en) | Processing method, device and system for push information | |
| US20160352816A1 (en) | Method and system for sharing data between social networking platforms | |
| WO2015043540A1 (en) | Methods, systems, and devices for sharing multimedia information | |
| CN104753911A (en) | Information processing method based on communication & social application, relevant device and system | |
| CN106487655B (en) | Message interaction method and device and processing server | |
| WO2014176896A1 (en) | System and method for updating information in an instant messaging application | |
| CN108122124B (en) | Information pushing method, platform and system | |
| CN112346608A (en) | Page display method and device based on business activity result display and electronic equipment | |
| WO2022078397A1 (en) | Communication method and apparatus, device, and storage medium | |
| CN112822089B (en) | Method and device for adding friends | |
| US20200265481A1 (en) | Donor and recipient authentic authorization | |
| CN113609413A (en) | Questionnaire delivery method, system, equipment, medium and product | |
| CN109768921B (en) | Data transparent transmission method and corresponding instant communication terminal | |
| CN112306596A (en) | Information interaction method and device and electronic equipment | |
| CN111125211A (en) | Contract establishing method and device, computer readable medium and electronic equipment | |
| CN111105301A (en) | Information processing method, terminal, server 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 |