Thread safety
adrianmay opened this issue · comments
Two frames running the counter demo demonstrate thread safety problems. To solve them, the constructor will have to take a callback and somehow lock the name of a persistent while it's being built or modfied. The existing interface can continue to be supported but have thread safety warnings all over it.
Fixed just by removing the last setTimeout and doing it synchronously instead. That makes the whole ss thing redundant.