I'm glad to hear that somebody has been working on this issue!
After read your proposal and previous dicussion, I realized that such
locking mechanism doesn't have to be tied to specific storage mechanism,
and a promise-based API
is more general than a synchronous API.
在 2015年07月16日 01:12, J
Yeah, I think a standalone primitive for "asynchronous atomics". The
big risk is of course that deadlocks can occur, but there's no real
way to completely avoid that while keeping a flexible platform. These
deadlocks would be asynchronous, so no thread will hang, but you can
easily end up with two
Based on similar feedback, I've been noodling on this too. Here are my
current thoughts:
https://gist.github.com/inexorabletash/a53c6add9fbc8b9b1191
Feedback welcome - I was planning to send this around shortly anyway.
On Wed, Jul 15, 2015 at 3:07 AM, 段垚 wrote:
> Hi all,
>
> I'm developing an
Hi all,
I'm developing an web-based editor which can edit HTML documents locally
(stored in indexedDB).
An issue I encountered is that there is no reliable way to ensure that
at most one editor instance (an instance is a web page) can open a
document at the same time.
* An editor instance ma
