how to handle click events happening at the same time in jquery
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
1
my system is all about sending remittances to different places in the world. i sometimes find a scenario by which 2 different users do the following:
- User1(the remittance payer) clicks "pay" button for paying it.
- User2(the remittance sender) clicks "return" button for returning it.
These 2 events occur at the same time thus leading to the system confused with which event is to be considered/handled first !
Q: Is there a way of considering one event by ignoring the other event ?
Any help is much appreciated.
Thanks in advance.
javascript jquery node.js
asked Nov 14 '18 at 7:30
CCCCCC
198
|
show 5 more comments
1
my system is all about sending remittances to different places in the world. i sometimes find a scenario by which 2 different users do the following:
- User1(the remittance payer) clicks "pay" button for paying it.
- User2(the remittance sender) clicks "return" button for returning it.
These 2 events occur at the same time thus leading to the system confused with which event is to be considered/handled first !
Q: Is there a way of considering one event by ignoring the other event ?
Any help is much appreciated.
Thanks in advance.
javascript jquery node.js
asked Nov 14 '18 at 7:30
CCCCCC
198
'at the same time' isn't a thing in JS, the events should be two different calls into the event handler which happen one after another. even if an event occurs at the same exact nanosecond, the js event handler will still have to process them separately
– RenaissanceProgrammer
Nov 14 '18 at 7:43
In the future Node will be multithreaded, but for now it's single threaded so you can't have race condition because all the events are put in a queue for serialized handling.
– Dominique Fortin
Nov 14 '18 at 7:48
@CCC Please give an example of the unwanted behavior that you observed.
– Dominique Fortin
Nov 14 '18 at 7:53
@Dominique Fortin, similar unwanted behaviors observed are: For settlements page, we have 2 buttons: 1. "Confirm" button 2. "Reject" button when these buttons are clicked at the same by 2 users, the system handles both events differently instead of considering one event.
– CCC
Nov 14 '18 at 8:13
@Dominique Fortin, 2. When 2 users click "return" button at the same time, the system considers both clicks as 2 different clicks. Thus leading to return duplicates in transaction entries table !
– CCC
Nov 14 '18 at 8:20
|
show 5 more comments
1
1
1
my system is all about sending remittances to different places in the world. i sometimes find a scenario by which 2 different users do the following:
- User1(the remittance payer) clicks "pay" button for paying it.
- User2(the remittance sender) clicks "return" button for returning it.
These 2 events occur at the same time thus leading to the system confused with which event is to be considered/handled first !
Q: Is there a way of considering one event by ignoring the other event ?
Any help is much appreciated.
Thanks in advance.
javascript jquery node.js
asked Nov 14 '18 at 7:30
CCCCCC
198
my system is all about sending remittances to different places in the world. i sometimes find a scenario by which 2 different users do the following:
- User1(the remittance payer) clicks "pay" button for paying it.
- User2(the remittance sender) clicks "return" button for returning it.
These 2 events occur at the same time thus leading to the system confused with which event is to be considered/handled first !
Q: Is there a way of considering one event by ignoring the other event ?
Any help is much appreciated.
Thanks in advance.
javascript jquery node.js
javascript jquery node.js
asked Nov 14 '18 at 7:30
CCCCCC
198
asked Nov 14 '18 at 7:30
CCCCCC
198
asked Nov 14 '18 at 7:30
CCCCCC
198
asked Nov 14 '18 at 7:30
CCCCCC
198
asked Nov 14 '18 at 7:30
CCCCCC
198
198
'at the same time' isn't a thing in JS, the events should be two different calls into the event handler which happen one after another. even if an event occurs at the same exact nanosecond, the js event handler will still have to process them separately
– RenaissanceProgrammer
Nov 14 '18 at 7:43
In the future Node will be multithreaded, but for now it's single threaded so you can't have race condition because all the events are put in a queue for serialized handling.
– Dominique Fortin
Nov 14 '18 at 7:48
@CCC Please give an example of the unwanted behavior that you observed.
– Dominique Fortin
Nov 14 '18 at 7:53
@Dominique Fortin, similar unwanted behaviors observed are: For settlements page, we have 2 buttons: 1. "Confirm" button 2. "Reject" button when these buttons are clicked at the same by 2 users, the system handles both events differently instead of considering one event.
– CCC
Nov 14 '18 at 8:13
@Dominique Fortin, 2. When 2 users click "return" button at the same time, the system considers both clicks as 2 different clicks. Thus leading to return duplicates in transaction entries table !
– CCC
Nov 14 '18 at 8:20
|
show 5 more comments
'at the same time' isn't a thing in JS, the events should be two different calls into the event handler which happen one after another. even if an event occurs at the same exact nanosecond, the js event handler will still have to process them separately
– RenaissanceProgrammer
Nov 14 '18 at 7:43
In the future Node will be multithreaded, but for now it's single threaded so you can't have race condition because all the events are put in a queue for serialized handling.
– Dominique Fortin
Nov 14 '18 at 7:48
@CCC Please give an example of the unwanted behavior that you observed.
– Dominique Fortin
Nov 14 '18 at 7:53
@Dominique Fortin, similar unwanted behaviors observed are: For settlements page, we have 2 buttons: 1. "Confirm" button 2. "Reject" button when these buttons are clicked at the same by 2 users, the system handles both events differently instead of considering one event.
– CCC
Nov 14 '18 at 8:13
@Dominique Fortin, 2. When 2 users click "return" button at the same time, the system considers both clicks as 2 different clicks. Thus leading to return duplicates in transaction entries table !
– CCC
Nov 14 '18 at 8:20
'at the same time' isn't a thing in JS, the events should be two different calls into the event handler which happen one after another. even if an event occurs at the same exact nanosecond, the js event handler will still have to process them separately
– RenaissanceProgrammer
Nov 14 '18 at 7:43
'at the same time' isn't a thing in JS, the events should be two different calls into the event handler which happen one after another. even if an event occurs at the same exact nanosecond, the js event handler will still have to process them separately
– RenaissanceProgrammer
Nov 14 '18 at 7:43
In the future Node will be multithreaded, but for now it's single threaded so you can't have race condition because all the events are put in a queue for serialized handling.
– Dominique Fortin
Nov 14 '18 at 7:48
In the future Node will be multithreaded, but for now it's single threaded so you can't have race condition because all the events are put in a queue for serialized handling.
– Dominique Fortin
Nov 14 '18 at 7:48
@CCC Please give an example of the unwanted behavior that you observed.
– Dominique Fortin
Nov 14 '18 at 7:53
@CCC Please give an example of the unwanted behavior that you observed.
– Dominique Fortin
Nov 14 '18 at 7:53
@Dominique Fortin, similar unwanted behaviors observed are: For settlements page, we have 2 buttons: 1. "Confirm" button 2. "Reject" button when these buttons are clicked at the same by 2 users, the system handles both events differently instead of considering one event.
– CCC
Nov 14 '18 at 8:13
@Dominique Fortin, similar unwanted behaviors observed are: For settlements page, we have 2 buttons: 1. "Confirm" button 2. "Reject" button when these buttons are clicked at the same by 2 users, the system handles both events differently instead of considering one event.
– CCC
Nov 14 '18 at 8:13
@Dominique Fortin, 2. When 2 users click "return" button at the same time, the system considers both clicks as 2 different clicks. Thus leading to return duplicates in transaction entries table !
– CCC
Nov 14 '18 at 8:20
@Dominique Fortin, 2. When 2 users click "return" button at the same time, the system considers both clicks as 2 different clicks. Thus leading to return duplicates in transaction entries table !
– CCC
Nov 14 '18 at 8:20
|
show 5 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53295088%2fhow-to-handle-click-events-happening-at-the-same-time-in-jquery%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53295088%2fhow-to-handle-click-events-happening-at-the-same-time-in-jquery%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
'at the same time' isn't a thing in JS, the events should be two different calls into the event handler which happen one after another. even if an event occurs at the same exact nanosecond, the js event handler will still have to process them separately
– RenaissanceProgrammer
Nov 14 '18 at 7:43
In the future Node will be multithreaded, but for now it's single threaded so you can't have race condition because all the events are put in a queue for serialized handling.
– Dominique Fortin
Nov 14 '18 at 7:48
@CCC Please give an example of the unwanted behavior that you observed.
– Dominique Fortin
Nov 14 '18 at 7:53
@Dominique Fortin, similar unwanted behaviors observed are: For settlements page, we have 2 buttons: 1. "Confirm" button 2. "Reject" button when these buttons are clicked at the same by 2 users, the system handles both events differently instead of considering one event.
– CCC
Nov 14 '18 at 8:13
@Dominique Fortin, 2. When 2 users click "return" button at the same time, the system considers both clicks as 2 different clicks. Thus leading to return duplicates in transaction entries table !
– CCC
Nov 14 '18 at 8:20