CN112988291B - Page event management method and device, computer readable medium and electronic equipment - Google Patents
Page event management method and device, computer readable medium and electronic equipment Download PDFInfo
- Publication number
- CN112988291B CN112988291B CN201911301779.XA CN201911301779A CN112988291B CN 112988291 B CN112988291 B CN 112988291B CN 201911301779 A CN201911301779 A CN 201911301779A CN 112988291 B CN112988291 B CN 112988291B
- Authority
- CN
- China
- Prior art keywords
- event
- page
- attribute
- target page
- state value
- 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
- 238000007726 management method Methods 0.000 title abstract description 35
- 238000000034 method Methods 0.000 claims abstract description 41
- 230000004044 response Effects 0.000 claims description 109
- 238000004590 computer program Methods 0.000 claims description 8
- 238000010586 diagram Methods 0.000 description 30
- 230000001960 triggered effect Effects 0.000 description 12
- 230000008569 process Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 230000006854 communication Effects 0.000 description 7
- 230000002452 interceptive effect Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
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/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
The embodiment of the application provides a page event management method, a page event management device, a computer readable medium and electronic equipment. The matching method comprises the following steps: when a target page is to be displayed, determining a first event focused by the target page; acquiring page event attributes of the first event in the target page; acquiring a recorded event attribute of the first event in an event record; and responding to the first event focused by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page. The technical scheme of the embodiment of the application can improve the flexibility of managing the page event, in particular to the cross-page event.
Description
Technical Field
The present application relates to the field of computers and communications technologies, and in particular, to a method and apparatus for managing page events, a computer readable medium, and an electronic device.
Background
In a page event management scenario, such as a cross-page event management scenario, event management is generally implemented through a proxy mode or a notification center mode, where a proxy party and a proxy party manage page events through a protocol. However, how to improve the flexibility of managing page events, especially cross-page events, is a technical problem to be solved.
Disclosure of Invention
The embodiment of the application provides a page event management method, a page event management device, a computer readable medium and electronic equipment, and further can improve the page event management accuracy at least to a certain extent.
Other features and advantages of the application will be apparent from the following detailed description, or may be learned by the practice of the application.
According to an aspect of an embodiment of the present application, there is provided a page event management method, including: when a target page is to be displayed, determining a first event focused by the target page; acquiring page event attributes of the first event in the target page; acquiring a recorded event attribute of the first event in an event record; and responding to the first event focused by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page.
According to an aspect of an embodiment of the present application, there is provided a page event management apparatus including: the determining unit is used for determining a first event focused by the target page when the target page is to be displayed; a first acquisition unit, configured to acquire a page event attribute of the first event in the target page; a second acquiring unit, configured to acquire a record event attribute of the first event in an event record; and the response unit is used for responding to the first event focused by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page.
In some embodiments of the present application, based on the foregoing solution, the target page includes a trigger button for triggering the second event, and the apparatus further includes: the generation unit is used for responding to the second event triggered by the user through the trigger button after the target page is displayed, and generating a recorded event attribute for the second event; and the storage unit is used for storing the recorded event attribute of the second event in the event record.
In some embodiments of the application, the event records are recorded by an event management center based on the foregoing scheme.
In some embodiments of the present application, based on the foregoing, the page event attribute includes a creation time of the target page, the record event attribute includes a first response reference time of the first event, and the response unit is configured to: detecting whether the creation time of the target page is earlier than a first response reference time of the first event; and if the creation time of the target page is earlier than the first response reference time of the first event, responding to the first event focused on by the target page.
In some embodiments of the application, based on the foregoing scheme, the response unit is configured to: after responding to the first event focused on the target page, updating the first response reference time of the first event in the recorded event attribute to the creation time of the target page.
In some embodiments of the application, based on the foregoing, the determining unit is configured to: before determining a first event focused by a target page, when the first event focused by the target page does not exist in the target page, updating the first response reference time of the first event in the recorded event attribute to the creation time of the target page.
In some embodiments of the present application, based on the foregoing, the page event attribute includes a second response reference time of the first event, the record event attribute includes a trigger time of the first event, and the response unit is configured to: detecting whether the second response reference time of the first event is earlier than the triggering time of the first event; and if the second response reference time of the first event is earlier than the triggering time of the first event, responding to the first event focused on the target page.
In some embodiments of the application, based on the foregoing scheme, the response unit is configured to: after responding to the first event focused by the target page, updating the second response reference time of the first event in the page event attribute to the triggering time of the first event.
In some embodiments of the present application, based on the foregoing, the page event attribute includes a first state value of the first event, the record event attribute includes a second state value of the first event, and the response unit is configured to: and updating the first state value into a second state value to obtain a new first state value.
In some embodiments of the present application, based on the foregoing, the page event attribute includes a first state value of the first event, the record event attribute includes a second state value of the first event, and the response unit is configured to: detecting whether the first state value is consistent with the second state value; and if the first state value is inconsistent with the second state value, updating the first state value into the second state value to obtain a new first state value.
According to an aspect of the embodiments of the present application, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a page event management method as described in the above embodiments.
According to an aspect of an embodiment of the present application, there is provided an electronic apparatus including: one or more processors; and a storage means for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the page event management method as described in the above embodiments.
In some embodiments of the present application, when a target page is to be displayed, a response is made to a first event focused on the target page by acquiring a page event attribute of the first event focused on the target page and a record event attribute in an event record, according to the page event attribute and the record event attribute of the first event. The method and the device have the advantages that the recorded event attribute of the first event focused by the target page is recorded in the event record, and the first event focused by the target page is correspondingly responded by acquiring the recorded event attribute of the first event from the event record and referring to the page event attribute acquired in the target page, so that the management of the page event is simplified, and the flexibility of managing the page event, particularly the cross-page event, can be improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application. It is evident that the drawings in the following description are only some embodiments of the present application and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art. In the drawings:
FIG. 1 shows an implementation environment diagram of a solution according to an embodiment of the application;
FIG. 2 illustrates an application diagram of a page event management method according to one embodiment of the application;
FIG. 3 illustrates a flow diagram of a page event management method according to one embodiment of the application;
FIG. 4 shows a flow chart of a method after a target page is presented, according to one embodiment of the application;
FIG. 5 illustrates a communication diagram of an event management center according to one embodiment of the application;
FIG. 6 illustrates a flow diagram for an implementation of an event management center according to one embodiment of the application;
FIG. 7 illustrates an implementation element diagram of an event management center according to one embodiment of the application;
FIG. 8 shows a detailed flow diagram of responding to a first event of interest to a target page, according to one embodiment of the application;
FIG. 9 shows a detailed flow diagram of responding to a first event of interest to a target page, according to one embodiment of the application;
FIG. 10 shows a detailed flow diagram of responding to a first event of interest to a target page, according to one embodiment of the application;
FIG. 11 illustrates a business flow diagram for implementing page event management according to one embodiment of the application;
FIG. 12 shows a block diagram of a page event management device according to one embodiment of the application;
Fig. 13 shows a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the application may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
Fig. 1 shows an implementation environment diagram of a technical solution according to an embodiment of the present application.
As shown in fig. 1, an implementation environment of the technical solution of the embodiment of the present application may include a terminal device. For example, any one of the smart phone 101, tablet 102, touch display 103, and portable computer 104 shown in fig. 1 is included, but of course, other electronic devices with touch or non-touch display functions, etc. may be used.
In one embodiment of the present application, a user may implement the technical solution of the embodiment of the present application using a smart phone with a touch or non-touch display function, such as smart phone 101 shown in fig. 1. Specifically, the screen of the smart phone can display a page, and an event which can be displayed or triggered is arranged in the page displayed by the screen.
In order to provide a more visual understanding of the present application to those skilled in the art, a specific example will be described herein.
In a specific implementation of an embodiment, the technical solution of the present application may be implemented with reference to the page shown in fig. 2, and as shown in fig. 2, an application schematic diagram of a page event management method according to an embodiment of the present application is shown.
As shown in fig. 2, the change situation of the event information in the display page after the operation instruction of the cross-page is shown, specifically, if some operations are performed on the display page by the user a, after the user a rolls back to the personal page, the whole page needs to be refreshed to ensure that the information display is updated in real time, these operations are trigger factors of the event, and if these operations are not performed on the display page, when the user a returns to the personal page, the whole interface does not need to be refreshed. The flow of the simple application is as follows:
User a can see the number of "praise" and "play" of each video in his own list of videos that the personal page praise, and if this video is user a's own video, the privacy status ("privacy" event)
In the effect level of event information display in the event management process, after clicking the 2 nd video in the private page 201 (at this time, the number of "praise" in the private page is 80), the private page 201 jumps to the play page 202 of the 2 nd video, and in the play process, the user performs praise operation through the lower right corner of the play page 202.
Meanwhile, if the video is just the video issued by the user a, the user a can also perform editing operations including modifying the privacy or public state of the video, and deleting the video (editing-related events are not shown in fig. 2).
After the user performs the praise operation, the user clicks the back button on the upper left corner of the playing page, at this time, the playing page 202 returns to the private page 203 of the user, and at this time, the information of the private page needs to be refreshed in whole or in part to ensure that the presentation of the page event information is normal. Such as "praise" number (at this time the number of "praise" in the private page is 81), play number, private or public status, deletion status of video, etc.
What has been described above is the simplest scenario spanning two consecutive pages, and in practical applications we will often encounter event management scenarios for complex links. For example, the user a may first enter the attention list of the private page, enter the private page of the user B in the attention list, then enter the playing page of a certain video from the private page of the user B, perform related operations (like or cancel like) on the playing page, and return to the private page of the user a itself, if the video that has been operated on the playing page is just shown in the video list that has been like by the user a itself, the entire page needs to be refreshed by the stand-up horse. To ensure that event change information caused by the operation of the user can be validated in real time.
The implementation details of the technical scheme of the embodiment of the application are described below:
According to a first aspect of the present disclosure, a page event management method is provided.
Referring to fig. 3, a flowchart of a page event management method according to an embodiment of the present application is shown, which may be performed by a device having a calculation processing function, such as the smart phone 101 shown in fig. 1, or the tablet 102 shown in fig. 1. As shown in fig. 3, the page event management method at least includes steps 310 to 370:
Step 310, when the target page is to be displayed, determining a first event focused on by the target page.
Step 330, obtaining the page event attribute of the first event in the target page.
Step 350, obtaining a recorded event attribute of the first event in the event record.
And step 370, responding to the first event focused on by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page.
In one embodiment of the present application, after the page is presented, a page event management method as shown in fig. 4 may also be implemented.
Referring to FIG. 4, a flow diagram of a method after a target page is presented is shown, according to one embodiment of the application. Steps 380 to 390 may be specifically included:
step 380, in response to the user triggering the second event through the trigger button, generating a recorded event attribute for the second event.
Step 390, saving the recorded event attribute of the second event in the event record.
In one embodiment of the present application, the event records described above may be recorded by an event management center.
In order to make those skilled in the art more aware of the event management center disclosed in the present application, the following details of the technical solution of the present application will be described around the event management center:
Referring to fig. 5, a communication diagram of an event management center according to one embodiment of the present application is shown. As shown in fig. 5, the disclosed page event management method will be implemented based on two parts, namely a base page presentation module 501 and an event management center 502.
Specifically, the basic page display module is mainly used for managing each link of a page in the whole life cycle, including page creation, page display, page event response, page interaction and page closing. In the present application, the event management center may then be the ability to provide the page with query triggering events and record triggering events. In addition, for the base page presentation module, in order to ensure that the results of the query triggering event are more accurate when multi-level pages are repeatedly entered, the page presentation module is also required to have the capability of recording and refreshing the time points to the event management center.
In a specific implementation of an embodiment, the implementation of the page event management method disclosed by the application through the basic page display module and the event management center can be implemented through a flow shown in fig. 6.
Referring to fig. 6, a flow diagram of an implementation of an event management center is shown, according to one embodiment of the application. Specifically, the method includes a flow 601, a flow 602, and a flow 603:
The process 601 mainly implements the process of creating a page, and the main content is to record the creation time, and register the type of the event of interest of the page based on the business situation, such as "like" event, "delete" event, and so on.
The process 602 mainly realizes the process of displaying the page, specifically, if the page has an event of interest, the page queries the event management center, and the event management center can update the event attribute of the event record of the event management center after the event response is performed after the event trigger record is queried. The recorded event attributes of the events of the event management center may also be updated if there are no events of interest or no triggers are queried.
The process 603 mainly implements a process during the interaction of the user, specifically, if the user triggers an event (such as "like" event, "delete" event, etc.), the trigger event record of the events is recorded in the event management center.
Each page has an implementation of a base class, e.g., the base class of all pages in the IOS system is UI View Controller. In the present application, among all the flow nodes shown in fig. 6, other flow nodes may be implemented in the base class, except for 3 flow nodes of "set event type of interest", "response event", and "event trigger record".
In a specific implementation of an embodiment, implementing the page event management method disclosed in the present application may be implemented by implementation elements as shown in fig. 7.
Referring to FIG. 7, an implementation element diagram of an event management center is shown, according to one embodiment of the application. Specifically, the system includes a basic page controller 701, a sub-page controller 702, and an event management center 703:
basic page controller 701: the underlying page controllers, inherited from UI View Controller, typically have their own page controller base class per App, which in this application can be denoted Base View Controller, with 2 attributes, namely the event type of interest, and the time of page creation, as well as three method protocols including page creation complete, page display, and response events.
Sub-page controller 702: the specific business page controllers inherited at Base View Controller, such as the private page and the play page shown in fig. 2, are all representations of specific content carried by the sub-page controllers. Since the sub-page controller inherits Base View Controller's capabilities, only 3 flow nodes as shown in FIG. 6, "set event type of interest", "respond to event", and "event trigger record" need be implemented
Event management center 703: in the application, 2 attributes, namely the creation time point of the last display page, and an event information storage dictionary (the dictionary is needed by internal logic implementation and does not need external exposure), and also can comprise external capability of triggering event and inquiring whether the event is triggered.
The following will describe in detail the implementation steps as shown in fig. 3:
Referring to fig. 3, in step 310, when a target page is to be presented, a first event of interest to the target page is determined.
In one embodiment of the present application, before determining the first event that the target page focuses on, it may be detected whether there is a first event focused on in the target page, and if it is detected that there is a first event focused on in the target page, a subsequent step is entered.
With continued reference to FIG. 3, in step 330, a page event attribute of the first event in the target page is obtained.
In one embodiment of the present application, the page event attribute of the first event in the target page may refer to a creation time of the target page. For example, in fig. 2, the private page 201 is created 11 minutes 11 seconds 11 on 11.11.2019, then the page event attribute of the "like" event of interest to the private page 201 may be: "Page creation time: 11 minutes 11 seconds at 11.11.11.2019, it should be noted that each page may have a page creation time that is fixed.
In one embodiment of the present application, the page event attribute of the first event in the target page may further refer to a second response reference time of the first event. Specifically, there may be a second response reference time for each event in the page. It should be noted that, when the page is created, if there is an event of interest in the page, the initial second response reference time corresponding to the event of interest in the page may be the creation time of the page, for example, in fig. 2, the private page 201 is created 11 minutes 11 seconds at 11 months 11 days 11 in 2019, and then the page event attribute of the "like" event of interest of the private page 201 may be: "second response reference time: 11 minutes 11 seconds 11 months 11 days 11 hours 11 years 2019. It should also be noted that the second response reference time for each event may be modified in subsequent operations.
In one embodiment of the present application, the page event attribute of the first event in the target page may refer to a first state value of the first event. Specifically, for example, in FIG. 2, the number of praise "80" shown in the personal page 201 is the first state value of the "praise" event.
With continued reference to FIG. 3, in step 350, a record event attribute of the first event in an event record is obtained.
In one embodiment of the present application, the recorded event attribute of the first event in the event record may refer to a trigger time of the first event. For example, in fig. 2, the "praise" event in the private page 202 is triggered by the user clicking 13 minutes 13 seconds at 13 days 13 of 2019, and then the trigger time of the "praise" event may be: "13 minutes 13 seconds at 13 days 13 months 13 days 13 2019", the recorded event attribute of the "praise" event recorded in the event record may be: "trigger time: 13 minutes 13 seconds 13 days 13 months 13 days 13 2019.
In addition, the trigger time of the first event may also be the creation time of the page shown when the first event is triggered, for example, in fig. 2, the private page 202 is created 12 minutes and 12 seconds on 12 days of 12 months of 2019, then after the "praise" event is triggered in the private page 202, the creation time "2019, 12 months of 12 days, 12 minutes and 12 seconds" of the private page 202 may be taken as the trigger time of the "praise" event, so the recorded event attribute of the "praise" event recorded in the event record may be: "trigger time: 12 minutes and 12 seconds on 12 months and 12 days of 2019.
It should be noted that there may be one trigger time in the event record for each event in the page, and the trigger time of the event in the event record is unchanged.
In one embodiment of the present application, the recorded event attribute of the first event in the event record may also refer to a first response reference time of the first event. Specifically, in the event record, each event may have a first response reference time. It should be noted that each time an event is triggered, its trigger time may be taken as an initial first response reference time for the event. For example, in fig. 2, the trigger time of the "praise" event in the private page 202 is "12 minutes 12 seconds on 12 days 12 months of 2019", and then the initial first response reference time of the "praise" event in the event record may be: "first response reference time: 12 minutes and 12 seconds on 12 months and 12 days of 2019. It should be noted that in the subsequent operations, the first response reference time corresponding to each event may be changed in the event record.
In one embodiment of the present application, the recorded event attribute of the first event in the event record may also refer to a second state value of the first event. Specifically, for example, in FIG. 2, after triggering the "like" event shown in the personal page 202, the like number "81" is the second state value of the "like" event in the event record.
With continued reference to FIG. 3, in step 370, the first event of interest to the target page is responded to in accordance with the page event attribute and the record event attribute of the first event to reveal the target page.
In the present application, step 370 may be implemented by the following embodiments:
embodiment 1,
In this embodiment, the page event attribute includes a creation time of the target page, the record event attribute includes a first response reference time of the first event, and responding to the first event focused on the target page according to the page event attribute and the record event attribute of the first event may be implemented through steps shown in fig. 8.
Referring to FIG. 8, a detailed flow diagram illustrating a response to a first event of interest to a target page is shown, according to one embodiment of the application. Specifically, steps 371 to 372 may be included:
Step 371 detects whether the creation time of the target page is earlier than a first response reference time of the first event.
If the creation time of the target page is earlier than the first response reference time of the first event, then a response is made to the first event of interest to the target page, step 372.
For example, the creation time of the target page is "2019, 11 minutes, 11 seconds", and the first response reference time of the first event is "2019, 12 minutes, 12 seconds", and by detecting, the creation time of the target page is earlier than the first response reference time of the first event, and at this time, the first event that is focused on by the target page needs to be responded.
In a specific implementation of the first embodiment, the page event attribute further includes a first state value of the first event, the record event attribute further includes a second state value of the first event, and the responding to the first event focused on the target page may be updating the first state value to the second state value, so as to obtain a new first state value.
For example, if the first event is a "like" event, the first state value of the "like" event is: "80 times", the second state value of the "like" event is: "81 times". Responding to the first event focused on by the target page, namely updating the first state value of the 'praise' event into: "81 times".
In a specific implementation of the first embodiment, after responding to the first event focused on the target page, the first response reference time of the first event in the recorded event attribute may be updated to be the creation time of the target page.
For example, the first response reference time of the first event in the recorded event attribute is "12 minutes and 12 seconds on 12 th 2019", the creation time of the target page is "11 minutes and 11 seconds on 11 th 2019, after responding to the first event of interest to the target page, the first response reference time of the first event in the recorded event attribute may be updated to" 11 minutes 11 seconds 11 on 11 days 11 months 2019 ".
In a specific implementation of the first embodiment, before the determining the first event focused on by the target page in step 310, the method may further include: if the first event of interest is detected to be absent in the target page, the first response reference time of the first event in the recorded event attribute can be updated to be the creation time of the target page.
The advantages of this embodiment are: by detecting whether the creation time of the target page is earlier than the first response reference time of the first event recorded in the event record to respond to the first event focused on by the target page, the response to the page event can be realized clearly, simply and flexibly.
Embodiment II,
In this embodiment, the page event attribute includes a second response reference time of the first event, the record event attribute includes a trigger time of the first event, and responding to the first event focused on the target page according to the page event attribute and the record event attribute of the first event may be implemented through steps shown in fig. 9.
Referring to FIG. 9, a detailed flow diagram of responding to a first event of interest to a target page is shown, according to one embodiment of the application. Specifically steps 373 to 374 may be included:
in step 373, it is detected whether the second response reference time of the first event is earlier than the trigger time of the first event.
If the second response reference time of the first event is earlier than the trigger time of the first event, then a response is made to the first event of interest to the target page, step 374.
In a specific implementation of the second embodiment, the page event attribute further includes a first state value of the first event, the record event attribute further includes a second state value of the first event, and the responding to the first event focused on the target page may be updating the first state value to the second state value, so as to obtain a new first state value.
In a specific implementation of the second embodiment, after responding to the first event focused on the target page, the second response reference time of the first event in the page event attribute may be updated to be the trigger time of the first event.
In a specific implementation of the second embodiment, after responding to the first event focused on the target page, the second response reference time of the first event in the page event attribute may also be updated to be the response time of responding to the first event focused on the target page.
Third embodiment,
In this embodiment, the page event attribute includes a first state value of the first event, the record event attribute includes a second state value of the first event, and responding to the first event focused on the target page according to the page event attribute and the record event attribute of the first event may be implemented through the steps shown in fig. 10.
Referring to FIG. 10, a detailed flow diagram of responding to a first event of interest to a target page is shown, according to one embodiment of the application. Specifically, steps 375 to 376 may be included:
Step 375, detecting whether the first state value is consistent with the second state value.
Step 376, if the first state value is inconsistent with the second state value, updating the first state value to the second state value to obtain a new first state value.
In order to make the present application more understandable to those skilled in the art, the present application will be described below with reference to the first embodiment, and a specific service scenario:
Referring to FIG. 11, a business flow diagram for implementing page event management is shown, according to one embodiment of the present application.
In this business scenario, the user jumps from page 1 to page 2, from page 2 to page 3, from page 3 to page 4 in that order. And then returns to the original path. Wherein, the event a1 of interest exists in the page 1, the event a2 of interest exists in the page 2, the event a2 of interest does not exist in the page 3 and the page 4 do not exist in any event of interest, but in the page 3, the event a1 can be triggered through corresponding operation, the event a2 can be triggered through corresponding operation, and when the page 2 and the page 1 are redisplayed, the response needs to be respectively carried out for the event a2 and the event a1 of interest. The specific implementation process comprises the following 23 steps:
Step 1: when the page 1 is created and displayed, the creation time t1 of the page 1 is recorded, the concerned event type a1 (t 1 and a1 are both in the page event attribute of the page 1) is registered based on the service condition, meanwhile, the t1 is updated to the event management center, and the creation time of the last displayed page is recorded as t 1.
Step 2: in response to the user's interactive operation, page 2 is created and jumps from page 1 to page 2.
Step 3: similarly to step 1, when the page 2 is displayed, the creation time t2 is recorded, the concerned event type a2 is registered based on the service condition (t 2 and a2 are both in the page event attribute of the page 2), meanwhile, t2 is updated to the event management center, and the creation time of the last displayed page is recorded as t 2.
Step 4: in response to the user's interactive operation, page 3 is created and jumps from page 2 to page 3.
Step 5: similarly to step 1, when page 3 is displayed, the creation time t3 thereof is recorded (there is no event of interest in page 3, so there is no a3 or a1, a 2), while t3 is updated to the event management center, and the creation time t3 is the last page presented.
Step 6: in response to the user's interactive operation at page 3, event a1 is triggered.
Step 7: the trigger event record of the event a1 is recorded in the event management center and stored in a dictionary manner, the state value of the event a1 is a1, and the first response reference time of the event a1 is t3 (because the creation time of the event trigger page is t 3).
Step 8: in response to the user's interactive operation, page 4 is created and jumps from page 3 to page 4.
Step 9: similarly to step 5, when page 4 is displayed, the creation time t4 thereof is recorded (there is no event of interest in page 4, so there is no a4 or a1, a 2), while t4 is updated to the event management center, and the creation time t4 is the last page presented.
Step 10: in response to the user interaction at page 4, trigger event a2
Step 11: the trigger event record of the event a2 is recorded in the event management center and stored in a dictionary manner, the state value of the event a2 is a2, and the first response reference time of the event a2 is t4 (because the creation time of the event trigger page is t 4).
Step 12: in response to the user's interactive operation, page 4 is jumped back to page 3.
Step 13: when the page 3 is redisplayed, since no event is concerned, the last display page creation time of the event management center is directly updated to t3, and the first response reference time of all events in the dictionary is updated to t3.
Step 14: in response to the user's interactive operation, page 3 is jumped back to page 2.
Step 15: when the page 2 is redisplayed, since there is an event a2 of interest, it is necessary to detect whether a2 is overdriven or not to the event management center.
Step 16: because the first response reference time corresponding to the event a2 in the dictionary stored in the event management center is t3, the creation time t2 of the page 2 is earlier than the first response reference time t3 corresponding to the event a2, so that the triggering result of the event a2 is returned
Step 17: the page 2 responds to the event a2 concerned by the event management center based on the trigger result of the event a2 returned by the event management center.
Step 18: the last presentation page creation time of the event management center is updated to be t2, and the first response reference time of all events in the dictionary is updated to be t2.
Step 19: in response to the user's interactive operation, page 2 is jumped back to page 1.
Step 20: when page 1 is redisplayed, similar to step 15, it is necessary to detect whether a1 has been triggered to the event management center because there is an event of interest a1.
Step 21: similar to step 16, since the first response reference time corresponding to the event a1 is t2 in the dictionary stored in the event management center, the creation time t1 of the page 1 is earlier than the first response reference time t2 corresponding to the event a1, so the trigger result of the event a1 is returned.
Step 22: similar to step 17, page 1 responds to event a1 of its interest based on the trigger result of event a1 returned by the event management center.
Step 23: similar to step 18, the last presented page creation time of the update event management center is t1, and the dictionary can be emptied because only 1 root page of page 1 remains in the entire page link at this time.
In the technical scheme of the embodiment of the application, the first event focused on the target page is responded by acquiring the page event attribute of the first event focused on the target page and the recorded event attribute in the event record and according to the page event attribute and the recorded event attribute of the first event. Because the recorded event attribute of the first event focused by the target page is recorded in the event record, the application can make the management of the page event simpler by acquiring the recorded event attribute of the first event from the event record and making a corresponding response to the first event focused by the target page by referring to the page event attribute acquired in the target page, thereby improving the flexibility of managing the page event, in particular the cross-page event.
The following describes an embodiment of the apparatus of the present application, which may be used to perform the page event management method in the above embodiment of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the page event management method described above.
Fig. 12 shows a block diagram of a page event management apparatus according to an embodiment of the present application.
Referring to fig. 12, a page event management apparatus 1200 according to an embodiment of the present application includes: a determination unit 1201, a first acquisition unit 1202, a second acquisition unit 1203, and a response unit 1204.
Wherein, the determining unit 1201 is configured to determine, when the target page is to be displayed, a first event focused on the target page; a first acquiring unit 1202 configured to acquire a page event attribute of the first event in the target page; a second obtaining unit 1203 configured to obtain a record event attribute of the first event in an event record; and a response unit 1204, configured to respond to the first event focused on by the target page according to the page event attribute and the record event attribute of the first event, so as to display the target page.
In some embodiments of the application, the event records are recorded by an event management center based on the foregoing scheme.
In some embodiments of the present application, based on the foregoing solution, the target page includes a trigger button for triggering the second event, and the apparatus further includes: the generation unit is used for responding to the second event triggered by the user through the trigger button after the target page is displayed, and generating a recorded event attribute for the second event; and the storage unit is used for storing the recorded event attribute of the second event in the event record.
In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a creation time of the target page, the recording event attribute includes a first response reference time of the first event, and the response unit 1204 is configured to: detecting whether the creation time of the target page is earlier than a first response reference time of the first event; and if the creation time of the target page is earlier than the first response reference time of the first event, responding to the first event focused on by the target page.
In some embodiments of the present application, based on the foregoing scheme, the response unit 1204 is configured to: after responding to the first event focused on the target page, updating the first response reference time of the first event in the recorded event attribute to the creation time of the target page.
In some embodiments of the present application, based on the foregoing scheme, the determining unit 1204 is configured to: before determining a first event focused by a target page, when the first event focused by the target page does not exist in the target page, updating the first response reference time of the first event in the recorded event attribute to the creation time of the target page.
In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a second response reference time of the first event, the record event attribute includes a trigger time of the first event, and the response unit 1204 is configured to: detecting whether the second response reference time of the first event is earlier than the triggering time of the first event; and if the second response reference time of the first event is earlier than the triggering time of the first event, responding to the first event focused on the target page.
In some embodiments of the present application, based on the foregoing scheme, the response unit 1204 is configured to: after responding to the first event focused by the target page, updating the second response reference time of the first event in the page event attribute to the triggering time of the first event.
In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a first state value of the first event, the record event attribute includes a second state value of the first event, and the response unit 1204 is configured to: and updating the first state value into a second state value to obtain a new first state value.
In some embodiments of the present application, based on the foregoing solution, the page event attribute includes a first state value of the first event, the record event attribute includes a second state value of the first event, and the response unit 1204 is configured to: detecting whether the first state value is consistent with the second state value; and if the first state value is inconsistent with the second state value, updating the first state value into the second state value to obtain a new first state value.
Fig. 13 shows a schematic diagram of a computer system suitable for use in implementing an embodiment of the application.
It should be noted that, the computer system 1300 of the electronic device shown in fig. 13 is only an example, and should not impose any limitation on the functions and the application scope of the embodiments of the present application.
As shown in fig. 13, the computer system 1300 includes a central processing unit (Central Processing Unit, CPU) 1301, which can perform various appropriate actions and processes according to a program stored in a Read-Only Memory (ROM) 1302 or a program loaded from a storage portion 1308 into a random access Memory (Random Access Memory, RAM) 1303, for example, performing the method described in the above embodiment. In the RAM 1303, various programs and data required for the system operation are also stored. The CPU 1301, ROM 1302, and RAM 1303 are connected to each other through a bus 1304. An Input/Output (I/O) interface 1305 is also connected to bus 1304.
The following components are connected to the I/O interface 1305: an input section 1306 including a keyboard, a mouse, and the like; an output portion 1307 including a Cathode Ray Tube (CRT), a Liquid crystal display (Liquid CRYSTAL DISPLAY, LCD), and a speaker, etc.; a storage portion 1308 including a hard disk or the like; and a communication section 1309 including a network interface card such as a LAN (Local Area Network ) card, a modem, or the like. The communication section 1309 performs a communication process via a network such as the internet. The drive 1310 is also connected to the I/O interface 1305 as needed. Removable media 1311, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memory, and the like, is installed as needed on drive 1310 so that a computer program read therefrom is installed as needed into storage portion 1308.
In particular, according to embodiments of the present application, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present application include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such embodiments, the computer program may be downloaded and installed from a network via the communication portion 1309 and/or installed from the removable medium 1311. When executed by a Central Processing Unit (CPU) 1301, performs various functions defined in the system of the present application.
It should be noted that, the computer readable medium shown in the embodiments of the present application may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-Only Memory (ROM), an erasable programmable read-Only Memory (Erasable Programmable Read Only Memory, EPROM), a flash Memory, an optical fiber, a portable compact disc read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present application, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. Where each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present application may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer-readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to implement the methods described in the above embodiments.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a touch terminal, or a network device, etc.) to perform the method according to the embodiments of the present application.
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (13)
1. A method of page event management, the method comprising:
when a target page is to be displayed, determining a first event focused by the target page;
acquiring page event attributes of the first event in the target page;
Acquiring a recorded event attribute of the first event in an event record;
responding to the first event focused by the target page according to the page event attribute and the record event attribute of the first event so as to display the target page;
If the page event attribute includes the creation time of the target page, the recording event attribute includes a first response reference time of the first event, and the responding to the first event focused on the target page according to the page event attribute and the recording event attribute of the first event includes: detecting whether the creation time of the target page is earlier than a first response reference time of the first event; if the creation time of the target page is earlier than the first response reference time of the first event, responding to the first event focused on by the target page;
If the page event attribute includes the second response reference time of the first event, the record event attribute includes the trigger time of the first event, and the responding to the first event focused on the target page according to the page event attribute and the record event attribute of the first event includes: detecting whether the second response reference time of the first event is earlier than the triggering time of the first event; and if the second response reference time of the first event is earlier than the triggering time of the first event, responding to the first event focused on the target page.
2. The method of claim 1, wherein the target page includes a trigger button for triggering a second event, and wherein after the target page is displayed, the method further comprises:
Generating a recorded event attribute for the second event in response to the user triggering the second event through the trigger button;
and storing the recorded event attribute of the second event in the event record.
3. The method of claim 1, wherein the event records are recorded by an event management center.
4. The method of claim 1, wherein after responding to the first event of interest for the target page, the method further comprises:
And updating the first response reference time of the first event in the recorded event attribute to the creation time of the target page.
5. The method of claim 1, wherein prior to determining the first event of interest for the target page, the method further comprises:
And when the first event of interest does not exist in the target page, updating the first response reference time of the first event in the recorded event attribute to the creation time of the target page.
6. The method of claim 1, wherein after responding to the first event of interest for the target page, the method further comprises:
and updating the second response reference time of the first event in the page event attribute to be the trigger time of the first event.
7. The method of any one of claims 1 to 6, wherein the page event attribute further comprises a first status value for the first event, the record event attribute further comprises a second status value for the first event,
The responding to the first event focused by the target page according to the page event attribute and the record event attribute of the first event comprises the following steps:
And updating the first state value into a second state value to obtain a new first state value.
8. The method of any one of claims 1 to 6, wherein the page event attribute further comprises a first status value for the first event, the record event attribute further comprises a second status value for the first event,
The responding to the first event focused by the target page according to the page event attribute and the record event attribute of the first event comprises the following steps:
detecting whether the first state value is consistent with the second state value;
And if the first state value is inconsistent with the second state value, updating the first state value into the second state value to obtain a new first state value.
9. A page event management apparatus, the apparatus comprising:
the determining unit is used for determining a first event focused by the target page when the target page is to be displayed;
A first acquisition unit, configured to acquire a page event attribute of the first event in the target page;
A second acquiring unit, configured to acquire a record event attribute of the first event in an event record;
A response unit, configured to respond to the first event focused on by the target page according to the page event attribute and the record event attribute of the first event, so as to display the target page;
wherein if the page event attribute includes the creation time of the target page, the recording event attribute includes a first response reference time of the first event, and the response unit is configured to: detecting whether the creation time of the target page is earlier than a first response reference time of the first event; if the creation time of the target page is earlier than the first response reference time of the first event, responding to the first event focused on by the target page;
Wherein if the page event attribute includes a second response reference time of the first event, the record event attribute includes a trigger time of the first event, and the response unit is configured to: detecting whether the second response reference time of the first event is earlier than the triggering time of the first event; and if the second response reference time of the first event is earlier than the triggering time of the first event, responding to the first event focused on the target page.
10. The apparatus of claim 9, wherein the page event attribute further comprises a first status value for the first event, and wherein the record event attribute further comprises a second status value for the first event; the response unit is further configured to:
And updating the first state value into a second state value to obtain a new first state value.
11. The apparatus of claim 9, wherein the page event attribute further comprises a first status value for the first event, and wherein the record event attribute further comprises a second status value for the first event; the response unit is further configured to:
detecting whether the first state value is consistent with the second state value;
And if the first state value is inconsistent with the second state value, updating the first state value into the second state value to obtain a new first state value.
12. A computer readable medium having stored thereon a computer program comprising executable instructions which, when executed by a processor, implement the method of any of claims 1 to 8.
13. An electronic device, comprising:
A processor; and
A memory for storing executable instructions of the processor;
wherein the processor is arranged to execute the executable instructions to implement the method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911301779.XA CN112988291B (en) | 2019-12-17 | 2019-12-17 | Page event management method and device, computer readable medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911301779.XA CN112988291B (en) | 2019-12-17 | 2019-12-17 | Page event management method and device, computer readable medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112988291A CN112988291A (en) | 2021-06-18 |
| CN112988291B true CN112988291B (en) | 2024-05-03 |
Family
ID=76342250
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911301779.XA Active CN112988291B (en) | 2019-12-17 | 2019-12-17 | Page event management method and device, computer readable medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112988291B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109358794A (en) * | 2018-10-10 | 2019-02-19 | 平安普惠企业管理有限公司 | WEB application program page furbishing method, device, computer equipment and storage medium |
| CN110413913A (en) * | 2019-07-04 | 2019-11-05 | 北京字节跳动网络技术有限公司 | A kind of page furbishing method, device, terminal and storage medium |
-
2019
- 2019-12-17 CN CN201911301779.XA patent/CN112988291B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109358794A (en) * | 2018-10-10 | 2019-02-19 | 平安普惠企业管理有限公司 | WEB application program page furbishing method, device, computer equipment and storage medium |
| CN110413913A (en) * | 2019-07-04 | 2019-11-05 | 北京字节跳动网络技术有限公司 | A kind of page furbishing method, device, terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112988291A (en) | 2021-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11803704B2 (en) | Intelligently updating a collaboration site or template | |
| WO2020253059A1 (en) | Method and apparatus for implementing multi-stage linkage drop-down box, and computer device | |
| US9183072B1 (en) | Error troubleshooting using a correlated knowledge base | |
| US11438227B2 (en) | Iteratively updating a collaboration site or template | |
| CN111190882B (en) | Target template creation method and device, electronic equipment and storage medium | |
| US20150332287A1 (en) | Social customer relationship management opportunity templating | |
| CN104331405B (en) | Data report processing method and device | |
| CN110990878B (en) | Construction method of private data derivative graph | |
| CN112988291B (en) | Page event management method and device, computer readable medium and electronic equipment | |
| CN111026945A (en) | Multi-platform crawler scheduling method and device and storage medium | |
| CN112579787A (en) | Knowledge graph construction method and device | |
| CN116051061A (en) | Information processing method, information processing device, electronic equipment and readable storage medium | |
| CN110674426A (en) | Webpage behavior reporting method and device | |
| US11860889B2 (en) | Cascading data impact visualization tool | |
| US11954088B2 (en) | Alert feed and subscription management | |
| CN112083974B (en) | Advertisement window closing method and device and electronic equipment | |
| CN110554892A (en) | Information acquisition method and device | |
| CN109450874B (en) | User account monitoring method and device | |
| CN113672660A (en) | Data query method, device and equipment | |
| CN113485689A (en) | Buried point processing method and device | |
| CN113961110B (en) | User operation response method, device, computer equipment and storage medium | |
| CN114363461B (en) | Application control method, device, electronic equipment and computer readable storage medium | |
| CN117389601A (en) | Financial software influence traceability analysis method, device, equipment and storage medium | |
| CN115904572A (en) | Template creating method, template calling method, program product, template system and template device | |
| CN110990171A (en) | Information prompting method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |