On Fri, Sep 25, 2009 at 5:52 AM, Darin Fisher <span dir="ltr"><<a href="mailto:darin@chromium.org">darin@chromium.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div><div></div>No, no... my point is that to the application developer, those "explicit"</div><div>points will appear quite implicit and mysterious. This is why I called</div><div>
out third-party JS libraries. One day, a function that you are using</div><div>might transition to scripting a plugin, which might cause a nested</div><div>loop, which could then force the lock to be released. As a programmer,</div>
<div>the unlocking is not explicit or predictable.</div></div></blockquote><div><br>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.<br>
<br>Beyond plugins, I hope and expect that library functions don't suddenly add calls to alert(), showModalDialog() or synchronous XHR.<br><br></div><div>Rob<br></div></div>-- <br>"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 53:5-6]<br>