Built in locking or semaphore mechanism

no, the changes are instant… what it have to happen is to prevent fast systems to get there before glide update… so minimum 1 sec and is all good… you can test my system as long you want… i guarantee that it will never fail… like Jeff… he was working on same network with fast clicking… he was able to beat glide update… so i put 1 sec delay… and no more chances

:wink: all good

From what I saw in video is used a username and then the same username with a 2 on the end

Jeff is a pro… and great guy!

Here is a screen shot from the first video

The user logins look different to me.

Anyways…

sorry… i did not magnify it… you right

Would you mind sharing the technique you used?

thats will cost you good whisky! you might spent hours or even days to solve this problem… and it is a big chance that you wil not… so a good bottle of Scotch looks like a very good price… :wink:

1 Like

Not.

It does not solve my problem as I need it in a public app no logins. I do not know that it works, and still doubt it does in all cases, as maybe it works with 2 users but not 50.

No issues.

too low?

it works with multiple users, first one is blocking all others… but it has to be log in
i can work on non log in scenario.

New version, no sign-in required!
please test it… best result is to test from deferent devices or other window must be incognito… if same device and no incognito, it will work too but notifications will be unstable…but still you cant double book!

@Jeff_Hager what do you think about the no sign-in version?