Hi,<br><br><div class="gmail_quote">On Wed, Aug 10, 2011 at 9:51 AM, DongWoo Im <span dir="ltr"><<a href="mailto:dw.im@samsung.com">dw.im@samsung.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<p><span lang="EN-US">Dear Andrei.<br>Thanks for your reply.</span></p>
<p><span lang="EN-US"></span> </p>
<p><span lang="EN-US">You said the redundant implementation is an intentional decision to give freedom to browser vendors.<br>You've written the spec. of geolocation, so that must be the intention of the editor.</span></p>
<p><span lang="EN-US"></span> </p>
<p><span lang="EN-US">However, I still think that is slightly inefficient.</span></p>
<p><span lang="EN-US">I think this way could be possible.</span></p>
<p><span lang="EN-US">Let's make the database management - read, write, and refer - in WebCore.</span></p>
<p><span lang="EN-US">We can also give freedom to browser vendors to decide the configuration of the database by implementing the port layer.<br>They can decide how long the permissions will live in database, offer the unique interface to the user, or even disable the database.</span></p>
<p><br></p></div></blockquote><div>As you say, the database schema will be depend on how the permissions are implemented: Safari grants permissions that expire after a while, while Android and Chromium store permissions until they are explicitly removed by users. Chromium also differentiates between permissions granted to an origin when its content is loaded as the top level document vs when it is loaded in a cross-origin iframe. I am therefore not sure what set of common functionality we could put in WebCore to make the effort worthwhile and actually gain anything. We already have wrappers for SQLite so it's very easy for each embedder to write the permission management code.</div>
<div><br></div><div>Thanks,</div><div>Andrei</div><div><br></div></div>