CN112306805A - Method and device for preventing repeated clicking, computer equipment and readable storage medium - Google Patents

Method and device for preventing repeated clicking, computer equipment and readable storage medium Download PDF

Info

Publication number
CN112306805A
CN112306805A CN202011192983.5A CN202011192983A CN112306805A CN 112306805 A CN112306805 A CN 112306805A CN 202011192983 A CN202011192983 A CN 202011192983A CN 112306805 A CN112306805 A CN 112306805A
Authority
CN
China
Prior art keywords
click
event
timestamp
trigger
signal
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
Application number
CN202011192983.5A
Other languages
Chinese (zh)
Inventor
毛丽君
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Pingan Payment Technology Service Co Ltd
Original Assignee
Pingan Payment Technology Service Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Pingan Payment Technology Service Co Ltd filed Critical Pingan Payment Technology Service Co Ltd
Priority to CN202011192983.5A priority Critical patent/CN112306805A/en
Publication of CN112306805A publication Critical patent/CN112306805A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3089Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
    • G06F11/3096Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents wherein the means or processing minimize the use of computing system or of computing system component resources, e.g. non-intrusive monitoring which minimizes the probe effect: sniffing, intercepting, indirectly deriving the monitored data from other directly available data
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3003Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3438Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment monitoring of user actions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Quality & Reliability (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Mathematical Physics (AREA)
  • Computer Hardware Design (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention relates to the technical field of software monitoring, and discloses a method and a device for preventing repeated clicking, computer equipment and a readable storage medium, wherein the method comprises the following steps: recording a click timestamp of the time of generating a click signal; acquiring a click event corresponding to the click signal, and acquiring a click stack corresponding to the click event; extracting historical click timestamps positioned at the top of a stack in a click stack, and calculating click time differences between the click timestamps and the historical click timestamps; judging whether the click time difference exceeds a preset click duration; if the click duration is exceeded, executing a click event; and if the click duration is not exceeded, intercepting the click event. The invention avoids the occurrence of the conditions that the server is blocked and lagged by the queue and the thread for executing the click event and even crashes the server due to repeated execution of the click event for a plurality of times in a short time. The invention also relates to the field of block chains, and the key event set obtained by traversing the keys of the network page and the click events thereof can be uploaded to the block chain.

Description

Method and device for preventing repeated clicking, computer equipment and readable storage medium
Technical Field
The invention relates to the technical field of software monitoring, in particular to a method and a device for preventing repeated clicking, computer equipment and a readable storage medium.
Background
The web page is a basic element constituting a website, and is a platform for bearing various website applications, and generally, a button is used for jumping to a page or feeding corresponding information back to a user in the design of the web page.
However, the inventor finds that, when a user triggers a click event corresponding to a button to be executed by clicking the button, the click event may not jump to a page or feed back corresponding information to the user due to the limitation of the operation calculation power of a server; at this time, the user may click the button many times to repeatedly trigger the execution of the click event, so that the server, which has originally been subjected to a large computational burden, is frosted on snow, which may cause the blocking and delaying of the queue and thread for executing the click event by the server, and even cause the server to crash.
Disclosure of Invention
The invention aims to provide a method, a device, computer equipment and a readable storage medium for preventing repeated clicking, which are used for solving the problems that in the prior art, a server executes a queue and a thread of a clicking event to be blocked and delayed and even the server is crashed due to multiple times of clicking by a user.
In order to achieve the above object, the present invention provides a method for preventing repeated clicks, comprising:
monitoring a click signal generated by a user side through clicking a key on a network page through a preset click processing module, and recording a click timestamp of the time of generating the click signal; the click signal reflects the code of the click key and a click timestamp for reflecting the time of clicking the key;
calling the click processing module to acquire a click event corresponding to the click signal and acquire a click stack corresponding to the click event;
judging whether the click stack is empty or not; if the click stack is empty, judging that the click signal is an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; if the click stack is not empty, extracting a historical click timestamp positioned at the top of the click stack, and calculating the click time difference between the click timestamp and the historical click timestamp;
judging whether the click time difference exceeds a preset click duration; if the click duration is exceeded, judging the click signal as an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
In the above solution, before the preset click processing module monitors a click signal generated by a user clicking a key on a web page, the method further includes:
triggering a page loading signal generated when a network page is loaded, and traversing keys of the network page and click events thereof to obtain a key event set;
creating a click processing module of the network page according to the key event set, and constructing a click stack and a trigger stack corresponding to each click event in the key event set; the click processing module is used for monitoring and recording a click timestamp when a key is clicked and generating a click signal, identifying a click event corresponding to the key and forwarding the click signal to the click event, and monitoring and recording a trigger timestamp of time for executing the click event according to the click signal; the click stack is used for storing click time stamps of click signals received by click events, and the trigger stack is used for storing the trigger time stamps generated when the corresponding click events are executed.
In the above solution, after traversing the keys of the web page and the click events thereof to obtain a key event set, the method further includes:
deleting the keys which can be clicked repeatedly and click events thereof in the key event set;
after deleting the re-clickable key and the click event thereof in the key event set, the method further comprises:
and uploading the key event set to a block chain.
In the above solution, the step of deleting the key that can be clicked repeatedly and the click event thereof in the key event set includes:
identifying inheritance keywords of each click event in the key event set through a developer debugging tool, and setting the click events with the inheritance keywords as events to be identified;
judging whether the class inherited by the event to be identified belongs to a preset repeatable base class set or not, wherein at least one class is arranged in the repeatable base class set;
if so, judging the event to be identified as a repeatable event, and deleting the repeatable event from the key event set;
if not, the event to be identified is restored to be a click event, and the click event is stored in the key event set.
In the above solution, after the recording generates the click timestamp of the click signal time, the method further includes:
and calling the click processing module to acquire a click event corresponding to the click signal and acquire a trigger timestamp corresponding to the click event, wherein the trigger timestamp reflects the time for executing the click event according to the click signal.
In the above scheme, after obtaining the trigger timestamp corresponding to the click event, the method further includes:
judging whether the trigger stack is empty or not;
if yes, judging that the click signal is an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack;
if not, extracting the historical trigger time stamp of the top in the trigger stack, and calculating the trigger time difference between the click time stamp of the click signal and the historical trigger time stamp of the top.
In the above solution, after the calculating the trigger time difference between the click timestamp of the click signal and the set-top historical trigger timestamp, the method further includes:
judging whether the trigger time difference exceeds a preset trigger duration;
if the trigger duration is exceeded, judging the click signal as an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack;
and if the trigger duration is not exceeded, intercepting the click event and ending to avoid repeatedly executing the click event.
In order to achieve the above object, the present invention further provides a device for preventing repeated clicks, comprising:
the monitoring and recording module is used for monitoring a click signal generated by a user side on a network page through clicking a key through a preset click processing module and recording a click timestamp of the time of generating the click signal; the click signal reflects the code of the click key and a click timestamp for reflecting the time of clicking the key;
the click matching module is used for calling the click processing module to acquire a click event corresponding to the click signal and acquire a click stack corresponding to the click event;
the click stack management module is used for judging whether the click stack is empty or not; if the click stack is empty, judging that the click signal is an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; if the click stack is not empty, extracting a historical click timestamp positioned at the top of the click stack, and calculating the click time difference between the click timestamp and the historical click timestamp;
the click judging module is used for judging whether the click time difference exceeds a preset click duration; if the click duration is exceeded, judging the click signal as an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
To achieve the above object, the present invention further provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor of the computer device implements the steps of the above method for preventing repeated clicks when executing the computer program.
To achieve the above object, the present invention further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the steps of the above method for preventing repeated clicks.
According to the method, the device, the computer equipment and the readable storage medium for preventing repeated clicking, click signals generated by clicking keys on a network page by a user side are monitored, click time stamps of time for generating the click signals are recorded, and click events corresponding to codes are obtained; whether the user performs the click operation of the click event again or not is identified by judging whether the click time difference exceeds the click duration time or not, so that the reliability of the click event executed by the page is ensured, and the click event is intercepted if the click duration time is not exceeded, so that the occurrence of the situation that the server breaks down due to the blockage and delay of a queue and a thread for executing the click event and even the click event is executed repeatedly for multiple times in a short time is avoided.
Drawings
FIG. 1 is a flowchart of a first embodiment of a method for preventing double clicking according to the present invention;
FIG. 2 is a schematic diagram of an environment application of a method for preventing a repeat click in a second embodiment of the method for preventing a repeat click according to the present invention;
FIG. 3 is a flowchart of a specific method of the method for preventing double clicking according to the second embodiment of the method for preventing double clicking of the present invention;
FIG. 4 is a schematic diagram illustrating program modules of a third embodiment of the anti-click-back apparatus of the present invention;
fig. 5 is a schematic diagram of a hardware structure of a computer device according to a fourth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The invention provides a method and a device for preventing repeated clicking, computer equipment and a readable storage medium, which are suitable for the technical field of software monitoring and provide a method for preventing repeated clicking based on a monitoring recording module, a clicking matching module, a clicking stack management module and a clicking judgment module. The method comprises the steps that a preset click processing module monitors click signals generated by clicking keys on a network page by a user side, and records click timestamps of time for generating the click signals; calling the click processing module to acquire a click event corresponding to the click signal and acquire a click stack corresponding to the click event; judging whether the click stack is empty or not; if the click stack is not empty, extracting a historical click timestamp positioned at the top of the click stack, and calculating the click time difference between the click timestamp and the historical click timestamp; judging whether the click time difference exceeds a preset click duration; if the click duration is exceeded, judging the click signal as an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
The first embodiment is as follows:
referring to fig. 1, a method for preventing repeated clicks of the present embodiment includes:
s103: monitoring a click signal generated by a user side through clicking a key on a network page through a preset click processing module, and recording a click timestamp of the time of generating the click signal; the click signal reflects the code of the click key and a click timestamp for reflecting the time of clicking the key;
s104: calling the click processing module to acquire a click event corresponding to the click signal and acquire a click stack corresponding to the click event;
s106: judging whether the click stack is empty or not; if the click stack is empty, judging that the click signal is an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; if the click stack is not empty, extracting a historical click timestamp positioned at the top of the click stack, and calculating the click time difference between the click timestamp and the historical click timestamp;
s107: judging whether the click time difference exceeds a preset click duration; if the click duration is exceeded, judging the click signal as an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
In this embodiment, the click processing module monitors a click signal generated by a user terminal by clicking a key on a web page, and records a click timestamp of the time when the click signal is generated, so as to ensure that the time when the click signal is generated can be obtained in time.
And acquiring a click event corresponding to the code by calling a click processing module and through the code of the click key in the click signal, and meanwhile, judging whether the click signal is generated by repeatedly clicking in a short time from the frequency dimension of the click key of the user by acquiring a click stack corresponding to the click event so as to ensure that the click signal can accurately trigger the corresponding click event.
Identifying the click signal by a method of judging whether the click stack is empty, if so, judging that the click signal is generated by the first click of the key by the user, and further judging that the click signal is an execution signal; if the click stack is not empty, judging that the click signal is generated when the user repeatedly clicks the key, further extracting a historical click timestamp positioned at the top of the click stack, and calculating a click time difference between the click timestamp and the historical click timestamp so as to identify whether the click signal is generated when the user firstly clicks the key.
Identifying by judging whether the click time difference exceeds the click duration; if the click duration is exceeded, judging that the click signal is not repeatedly clicked in a short time by the user, but clicking operation of re-executing the click event is performed by the user because the page is not jumped for a long time or information is fed back, and ensuring the reliability of executing the click event by the page; if the click duration is not exceeded, the click signal is judged to be repeated click of the user in a short time, and the click event is intercepted, so that the condition that the server breaks down due to queue and thread blockage and delay of the click event caused by repeated click event execution in a short time is avoided.
Example two:
the embodiment is a specific application scenario of the first embodiment, and the method provided by the present invention can be more clearly and specifically explained through the embodiment.
Next, the method provided in this embodiment will be specifically described by taking an example in which, in a server running a method for preventing repeated clicks, a click time difference between a click time stamp and a historical click time stamp is calculated, whether the click time difference exceeds a preset click duration is determined, and the click event is executed or intercepted. It should be noted that the present embodiment is only exemplary, and does not limit the protection scope of the embodiments of the present invention.
Fig. 2 schematically shows an environment application diagram of the method for preventing repeated clicks according to the second embodiment of the present application.
In an exemplary embodiment, the servers 2 in which the method for preventing repeated clicks is located are respectively connected with the user terminals 4 through the network 3; the server 2 may provide services through one or more networks 3, which networks 3 may include various network devices, such as routers, switches, multiplexers, hubs, modems, bridges, repeaters, firewalls, proxy devices, and/or the like. The network 3 may include physical links, such as coaxial cable links, twisted pair cable links, fiber optic links, combinations thereof, and/or the like. The network 3 may include wireless links, such as cellular links, satellite links, Wi-Fi links, and/or the like; the user terminal 4 may be a computer device such as a smart phone, a tablet computer, a notebook computer, and a desktop computer.
Fig. 3 is a flowchart of a specific method of a method for preventing repeated clicks according to an embodiment of the present invention, where the method specifically includes steps S200 to S210.
S200: and triggering a page loading signal generated when the network page is loaded, and traversing keys of the network page and click events thereof to obtain a key event set.
When monitoring or receiving a page loading signal generated by a server loading a network page, acquiring a page code in the network page according to the page loading signal, and traversing key attributes and click events in the page code through a developer debugging tool; the page code is a computer program for defining and executing the network page, the key attribute is an attribute code used for defining keys in the network page in the page code, and the click event is an event code which corresponds to the key attribute in the code page and is used for triggering execution according to a click signal generated by the key attribute.
In this embodiment, the page code may be html code, java code, Android code or js code. Traversing character codes with button characters in the page codes through a developer debugging tool, and setting the character codes as key attributes; and identifying an event, key code event and an event, which event corresponding to the key attribute through the developer debugging tool to obtain a click event corresponding to the key attribute.
It should be noted that the developer debugging tool is a computer tool for developing and managing pages, such as ADB, TraceView, Logcat, Dev Tools. Since the developer debugging tool belongs to the prior art, and the technical problem solved in this step is how to identify the button and the click event in the web page, the use and operation principle of the developer debugging tool are not described herein again.
S201: and deleting the key which can be clicked repeatedly and the click event thereof in the key event set.
In order to avoid the situation that repeated clicking without interception in a network page is intercepted, so that a repeatedly executable clicking event is blocked, the key which can be repeatedly clicked and the clicking event corresponding to the key in the key event set are identified and deleted, so that the clicking event corresponding to the key can be repeatedly triggered for multiple times when the key with higher precision requirement is clicked, and the diversity of network page key management is further met.
In a preferred embodiment, the step of deleting the re-clickable button and the click event thereof in the button event set comprises:
s11: and identifying the inheritance keywords of each click event in the key event set through a developer debugging tool, and setting the click events with the inheritance keywords as events to be identified.
In this step, the inherited keyword is an extands. Meanwhile, the technical effect of setting the click event with the keywords as the event to be identified can be realized by adding the label to be identified in the click event.
S12: and judging whether the class inherited by the event to be identified belongs to a preset repeatable base class set, wherein the repeatable base class set at least has one class.
S13: if yes, the event to be identified is judged to be a repeatable event, and the repeatable event is deleted from the key event set.
In this step, the technical effect of determining the event to be identified as a repeatable event can be achieved by modifying the tag to be identified in the event to be identified as a repeatable tag.
S14: if not, the event to be identified is restored to be a click event, and the click event is stored in the key event set.
In this step, the technical effect of restoring the event to be identified to the click time can be achieved by deleting the tag to be identified in the event to be identified.
Illustratively, assuming there is a Cleanser class in the repeatable base class set, if the code of the click event is:
public class Detergent extends Cleanser{
}
then, setting the click event as an event to be identified as the code has an "extensions" inheritance keyword;
since the term "detegent extensions clearers" indicates that detegent inherits the clearers class, which belongs to the repeatable base class set, the time to be identified is set as a repeatable event.
Optionally, after deleting the key that can be clicked repeatedly in the key event set and the click event thereof, the method further includes:
and uploading the key event set to a block chain.
It should be noted that the corresponding summary information is obtained based on the key event set, and specifically, the summary information is obtained by hashing the key event set, for example, by using the sha256s algorithm. Uploading summary information to the blockchain can ensure the safety and the fair transparency of the user. The user device may download the summary information from the blockchain to verify that the set of key events has been tampered with. The blockchain referred to in this example is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm, and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
S202: creating a click processing module of the network page according to the key event set, and constructing a click stack and a trigger stack corresponding to each click event in the key event set; the click processing module is used for monitoring and recording a click timestamp when a key is clicked and generating a click signal, identifying a click event corresponding to the key and forwarding the click signal to the click event, and monitoring and recording a trigger timestamp of time for executing the click event according to the click signal; the click stack is used for storing click time stamps of click signals received by click events, and the trigger stack is used for storing the trigger time stamps generated when the corresponding click events are executed.
The method aims to avoid the situation that code redundancy occurs because each key is provided with a set of anti-repeated click codes, and can judge whether the current click action of the user on the key is used for executing a click event or is repeated click action caused by anxiety or misoperation and the like according to the click timestamp and the trigger timestamp.
The method comprises the steps that a click processing module used for monitoring and recording click timestamps and trigger timestamps and configuring incidence relations between keys and click events is built through a key event set, the key event set generated by traversing page codes integrates the relations between the keys and the click events in a network page, each click event receives click timestamp management of a click signal, and each click event generates trigger timestamp management when being executed.
Therefore, the keys of the network page and the clicking events thereof can be subjected to repeated clicking prevention management only by one clicking processing module, and each key is not required to be provided with a set of repeated clicking prevention codes, so that code redundancy is reduced, a clicking stack and a triggering stack are effectively utilized, and the behavior for clicking the key is judged.
Optionally, after creating the click processing module of the web page according to the key event set, the method further includes:
constructing click variables and trigger variables corresponding to each click event in the key event set; the click variable is used for storing a click timestamp of a click signal received by a click event, and the trigger variable is used for storing a trigger timestamp generated when the corresponding click event is executed.
In the step, a register module is opened up in a server running the method for preventing repeated clicking to be used as a carrier for setting the clicking variable and the triggering variable.
S203: monitoring a click signal generated by a user side through clicking a key on a network page through a preset click processing module, recording a click timestamp of the time of generating the click signal, and executing the step S204 or the step S205; and the click signal reflects the code of the click key and a click timestamp for reflecting the time of clicking the key.
In order to ensure that the time for generating the click signal can be obtained in time, the click processing module monitors the click signal generated by the user side through clicking the key on the network page, and records the click timestamp for generating the time of the click signal.
In this embodiment, the click processing module monitors a behavior of a user clicking a button by using an onclick event.
S204: and calling the click processing module to acquire the click event corresponding to the click signal, acquiring the click stack corresponding to the click event, and executing the step S206.
In order to ensure that the click signal can accurately trigger the corresponding click event, the click processing module is called, the click event corresponding to the code is obtained through the code of the click button in the click signal, and meanwhile, the click stack corresponding to the click event is obtained to judge whether the click signal is generated by repeated click in a short time according to the frequency dimension of the click button of a user. Wherein the data operation of the click stack is first-in and last-out.
In this embodiment, the click timestamp is set as a local variable, so that the value of the click timestamp is changed along with the behavior of the user clicking the key.
Optionally, after the click processing module is called to obtain the click event corresponding to the click signal, the method may further include:
and obtaining a click variable corresponding to the click event.
S205: and calling the click processing module to acquire a click event corresponding to the click signal and a trigger timestamp corresponding to the click event, wherein the trigger timestamp reflects the time of executing the click event according to the click signal, and then executing the step S208.
In order to ensure that the click signal can accurately trigger the corresponding click event, the step calls a click processing module, obtains the click time corresponding to the code through the code of the click key in the click signal, and also obtains a trigger stack corresponding to the click event so as to judge whether the click signal triggers the click event for multiple times in a short time from the frequency dimension executed by the click event. Wherein the data operation of the trigger stack is a first-in-last-out.
In this embodiment, the trigger timestamp is set as a local variable, so that the value of the trigger timestamp is changed along with the behavior of clicking a key by a user.
S206: judging whether the click stack is empty or not;
if the click stack is empty, judging that the click signal is an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack;
if the click stack is not empty, extracting a historical click timestamp positioned at the top of the click stack, calculating a click time difference between the click timestamp and the historical click timestamp, and executing the step S207.
In order to identify whether the click signal is generated when the user clicks the key for the first time, the step identifies the click signal by a method of judging whether a click stack is empty, if the click stack is empty, the click signal is generated when the user clicks the key for the first time, and then the click signal is judged as an execution signal; if the click stack is not empty, judging that the click signal is generated when the user repeatedly clicks the key, further extracting a historical click timestamp positioned at the top of the click stack, and calculating the click time difference between the click timestamp and the historical click timestamp.
The click time difference reflects the time difference between the clicks of the keys by the user from the angle of the keys clicked by the user, and the length of the time difference is beneficial to reflecting whether the behavior of the user is the behavior of repeated clicks due to worries or the repeated clicks due to the fact that the page is not jumped for a long time or the result is not fed back, so that the click event is not successfully triggered to be executed by the click signal, and the blockage or the error occurs in the process of triggering the corresponding click event according to the click signal.
Optionally, after obtaining the click variable corresponding to the click event, the method further includes:
judging whether the value of the click variable is a null value or not;
if the value of the click variable is a null value, judging that the click signal is an execution signal, executing the click event and replacing the click variable with the click timestamp;
and if the value of the click variable is not a null value, calculating the click time difference between the click timestamp and the click variable.
In this embodiment, the S206 is shown in fig. 3 by the following labels:
s61: judging whether the click stack is empty or not;
s62: if the click stack is empty, judging that the click signal is an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack;
s63: if the click stack is not empty, extracting a historical click timestamp positioned at the top of the click stack, calculating a click time difference between the click timestamp and the historical click timestamp, and executing the step S207.
S207: judging whether the click time difference exceeds a preset click duration;
if the click duration is exceeded, judging the click signal as an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack;
and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
In order to avoid the situation that the server is blocked, delayed or even crashed due to repeated events executed for multiple times because the server executes the click events repeatedly in a short time due to repeated clicks of the user, the step identifies by judging whether the click time difference exceeds the click duration time; if the click duration is exceeded, judging that the click signal is not repeatedly clicked in a short time by the user, but clicking operation of re-executing the click event is performed by the user because the page is not jumped for a long time or information is fed back, and ensuring the reliability of executing the click event by the page;
if the click duration is not exceeded, the click signal is judged to be repeated click of the user in a short time, and the click event is intercepted, so that the condition that the server breaks down due to queue and thread blockage and delay of the click event caused by repeated click event execution in a short time is avoided.
In this embodiment, the click duration is used as a global variable to ensure that the click processing module determines the click signal according to the fixed click duration; meanwhile, the historical click time stamp in the click stack is used as a global variable to solidify the time of the key click, so that the comparison of the time difference between the current time of the key click and the latest time of the key click is facilitated.
Further, the embodiment adopts an event distribution mechanism to execute the click event, and adopts an event interception mechanism to intercept the click event.
It should be noted that, the event distribution mechanism adopts the following method:
public booleandispatchTouchEvent(MotionEventev)。
the event interception mechanism adopts the following method:
public booleanonInterceptTouchEvent(MotionEventev)。
optionally, after calculating the click time difference between the click time stamp and the historical click time stamp, the method further includes:
judging whether the click time difference exceeds a preset click duration;
if the click duration is exceeded, judging that the click signal is an execution signal, executing the click event, and replacing the value of the click variable with the click timestamp;
and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
In this embodiment, the S207 is shown in fig. 3 by the following labels:
s71: judging whether the click time difference exceeds a preset click duration;
s72: if the click duration is exceeded, judging the click signal as an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack;
s73: and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
S208: judging whether the trigger stack is empty or not;
if yes, judging that the click signal is an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack;
if not, extracting the historical trigger time stamp of the top in the trigger stack, calculating the trigger time difference between the click time stamp of the click signal and the historical trigger time stamp of the top, and then executing the step S209.
In order to identify whether the click signal is a signal for triggering a click event for the first time, the click signal is identified by judging whether a trigger stack is empty, if the trigger stack is empty, the click signal is generated by a user clicking the key for the first time, and is further judged as an execution signal, the time for executing the click event is monitored by the click processing module, and the time is set as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack; if the trigger stack is not empty, judging that the click signal is generated when the user repeatedly clicks the key, further extracting a historical trigger timestamp positioned at the top of the trigger stack, and calculating a trigger time difference between the historical trigger timestamp and the click timestamp.
Optionally, judging whether the value of the trigger variable is a null value;
if yes, judging that the click signal is an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; replacing the value of the trigger variable with the trigger timestamp;
if not, calculating the triggering time difference between the clicking time stamp of the clicking signal and the triggering variable.
In this embodiment, the S208 is shown in fig. 3 by the following labels:
s81: judging whether the trigger stack is empty or not;
s82: if yes, judging that the click signal is an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack;
s83: if not, extracting the historical trigger time stamp of the top in the trigger stack, calculating the trigger time difference between the click time stamp of the click signal and the historical trigger time stamp of the top, and then executing the step S209.
S209: judging whether the trigger time difference exceeds a preset trigger duration;
if the trigger duration is exceeded, judging the click signal as an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack;
and if the trigger duration is not exceeded, intercepting the click event and ending to avoid repeatedly executing the click event.
In order to identify whether a blockage or an error occurs in the execution process of the click event, whether the trigger time difference exceeds the trigger duration is judged, wherein the trigger time difference reflects the click time stamp of the key clicked by the user and the time difference between the trigger time stamp of the latest click event and the trigger time stamp of the corresponding click event triggered after the key is clicked by the user. Since the trigger timestamp reflects the time node that successfully triggers the execution of the click event, once the click timestamp and the historical trigger timestamp set at the top in the trigger stack exceed the trigger duration, it indicates that, when the click signal is received, the page does not jump or feedback the corresponding information even if the click event is successfully triggered, thereby reflecting that the execution of the click event is not successful, and further indicating that a jam or an error may occur in the process of executing the click event.
In this embodiment, the trigger duration is used as a global variable to ensure that the trigger processing module determines the trigger signal according to the fixed trigger duration; meanwhile, the historical trigger timestamp in the trigger stack is used as a global variable to solidify the time of triggering the key, so that the comparison of the current time of clicking the key and the time difference between the latest time of triggering the click event corresponding to the key is facilitated.
In a preferred embodiment, after the setting the trigger timestamp as the historical trigger timestamp is saved to the trigger stack, the method further includes:
and sending the click event to a control end.
Since the click event may be blocked or wrong in the execution process, the click event is sent to the control end, so that the developer can timely process the click event with the error.
Further, the embodiment adopts an event distribution mechanism to execute the click event, and adopts an event interception mechanism to intercept the click event.
It should be noted that, the event distribution mechanism adopts the following method:
public booleandispatchTouchEvent(MotionEventev)。
the event interception mechanism adopts the following method:
public booleanonInterceptTouchEvent(MotionEventev)。
optionally, after calculating a trigger time difference between the click timestamp of the click signal and the trigger variable, the method further includes:
judging whether the trigger time difference exceeds a preset trigger duration;
if the trigger duration is exceeded, judging the click signal as an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; replacing the value of the trigger variable with the trigger timestamp;
and if the trigger duration is not exceeded, intercepting the click event and ending to avoid repeatedly executing the click event.
In this embodiment, the S209 is shown in fig. 3 by the following labels:
s91: judging whether the trigger time difference exceeds a preset trigger duration;
s92: if the trigger duration is exceeded, judging the click signal as an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack;
s93: and if the trigger duration is not exceeded, intercepting the click event and ending to avoid repeatedly executing the click event.
S210: traversing each click stack and each trigger stack in the click processing module;
identifying click stacks of which the number of historical click timestamps exceeds a preset click threshold value, and sending click events corresponding to the click stacks to a control terminal;
and identifying the trigger stacks of which the number of the historical trigger timestamps exceeds a preset trigger threshold, and sending the click time corresponding to the trigger stacks to a control terminal.
In this step, for the click stacks whose historical click timestamps exceed the click threshold, it is indicated that the click events corresponding to the click stacks are frequently clicked, and it is further indicated that the click signals may not trigger the execution of the click events, so that the click events are sent to the control end, and developers can repair the click events conveniently.
For the trigger stacks with the historical trigger timestamps exceeding the trigger threshold, the trigger stacks corresponding to the trigger stacks are frequently triggered, and further the click events cannot be skipped or corresponding information cannot be fed back in time even if the click events are frequently executed, so that the click events are sent to the control end, and developers can repair the trigger stacks.
Example three:
referring to fig. 4, a device 1 for preventing repeated clicks of the present embodiment includes:
the monitoring and recording module 13 is used for monitoring a click signal generated by a user terminal through clicking a key on a network page through a preset click processing module and recording a click timestamp of the time of generating the click signal; the click signal reflects the code of the click key and a click timestamp for reflecting the time of clicking the key;
the click matching module 14 is used for calling the click processing module to acquire a click event corresponding to the click signal and acquire a click stack corresponding to the click event;
the click stack management module 16 is used for judging whether the click stack is empty or not; if the click stack is empty, judging that the click signal is an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; if the click stack is not empty, extracting a historical click timestamp positioned at the top of the click stack, and calculating the click time difference between the click timestamp and the historical click timestamp;
a click judgment module 17, configured to judge whether the click time difference exceeds a preset click duration; if the click duration is exceeded, judging the click signal as an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
Optionally, the device 1 for preventing repeated clicks further includes:
and the triggering traversing module 10 is configured to trigger a page loading signal generated when a web page is loaded, and traverse keys of the web page and click events thereof to obtain a key event set.
Optionally, the device 1 for preventing repeated clicks further includes:
and the deleting module 11 is configured to delete the key which can be clicked repeatedly in the key event set and the click event thereof.
Optionally, the device 1 for preventing repeated clicks further includes:
the stack creation module 12 is used for creating a click processing module of the network page according to the key event set, and constructing a click stack and a trigger stack corresponding to each click event in the key event set; the click processing module is used for monitoring and recording a click timestamp when a key is clicked and generating a click signal, identifying a click event corresponding to the key and forwarding the click signal to the click event, and monitoring and recording a trigger timestamp of time for executing the click event according to the click signal; the click stack is used for storing click time stamps of click signals received by click events, and the trigger stack is used for storing the trigger time stamps generated when the corresponding click events are executed.
Optionally, the device 1 for preventing repeated clicks further includes:
and the trigger matching module 15 is configured to call the click processing module to obtain a click event corresponding to the click signal, and obtain a trigger timestamp corresponding to the click event, where the trigger timestamp is a trigger timestamp reflecting a time for executing the click event according to the click signal, and then call the trigger stack management module 18.
Optionally, the device 1 for preventing repeated clicks further includes:
a trigger stack management module 18, configured to determine whether the trigger stack is empty;
if yes, judging that the click signal is an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack;
if not, extracting the historical trigger time stamp of the top in the trigger stack, calculating the trigger time difference between the click time stamp of the click signal and the historical trigger time stamp of the top, and calling a trigger judgment module 19.
Optionally, the device 1 for preventing repeated clicks further includes:
a trigger judging module 19, configured to judge whether the trigger time difference exceeds a preset trigger duration; if the trigger duration is exceeded, judging the click signal as an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack; and if the trigger duration is not exceeded, intercepting the click event and ending to avoid repeatedly executing the click event.
Optionally, the device 1 for preventing repeated clicks further includes:
the stack management module 20 is used for traversing each click stack and each trigger stack in the click processing module; identifying click stacks of which the number of historical click timestamps exceeds a preset click threshold value, and sending click events corresponding to the click stacks to a control terminal; and identifying the trigger stacks of which the number of the historical trigger timestamps exceeds a preset trigger threshold, and sending the click time corresponding to the trigger stacks to a control terminal.
The technical scheme is applied to the field of software monitoring, and the click timestamp of the click signal time is generated by recording; calling the click processing module to acquire a click event corresponding to the click signal and acquire a click stack corresponding to the click event; extracting historical click timestamps positioned at the top of the stack in the click stack, and calculating click time differences between the click timestamps and the historical click timestamps; judging whether the click time difference exceeds a preset click duration; if the click duration is exceeded, executing the click event; if the click duration time is not exceeded, intercepting the click event, and avoiding the occurrence of the conditions of queue and thread blockage, delay and even server crash caused by the fact that the server executes the click event repeatedly for multiple times in a short time in a mode of monitoring system data of the server (namely, the click signal and the click timestamp thereof), thereby realizing the purpose of the server
Example four:
in order to achieve the above object, the present invention further provides a computer device 5, in which components of the device 1 for preventing repeated clicks in the third embodiment may be distributed in different computer devices, and the computer device 5 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster formed by multiple application servers) for executing programs, and the like. The computer device of the embodiment at least includes but is not limited to: a memory 51, a processor 52, which may be communicatively coupled to each other via a system bus, as shown in FIG. 5. It should be noted that fig. 5 only shows a computer device with components, but it should be understood that not all of the shown components are required to be implemented, and more or fewer components may be implemented instead.
In this embodiment, the memory 51 (i.e., a readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory 51 may be an internal storage unit of the computer device, such as a hard disk or a memory of the computer device. In other embodiments, the memory 51 may be an external storage device of a computer device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the computer device. Of course, the memory 51 may also include both internal and external storage devices of the computer device. In this embodiment, the memory 51 is generally used for storing an operating system and various application software installed on the computer device, such as the program codes of the device for preventing repeated clicks in the third embodiment. Further, the memory 51 may also be used to temporarily store various types of data that have been output or are to be output.
Processor 52 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 52 is typically used to control the overall operation of the computer device. In this embodiment, the processor 52 is configured to run a program code stored in the memory 51 or process data, for example, run a device for preventing a double click, so as to implement the method for preventing a double click in the first embodiment and the second embodiment.
Example five:
to achieve the above objects, the present invention also provides a computer readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application store, etc., on which a computer program is stored, which when executed by a processor 52, implements corresponding functions. The computer readable storage medium of the present embodiment is used for storing a device for preventing a repeat click, and when being executed by the processor 52, the device implements the method for preventing a repeat click of the first embodiment and the second embodiment.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (10)

1. A method of preventing double clicking, comprising:
monitoring a click signal generated by a user side through clicking a key on a network page through a preset click processing module, and recording a click timestamp of the time of generating the click signal; the click signal reflects the code of the click key and a click timestamp for reflecting the time of clicking the key;
calling the click processing module to acquire a click event corresponding to the click signal and acquire a click stack corresponding to the click event;
judging whether the click stack is empty or not; if the click stack is empty, judging that the click signal is an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; if the click stack is not empty, extracting a historical click timestamp positioned at the top of the click stack, and calculating the click time difference between the click timestamp and the historical click timestamp;
judging whether the click time difference exceeds a preset click duration; if the click duration is exceeded, judging the click signal as an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
2. The method for preventing repeated clicks according to claim 1, wherein before the preset click processing module monitors the click signal generated by the user terminal by clicking the button on the web page, the method further comprises:
triggering a page loading signal generated when a network page is loaded, and traversing keys of the network page and click events thereof to obtain a key event set;
creating a click processing module of the network page according to the key event set, and constructing a click stack and a trigger stack corresponding to each click event in the key event set; the click processing module is used for monitoring and recording a click timestamp when a key is clicked and generating a click signal, identifying a click event corresponding to the key and forwarding the click signal to the click event, and monitoring and recording a trigger timestamp of time for executing the click event according to the click signal; the click stack is used for storing click time stamps of click signals received by click events, and the trigger stack is used for storing the trigger time stamps generated when the corresponding click events are executed.
3. The method of claim 2, wherein after traversing the keys of the web page and the click events thereof to obtain a set of key events, the method further comprises:
deleting the keys which can be clicked repeatedly and click events thereof in the key event set;
after deleting the re-clickable key and the click event thereof in the key event set, the method further comprises:
and uploading the key event set to a block chain.
4. The method of claim 3, wherein the step of deleting the re-clickable button and its click event in the set of button events comprises:
identifying inheritance keywords of each click event in the key event set through a developer debugging tool, and setting the click events with the inheritance keywords as events to be identified;
judging whether the class inherited by the event to be identified belongs to a preset repeatable base class set or not, wherein at least one class is arranged in the repeatable base class set;
if so, judging the event to be identified as a repeatable event, and deleting the repeatable event from the key event set;
if not, the event to be identified is restored to be a click event, and the click event is stored in the key event set.
5. The method of claim 1, wherein after the recording generates a click timestamp of the click signal time, the method further comprises:
and calling the click processing module to acquire a click event corresponding to the click signal and acquire a trigger timestamp corresponding to the click event, wherein the trigger timestamp reflects the time for executing the click event according to the click signal.
6. The method of claim 5, wherein after obtaining a trigger timestamp corresponding to the click event, the method further comprises:
judging whether the trigger stack is empty or not;
if yes, judging that the click signal is an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack;
if not, extracting the historical trigger time stamp of the top in the trigger stack, and calculating the trigger time difference between the click time stamp of the click signal and the historical trigger time stamp of the top.
7. The method of claim 6, wherein after calculating the trigger time difference between the click timestamp of the click signal and the set-top historical trigger timestamp, the method further comprises:
judging whether the trigger time difference exceeds a preset trigger duration;
if the trigger duration is exceeded, judging the click signal as an execution signal and executing the click event, monitoring the time for executing the click event through the click processing module and setting the time as a trigger timestamp; setting the trigger timestamp as a historical trigger timestamp and storing the historical trigger timestamp in the trigger stack;
and if the trigger duration is not exceeded, intercepting the click event and ending to avoid repeatedly executing the click event.
8. An anti-double click device, comprising:
the monitoring and recording module is used for monitoring a click signal generated by a user side on a network page through clicking a key through a preset click processing module and recording a click timestamp of the time of generating the click signal; the click signal reflects the code of the click key and a click timestamp for reflecting the time of clicking the key;
the click matching module is used for calling the click processing module to acquire a click event corresponding to the click signal and acquire a click stack corresponding to the click event;
the click stack management module is used for judging whether the click stack is empty or not; if the click stack is empty, judging that the click signal is an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; if the click stack is not empty, extracting a historical click timestamp positioned at the top of the click stack, and calculating the click time difference between the click timestamp and the historical click timestamp;
the click judging module is used for judging whether the click time difference exceeds a preset click duration; if the click duration is exceeded, judging the click signal as an execution signal, executing the click event, setting the click timestamp as a historical click timestamp, and storing the historical click timestamp in the click stack; and if the click duration time is not exceeded, judging that the click signal is a repeated signal and intercepting the click event.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of preventing double clicking as claimed in any one of claims 1 to 7 are implemented by the processor of the computer device when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, the computer program stored in the computer-readable storage medium, when being executed by a processor, implementing the steps of the method for preventing double clicking as claimed in any one of claims 1 to 7.
CN202011192983.5A 2020-10-30 2020-10-30 Method and device for preventing repeated clicking, computer equipment and readable storage medium Pending CN112306805A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011192983.5A CN112306805A (en) 2020-10-30 2020-10-30 Method and device for preventing repeated clicking, computer equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011192983.5A CN112306805A (en) 2020-10-30 2020-10-30 Method and device for preventing repeated clicking, computer equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN112306805A true CN112306805A (en) 2021-02-02

Family

ID=74332992

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011192983.5A Pending CN112306805A (en) 2020-10-30 2020-10-30 Method and device for preventing repeated clicking, computer equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN112306805A (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113032172A (en) * 2021-03-04 2021-06-25 北京字节跳动网络技术有限公司 Abnormity detection method and device and electronic equipment
CN113419874A (en) * 2021-06-21 2021-09-21 网易(杭州)网络有限公司 Interface request triggering method and device, storage medium and computer equipment
CN113709258A (en) * 2021-10-27 2021-11-26 湖南新云网科技有限公司 Praise anti-replay method, equipment and storage medium
CN113986091A (en) * 2021-10-29 2022-01-28 掌阅科技股份有限公司 Anti-repeat click method, electronic device and computer storage medium
CN113032172B (en) * 2021-03-04 2024-05-28 北京字节跳动网络技术有限公司 Abnormality detection method and device and electronic equipment

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113032172A (en) * 2021-03-04 2021-06-25 北京字节跳动网络技术有限公司 Abnormity detection method and device and electronic equipment
CN113032172B (en) * 2021-03-04 2024-05-28 北京字节跳动网络技术有限公司 Abnormality detection method and device and electronic equipment
CN113419874A (en) * 2021-06-21 2021-09-21 网易(杭州)网络有限公司 Interface request triggering method and device, storage medium and computer equipment
CN113419874B (en) * 2021-06-21 2023-08-08 网易(杭州)网络有限公司 Interface request triggering method and device, storage medium and computer equipment
CN113709258A (en) * 2021-10-27 2021-11-26 湖南新云网科技有限公司 Praise anti-replay method, equipment and storage medium
CN113709258B (en) * 2021-10-27 2022-02-11 湖南新云网科技有限公司 Praise anti-replay method, equipment and storage medium
CN113986091A (en) * 2021-10-29 2022-01-28 掌阅科技股份有限公司 Anti-repeat click method, electronic device and computer storage medium

Similar Documents

Publication Publication Date Title
CN112306805A (en) Method and device for preventing repeated clicking, computer equipment and readable storage medium
CN108600029B (en) Configuration file updating method and device, terminal equipment and storage medium
EP3712793B1 (en) Integrity assurance during runtime
CN108932189B (en) Method and device for saving server log
US10489232B1 (en) Data center diagnostic information
CN112527484B (en) Workflow breakpoint continuous running method and device, computer equipment and readable storage medium
CN111835467B (en) Message sending method, device, computer equipment and storage medium
CN110062926B (en) Device driver telemetry
US11934972B2 (en) Configuration assessment based on inventory
CN111651595A (en) Abnormal log processing method and device
CN114936136A (en) Business process monitoring method and device, computer equipment and storage medium
CN110908910B (en) Block chain-based test monitoring method and device and readable storage medium
CN116305290A (en) System log security detection method and device, electronic equipment and storage medium
CN111782440A (en) Data processing method and device and electronic equipment
CN109508249B (en) Crash processing method and device and electronic equipment
CN111338688A (en) Long-acting data caching method and device, computer system and readable storage medium
CN113031997A (en) Upgrade package generation and management method and device, computer equipment and storage medium
CN112118352B (en) Method and device for processing notification trigger message, electronic equipment and computer readable medium
CN112148387A (en) Method and device for preloading feedback information, computer equipment and storage medium
CN115495424A (en) Data processing method, electronic device and computer program product
CN114090268B (en) Container management method and container management system
CN115269252A (en) Application program fault processing method, device, equipment and storage medium
CN115373886A (en) Service group container shutdown method, device, computer equipment and storage medium
CN114416560A (en) Program crash analysis aggregation method and system
CN111722946A (en) Distributed transaction processing method and device, computer equipment and readable 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