[whatwg] Structured clone algorithm on LocalStorage
robert at ocallahan.org
Thu Sep 24 21:28:49 PDT 2009
On Fri, Sep 25, 2009 at 5:52 AM, Darin Fisher <darin at chromium.org> wrote:
> No, no... my point is that to the application developer, those "explicit"
> points will appear quite implicit and mysterious. This is why I called
> out third-party JS libraries. One day, a function that you are using
> might transition to scripting a plugin, which might cause a nested
> loop, which could then force the lock to be released. As a programmer,
> the unlocking is not explicit or predictable.
The unlocking around plugin calls is a problem, but it seems to me that any
given library function is much more likely start with a plugin-based
implementation and eventually switch to a non-plugin-based implementation
than the other way around.
Beyond plugins, I hope and expect that library functions don't suddenly add
calls to alert(), showModalDialog() or synchronous XHR.
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg