Re:Web Locks API
by nitwit005 on Sunday November 10, 2024 @02:59PM
(#42102257)
How does a shared memory space work if you have different versions of scripts for the same domain?
[ Parent
| on HN ]
Re:Web Locks API
by horsawlarway on Sunday November 10, 2024 @08:11PM
(#42103777)
Same way a shared database works across multiple client versions as you roll out a new deployment.
Or the same way two completely different processes can access the same address space with shared memory IPC.
You aren't running in the same memory space, you're just communicating with a shared resource.
Why would that matter? The tabs don't share memory. Any code doesn't run when it tries to acquire a lot that another piece of code from another tab has already acquired. The two tabs don't even need to run the same app.
Well, it might matter for functionality in the application.
After you fix a lock-related bug for example, how do you deal with an open tab running a different version of your code that is erroneously misusing a lock?
You need to account for that when you release new code, yeah? Rename the lock maybe? Some other logic?
What are you imagining doing with these web locks apis?