CN113626158A - Event agent-based embedded point execution method and device - Google Patents
Event agent-based embedded point execution method and device Download PDFInfo
- Publication number
- CN113626158A CN113626158A CN202110929785.0A CN202110929785A CN113626158A CN 113626158 A CN113626158 A CN 113626158A CN 202110929785 A CN202110929785 A CN 202110929785A CN 113626158 A CN113626158 A CN 113626158A
- Authority
- CN
- China
- Prior art keywords
- event
- setting
- page
- attribute
- point
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 238000004590 computer program Methods 0.000 claims description 16
- 235000009508 confectionery Nutrition 0.000 claims 1
- 230000003993 interaction Effects 0.000 abstract description 10
- 238000012423 maintenance Methods 0.000 abstract description 10
- 238000011161 development Methods 0.000 abstract description 8
- 230000009545 invasion Effects 0.000 abstract description 6
- 239000003795 chemical substances by application Substances 0.000 description 36
- 230000006870 function Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 12
- 230000000007 visual effect Effects 0.000 description 10
- 238000012544 monitoring process Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 230000006399 behavior Effects 0.000 description 4
- 230000005587 bubbling Effects 0.000 description 4
- 239000000872 buffer Substances 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005206 flow analysis Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- 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/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
-
- 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/957—Browsing optimisation, e.g. caching or content distillation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/14—Tree-structured documents
- G06F40/143—Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The embodiment of the application provides a buried point execution method and a buried point execution device based on an event agent, which relate to the field of finance, and the method comprises the following steps: adding a setting event triggering the execution of the embedded point to an agent event of a setting page main body element; adding a set attribute to an attribute list of the document object element to be buried; and responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute. The method has no invasion to the logic part of the service agent and UI display and interaction; the compatibility to the browser is good, the browser does not depend on any frame, and the universality is strong; the development and maintenance costs are low.
Description
Technical Field
The application relates to the fields of finance and the like, in particular to a buried point execution method and device based on event agency.
Background
The existing point-burying scheme mainly has the following three modes: first, code embedding: inserting a section of code in various response events, storing the monitoring behavior or directly transmitting the monitoring behavior to a server end in a certain data format; secondly, visually burying points: and (4) embedding points in place of codes by means of visual interaction. Separating the service code and the embedded point code, providing a visual interactive page, inputting the page as the service code, adding embedded point events and the like in the service code in a self-defined manner through the visual system, and finally outputting the code which is coupled with the service code and the embedded point code; thirdly, no buried point is present: the non-buried point is not required to be buried, but is all buried points, any event at the front end is bound with a mark, and all events are recorded. The data which we want is analyzed by uploading the record file regularly and matching with file analysis.
Each code burying point needs to be added with a corresponding code, so that the intrusion on the service codes is high, the risk is high, the workload is large, and the maintenance is difficult; the visual embedded point sounds high and is actually not greatly different from the code embedded point, and only one system is used for realizing the process of manually inserting the embedded point code. The visual embedded point depends on the system, and the flexibility is low; the non-buried point can increase a lot of pressure for data transmission and a server due to the fact that the full amount of data is collected, the overall performance of the system is reduced, and the data which are required to be uploaded by each event cannot be flexibly customized.
Disclosure of Invention
Aiming at the problems in the prior art, the application provides a buried point execution method and device based on event proxy, wherein a setting event triggering the buried point execution is added to a proxy event of a setting page main element; adding a set attribute to an attribute list of the document object element to be buried; and responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute. The invention has no invasion to the logic part of the service agent and UI display and interaction; the compatibility to the browser is good, the browser does not depend on any frame, and the universality is strong; the development and maintenance costs are low.
In one aspect of the present invention, an event agent-based embedded point execution method is provided, including:
adding a setting event triggering the execution of the embedded point to an agent event of a setting page main body element;
adding a set attribute to an attribute list of the document object element to be buried;
and responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute.
In a preferred embodiment, further comprising:
and acquiring and defining a page as the setting page.
In a preferred embodiment, further comprising:
and determining a set event for triggering the execution of the buried point.
In a preferred embodiment, the setting of the attribute value of the attribute includes:
calling page information, calling element name information, calling element level information, calling url information, browser version information and kernel information.
In a preferred embodiment, further comprising:
and acquiring the main body element of the setting page.
In another aspect of the present invention, an event agent-based embedded point executing apparatus is provided, including:
the proxy event adding module is used for adding a set event triggering the execution of the embedded point into a proxy event of a set page main element;
the set attribute adding module is used for adding a set attribute to an attribute list of the document object element of the point to be buried;
and the buried point execution module responds to the trigger of the setting event on the setting page and executes corresponding buried point operation on the document object element with the setting attribute.
In a preferred embodiment, further comprising:
and the setting page definition module acquires and defines a page as the setting page.
In a preferred embodiment, further comprising:
and the setting event determining module is used for determining the setting event executed by the trigger buried point.
In a preferred embodiment, the setting of the attribute value of the attribute includes:
calling page information, calling element name information, calling element level information, calling url information, browser version information and kernel information.
In a preferred embodiment, further comprising:
and the main element acquisition module is used for acquiring the main elements of the set page.
In another aspect of the present invention, the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the event agent-based embedded point execution method when executing the program.
In still another aspect of the present invention, the present application provides a computer-readable storage medium having a computer program stored thereon, which when executed by a processor, implements the event agent-based buried point execution method.
According to the technical scheme, the embedded point execution method based on the event agent comprises the following steps: adding a setting event triggering the execution of the embedded point to an agent event of a setting page main body element; adding a set attribute to an attribute list of the document object element to be buried; and responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute. The invention has no invasion to the logic part of the service agent and UI display and interaction; the compatibility to the browser is good, the browser does not depend on any frame, and the universality is strong; the development and maintenance costs are low.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a flow chart of a buried point execution method based on an event agent.
FIG. 2 is a schematic flow chart diagram of an embodiment.
Fig. 3 is a schematic diagram of a buried point execution node structure based on an event agent.
Fig. 4 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the embedded point execution method and device based on the event broker disclosed in the present application can be used in the financial field, and can also be used in any field other than the financial field and other fields.
The existing point-burying scheme mainly has the following three modes: first, code embedding: inserting a section of code in various response events, storing the monitoring behavior or directly transmitting the monitoring behavior to a server end in a certain data format; secondly, visually burying points: and (4) embedding points in place of codes by means of visual interaction. Separating the service code and the embedded point code, providing a visual interactive page, inputting the page as the service code, adding embedded point events and the like in the service code in a self-defined manner through the visual system, and finally outputting the code which is coupled with the service code and the embedded point code; thirdly, no buried point is present: the non-buried point is not required to be buried, but is all buried points, any event at the front end is bound with a mark, and all events are recorded. The data which we want is analyzed by uploading the record file regularly and matching with file analysis.
Each code burying point needs to be added with a corresponding code, so that the intrusion on the service codes is high, the risk is high, the workload is large, and the maintenance is difficult; the visual embedded point sounds high and is actually not greatly different from the code embedded point, and only one system is used for realizing the process of manually inserting the embedded point code. The visual embedded point depends on the system, and the flexibility is low; the non-buried point can increase a lot of pressure for data transmission and a server due to the fact that the full amount of data is collected, the overall performance of the system is reduced, and the data which are required to be uploaded by each event cannot be flexibly customized.
Aiming at the problems in the prior art, the application provides a buried point execution method and device based on event proxy, wherein a setting event triggering the buried point execution is added to a proxy event of a setting page main element; adding a set attribute to an attribute list of the document object element to be buried; responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute, so that the method has no invasion to the logic part and UI (user interface) display and interaction of the service agent; the compatibility to the browser is good, the browser does not depend on any frame, and the universality is strong; the development and maintenance costs are low.
The following describes the embedded point execution method and device based on the event broker in detail with reference to the accompanying drawings.
In an embodiment, an event agent-based embedded point execution method is provided, as shown in fig. 1, and includes the following specific steps:
s1, adding the setting event triggering the execution of the buried point to the proxy event of the main element of the setting page;
specifically, the event agent is a common skill for binding events in JavaScript, that is, an event that originally needs to be bound to a child element is delegated to a parent element, so that the parent element serves as an event monitoring task. The principle of event brokering is event bubbling of document object elements. For a page, the parent element is the main element of the outermost layer, so the setting event triggering the execution of the buried point is added to the proxy event of the main element of the page. In a specific embodiment, a page is first acquired and defined as a set page, it can be understood that the set page is a page to be monitored, where a point needs to be buried, and acquiring the page is to acquire code information and page element structure information of the page. In a specific embodiment, the setting event triggering the execution of the buried point may be set to any event related to the page, such as a click event, a page loading event, a mouse moving event, and the like. Once an event is determined as a set event that triggers the execution of a buried point, the buried point execution may be triggered when the user executes the event on the page.
S2, adding a set attribute to the attribute list of the document object element of the point to be buried;
specifically, the page DOM is a tree structure that represents a page document as elements, attributes, and text, and each component in the page document is a node. The DOM is defined as follows: the entire document is a document node, each page tag is an element node, the text contained in the page element is a text node, and each page attribute is an attribute node. It will be appreciated that each element node or text node has a corresponding attribute node. And if the certain document object element needs to be subjected to point burying, adding a set attribute into the corresponding attribute list. In subsequent buried point triggering, only document object elements having set attributes will be buried. The attribute values of the set attributes comprise calling page information, calling element name information, calling element level information, calling url information, browser version information and kernel information.
In a specific embodiment, after a setting attribute is newly added to a document object element needing to be embedded, not all setting events are proxied, and the setting attribute needs to be manually added to the document object element needing to be embedded; if the service has personalized embedded point information to be uploaded, the service can be defined into an attribute value of a set attribute, the value is an object, and the key value is used for storing the information, so that the flexibility is increased.
And S3, responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute.
Specifically, the page is used for embedding points, namely for flow analysis. The meaning of traffic includes many: number of Page Views (PV), number of independent visitors (UV), IP, page dwell time, page operation time, number of page accesses, number of button clicks, number of file downloads, etc. When a setting event on a page occurs, the document object element with the setting attribute executes the corresponding buried point operation. In a specific embodiment, if the set proxy event is a page loading event, the embedded point operation is to upload browser version information, kernel information, page element information, loading time information, loading url information, and the like of a currently loaded page.
The present invention will be further described with reference to a specific implementation scenario.
Scene one: page pointing is performed by a proxy page click event, as in FIG. 2.
S101, acquiring and defining a page as a monitoring page to obtain a DOM structure tree of the page. The event to be proxied is added to the parent element in the DOM structure tree, the item uses the framework Vue, the single page application, so only the event to be proxied needs to be added to the outermost body element. In this implementation scenario, the click event is selected as the proxied event.
And S102, introducing an md.js configuration file to facilitate switching between the non-buried point scheme and the personalized buried point scheme, wherein the configuration file comprises whether the non-buried point scheme is started or not and a set attribute name for the personalized buried point. In the implementation scenario, the attribute name is set to data-md, and the no-buried-point scheme is set to not be started.
S103, adding set attribute data-md to the DOM node needing the embedded point, wherein all click events are not proxied due to the fact that a non-embedded point scheme is not started, and the data-md attribute needs to be manually added to the DOM node needing the embedded point; the method includes the steps that personalized data-md attribute values, calling pages, calling elements, calling element levels, calling urls, browser versions, kernels and the like can automatically acquire information and are uniformly processed by proxy functions, theoretically, proxy embedded points can be started as long as data-md attributes are defined, but if personalized embedded point information of services needs to be uploaded, the data-md attributes can be defined into the attribute values of the data-md, the values are an object, and the stored information is strengthened, so that flexibility is improved.
S104, clicking any element on the page by the user, triggering a clicking event due to a bubbling mechanism, checking whether a clicked target DOM contains a data-md attribute, if so, calling a buried point api to finish uploading of buried point information, and if not, indicating that a self-defined value exists, and synchronously uploading the data after analyzing the data-md.
From the above description, the embedded point executing method based on event agent according to the present invention adds the setting event triggering the embedded point execution to the agent event of the main element of the setting page; adding a set attribute to an attribute list of the document object element to be buried; and responding to the trigger of the setting event on the setting page, and executing corresponding point burying operation on the document object element with the setting attribute, so that the method can accurately reflect the execution conditions of the database statements in different time periods in a real operating environment, has good universality, and can detect the database statements in different types.
From the software aspect, the present application provides an embodiment of an event agent-based embedded point execution device for executing all or part of the contents in the event agent-based embedded point execution method, and referring to fig. 3, the event agent-based embedded point execution device specifically includes the following contents:
the proxy event adding module 1 is used for adding a setting event for triggering the execution of the embedded point into a proxy event of a setting page main element;
the set attribute adding module 2 is used for adding a set attribute to an attribute list of the document object element of the point to be buried;
and the buried point execution module 3 responds to the trigger of the setting event on the setting page and executes corresponding buried point operation on the document object element with the setting attribute.
As can be seen from the above description, the embedded point executing device based on event agent according to the present invention adds the setting event triggering the embedded point execution to the agent event of the main element of the setting page; adding a set attribute to an attribute list of the document object element to be buried; and responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute. The invention has no invasion to the logic part of the service agent and UI display and interaction; the compatibility to the browser is good, the browser does not depend on any frame, and the universality is strong; the development and maintenance costs are low.
In a specific embodiment, an event agent-based embedded point executing apparatus is provided, which specifically includes:
the proxy event adding module 1 is used for adding a setting event for triggering the execution of the embedded point into a proxy event of a setting page main element;
specifically, the event agent is a common skill for binding events in JavaScript, that is, an event that originally needs to be bound to a child element is delegated to a parent element, so that the parent element serves as an event monitoring task. The principle of event brokering is event bubbling of document object elements. For a page, the parent element is the main element of the outermost layer, so the setting event triggering the execution of the buried point is added to the proxy event of the main element of the page. In a specific embodiment, a page is first acquired and defined as a set page, it can be understood that the set page is a page to be monitored, where a point needs to be buried, and acquiring the page is to acquire code information and page element structure information of the page. In a specific embodiment, the setting event triggering the execution of the buried point may be set to any event related to the page, such as a click event, a page loading event, a mouse moving event, and the like. Once an event is determined as a set event that triggers the execution of a buried point, the buried point execution may be triggered when the user executes the event on the page.
The set attribute adding module 2 is used for adding a set attribute to an attribute list of the document object element of the point to be buried;
specifically, the page DOM is a tree structure that represents a page document as elements, attributes, and text, and each component in the page document is a node. The DOM is defined as follows: the entire document is a document node, each page tag is an element node, the text contained in the page element is a text node, and each page attribute is an attribute node. It will be appreciated that each element node or text node has a corresponding attribute node. And if the certain document object element needs to be subjected to point burying, adding a set attribute into the corresponding attribute list. In subsequent buried point triggering, only document object elements having set attributes will be buried. The attribute values of the set attributes comprise calling page information, calling element name information, calling element level information, calling url information, browser version information and kernel information.
In a specific embodiment, after a setting attribute is newly added to a document object element needing to be embedded, not all setting events are proxied, and the setting attribute needs to be manually added to the document object element needing to be embedded; if the service has personalized embedded point information to be uploaded, the service can be defined into an attribute value of a set attribute, the value is an object, and the key value is used for storing the information, so that the flexibility is increased.
And the buried point execution module 3 responds to the trigger of the setting event on the setting page and executes corresponding buried point operation on the document object element with the setting attribute.
Specifically, the page is used for embedding points, namely for flow analysis. The meaning of traffic includes many: number of Page Views (PV), number of independent visitors (UV), IP, page dwell time, page operation time, number of page accesses, number of button clicks, number of file downloads, etc. When a setting event on a page occurs, the document object element with the setting attribute executes the corresponding buried point operation. In a specific embodiment, if the set proxy event is a page loading event, the embedded point operation is to upload browser version information, kernel information, page element information, loading time information, loading url information, and the like of a currently loaded page.
The present invention will be further described with reference to a specific implementation scenario.
Scene one: by using the device of the invention, page embedding is executed by proxy page click events.
The agent event adding module is used for executing the following contents: and acquiring and defining a page as a monitoring page to obtain a DOM structure tree of the page. The event to be proxied is added to the parent element in the DOM structure tree, the item uses the framework Vue, the single page application, so only the event to be proxied needs to be added to the outermost body element. In this implementation scenario, the click event is selected as the proxied event.
The setting attribute adding module is used for executing the following contents: in order to facilitate switching between the non-buried point scheme and the personalized buried point scheme, an md.js configuration file is introduced, and the configuration file comprises whether the non-buried point scheme is started or not and a set attribute name for the personalized buried point. In the implementation scenario, the attribute name is set to data-md, and the no-buried-point scheme is set to not be started. Adding set attribute data-md to a DOM node needing a buried point, wherein all click events are not proxied due to the fact that a non-buried point scheme is not started, and the data-md attribute needs to be manually added to the DOM node needing the buried point;
the buried point execution module is used for executing the following contents: the method includes the steps that personalized data-md attribute values, calling pages, calling elements, calling element levels, calling urls, browser versions, kernels and the like can automatically acquire information and are uniformly processed by proxy functions, theoretically, proxy embedded points can be started as long as data-md attributes are defined, but if personalized embedded point information of services needs to be uploaded, the data-md attributes can be defined into the attribute values of the data-md, the values are an object, and the stored information is strengthened, so that flexibility is improved. The user clicks any element on the page, a clicking event is triggered due to a bubbling mechanism, whether a clicked target DOM contains a data-md attribute is checked, if yes, a buried point api is called to finish uploading of buried point information, if the data-md is not null, a self-defined value is shown, and the data can be synchronously uploaded after being analyzed.
As can be seen from the above description, the embedded point executing apparatus based on event agent provided by the present invention includes an agent event adding module 1, which adds a setting event triggering embedded point execution to an agent event of a setting page main element; the set attribute adding module 2 is used for adding a set attribute to an attribute list of the document object element of the point to be buried; and the buried point execution module 3 responds to the trigger of the setting event on the setting page and executes corresponding buried point operation on the document object element with the setting attribute. The invention has no invasion to the logic part of the service agent and UI display and interaction; the compatibility to the browser is good, the browser does not depend on any frame, and the universality is strong; the development and maintenance costs are low.
From a hardware level, the present application provides an embodiment of an electronic device for implementing all or part of contents in a buried point execution method based on an event broker, where the electronic device specifically includes the following contents:
fig. 4 is a schematic block diagram of a system configuration of an electronic device 9600 according to an embodiment of the present application. As shown in fig. 4, the electronic device 9600 can include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this fig. 4 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.
In one embodiment, the event agent based buried point execution method functionality may be integrated into a central processor. Wherein the central processor may be configured to control:
s1, adding the setting event triggering the execution of the buried point to the proxy event of the main element of the setting page;
s2, adding a set attribute to the attribute list of the document object element of the point to be buried;
and S3, responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute.
As can be seen from the above description, the electronic device provided in the embodiment of the present application is non-intrusive to the logic portion and UI display and interaction of the service broker; the compatibility to the browser is good, the browser does not depend on any frame, and the universality is strong; the development and maintenance costs are low.
In another embodiment, the event agent-based embedded point executing node may be configured separately from the central processor 9100, for example, the event agent-based embedded point executing node may be configured as a chip connected to the central processor 9100, and the event agent-based embedded point executing method function is implemented by the control of the central processor.
As shown in fig. 4, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 also does not necessarily include all of the components shown in fig. 4; further, the electronic device 9600 may further include components not shown in fig. 4, which may be referred to in the art.
As shown in fig. 4, a central processor 9100, sometimes referred to as a controller or operational control, can include a microprocessor or other processor device and/or logic device, which central processor 9100 receives input and controls the operation of the various components of the electronic device 9600.
The memory 9140 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 9100 can execute the program stored in the memory 9140 to realize information storage or processing, or the like.
The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. Power supply 9170 is used to provide power to electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, an LCD display, but is not limited thereto.
The memory 9140 can be a solid state memory, e.g., Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 9140 could also be some other type of device. Memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 being used for storing application programs and function programs or for executing a flow of operations of the electronic device 9600 by the central processor 9100.
The memory 9140 can also include a data store 9143, the data store 9143 being used to store data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers for the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, contact book applications, etc.).
The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. The communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as in the case of a conventional mobile communication terminal.
Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby implementing ordinary telecommunications functions. The audio processor 9130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100, thereby enabling recording locally through the microphone 9132 and enabling locally stored sounds to be played through the speaker 9131.
An embodiment of the present application further provides a computer-readable storage medium capable of implementing all the steps in the event-agent-based embedded point execution method in the foregoing embodiment, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program implements all the steps of the event-agent-based embedded point execution method in the foregoing embodiment, where the execution subject is a server or a client, for example, when the processor executes the computer program, the processor implements the following steps:
s1, adding the setting event triggering the execution of the buried point to the proxy event of the main element of the setting page;
s2, adding a set attribute to the attribute list of the document object element of the point to be buried;
and S3, responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute.
From the above description, it can be seen that the computer-readable storage medium provided in the embodiments of the present application is non-intrusive to the logic portion and UI presentation and interaction of the service broker; the compatibility to the browser is good, the browser does not depend on any frame, and the universality is strong; the development and maintenance costs are low.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (nodes), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The principle and the implementation mode of the invention are explained by applying specific embodiments in the invention, and the description of the embodiments is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (12)
1. A buried point execution method based on an event agent is characterized by comprising the following steps:
adding a setting event triggering the execution of the embedded point to an agent event of a setting page main body element;
adding a set attribute to an attribute list of the document object element to be buried;
and responding to the trigger of the setting event on the setting page, and executing corresponding buried point operation on the document object element with the setting attribute.
2. The event broker-based embedded point execution method according to claim 1, further comprising:
and acquiring and defining a page as the setting page.
3. The event broker-based embedded point execution method according to claim 1, further comprising:
and determining a set event for triggering the execution of the buried point.
4. The event broker-based embedded point execution method of claim 1, wherein setting attribute values of the attributes comprises:
calling page information, calling element name information, calling element level information, calling url information, browser version information and kernel information.
5. The event broker-based embedded point execution method according to claim 1, further comprising:
and acquiring the main body element of the setting page.
6. An event agent-based embedded point execution device, comprising:
the proxy event adding module is used for adding a set event triggering the execution of the embedded point into a proxy event of a set page main element;
the set attribute adding module is used for adding a set attribute to an attribute list of the document object element of the point to be buried;
and the buried point execution module responds to the trigger of the setting event on the setting page and executes corresponding buried point operation on the document object element with the setting attribute.
7. The event broker based embedded point executing device according to claim 6, further comprising:
and the setting page definition module acquires and defines a page as the setting page.
8. The event broker based embedded point executing device according to claim 6, further comprising:
and the setting event determining module is used for determining the setting event executed by the trigger buried point.
9. The event broker-based embedded point executing device according to claim 6, wherein the setting of the attribute value of the attribute comprises:
calling page information, calling element name information, calling element level information, calling url information, browser version information and kernel information.
10. The event broker based embedded point executing device according to claim 6, further comprising:
and the main element acquisition module is used for acquiring the main elements of the set page.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the event agent based buried point execution method of any one of claims 1 to 5 when executing the program.
12. A computer-readable storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the event broker based sweet spot execution method of any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110929785.0A CN113626158A (en) | 2021-08-13 | 2021-08-13 | Event agent-based embedded point execution method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110929785.0A CN113626158A (en) | 2021-08-13 | 2021-08-13 | Event agent-based embedded point execution method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113626158A true CN113626158A (en) | 2021-11-09 |
Family
ID=78385284
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110929785.0A Pending CN113626158A (en) | 2021-08-13 | 2021-08-13 | Event agent-based embedded point execution method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113626158A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115033825A (en) * | 2022-06-21 | 2022-09-09 | 北京达佳互联信息技术有限公司 | Page data processing method, device, equipment and medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109960633A (en) * | 2019-03-28 | 2019-07-02 | 深圳市跃动运营科技有限公司 | A kind of data visualization buries point methods, storage medium and intelligent terminal |
| CN111046317A (en) * | 2019-12-27 | 2020-04-21 | 北京奇艺世纪科技有限公司 | Page data acquisition method, device, equipment and computer readable storage medium |
| CN112527414A (en) * | 2020-12-23 | 2021-03-19 | 平安普惠企业管理有限公司 | Front-end-based data processing method, device, equipment and storage medium |
-
2021
- 2021-08-13 CN CN202110929785.0A patent/CN113626158A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109960633A (en) * | 2019-03-28 | 2019-07-02 | 深圳市跃动运营科技有限公司 | A kind of data visualization buries point methods, storage medium and intelligent terminal |
| CN111046317A (en) * | 2019-12-27 | 2020-04-21 | 北京奇艺世纪科技有限公司 | Page data acquisition method, device, equipment and computer readable storage medium |
| CN112527414A (en) * | 2020-12-23 | 2021-03-19 | 平安普惠企业管理有限公司 | Front-end-based data processing method, device, equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115033825A (en) * | 2022-06-21 | 2022-09-09 | 北京达佳互联信息技术有限公司 | Page data processing method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9141611B2 (en) | Aggregated web analytics request systems and methods | |
| CN103150513B (en) | The method of the implantation information in interception application program and device | |
| US20200357007A1 (en) | Page data acquisition method, apparatus, server, electronic device and computer readable medium | |
| CN109800135B (en) | Information processing method and terminal | |
| CN109684571B (en) | Data acquisition method and device and storage medium | |
| CN111813629A (en) | Method, device and equipment for generating monitoring data of Web page | |
| CN113934913A (en) | Data capture method and device, storage medium and electronic equipment | |
| CN111949522A (en) | User interface automatic testing method and device | |
| CN104731869A (en) | Page display method and device | |
| CN111177519A (en) | Webpage content acquisition method and device, storage medium and equipment | |
| CN111177623A (en) | Information processing method and device | |
| CN110825600B (en) | Page information processing method, server and page display device | |
| CN102387174A (en) | Micro-piece for automatically upgrading information of social network site and method thereof | |
| CN113626158A (en) | Event agent-based embedded point execution method and device | |
| CN103488508A (en) | Browser working method, browser and terminal equipment | |
| CN112307386A (en) | Information monitoring method, system, electronic device and computer readable storage medium | |
| CN114816637B (en) | Application display method, device and system embedded in applet | |
| CN111382039A (en) | Method, device, electronic equipment and storage medium for reporting user behavior event | |
| CN115563423A (en) | Data acquisition method and device, computer equipment and storage medium | |
| CN112671615B (en) | Method, system and storage medium for collecting front-end user operation behavior data | |
| CN111158678B (en) | Video playing method and device, client device and electronic device | |
| CN112799927A (en) | Operation behavior information acquisition method and device for front-end user | |
| CN107704491B (en) | Message processing method and device | |
| CN112287261A (en) | Resource loading method and electronic equipment | |
| CN111767447A (en) | Method and device for determining user traffic path |
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 |