Комментарии:
Thank you!
ОтветитьOne question though: is the CacheService thread-safe? I mean, if we both update and read data from the same ScriptCache, we should use a lock for both reading and updating, right? Or else we could read some data that is already being updated by another thread. Is that correct?
ОтветитьThanks for a brilliant demonstration of why and when this feature matters. I struggled to grasp it until I watched your chapter 8 series on Lock Service 🙏
ОтветитьThank you for this great video! It will definitely help me with my current project.
Ответить😀 How to lock two functions at the same time using script lock 🔒 ? Please help 🙏
Ответитьvery nice video. thank you!
ОтветитьMuch appreciated!
ОтветитьThank you so much for this video
ОтветитьThat was well explained and helpful, thank you
ОтветитьGreat explanation, David. Thanks a lot.
ОтветитьThank you
ОтветитьThank you so much for this video. I had some problems in my webapp with 50 people without that lock function. This really helps!
ОтветитьAwesome, thanks a lot David. 👏
Ответитьbro i search code for lock eniter row depend on date if you known any code tell to me
ОтветитьI try this but when tried with 4 people execute the form like you have at exact same time, it only create 3 rows instead of 4. Why this happened and any solution?
ОтветитьExcellent videos, remember if you can enlarge the letter a little bit for future videos because it doesn't look good on notebooks. thanks.
ОтветитьThis implementation is a must when dealing with multi-user web app access. Thanks David!!! Much appreciated!
ОтветитьThank you very much for your video!
Ответитьhow to create hmtl page with password using appscript
ОтветитьThanks David for this course was very helpful.
I have 2 questions
First
why do you need the if statement (lock.hasLock) you're either way not able to continue with the code if your not able to get the lock.
Second
is there a need to release the lock if its by the end of my code or its being released automatically once the script is completed
Thanks again