W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

Re: [IndexedDB] How to recover data from IndexedDB if the origin domain don't exist anymore?

From: <piranna@gmail.com>
Date: Wed, 9 Jan 2013 19:06:41 +0100
Message-ID: <CAKfGGh0k94ZFr0fp3GJE6gyiMXA5iYTca3pF=t+P+mc+RY5N7Q@mail.gmail.com>
To: "SULLIVAN, BRYAN L" <bs3131@att.com>
Cc: Todd Blanchard <toddvblanchard@gmail.com>, "public-webapps@w3.org" <public-webapps@w3.org>
>
>
> Perhaps what we need (and I am ducking as I say this) is a meta tag for
> web pages, e.g. ****
>
> <meta name="previously-known-as" content="http://olddomain.com:80">****
>
> or ****
>
> <meta name="same-as" content="http://olddomain.com:80">****
>
> ** **
>
> This could then be used by the browser to allow the user (always in
> control of such decisions) to grant the new origin to take ownership of (or
> at least gain read/write access to) any existing data of the old origin.**
> **
>
> **
>
PubNub API has the hability to add a 'origin' argument on its constructor (
http://stackoverflow.com/questions/12843178/cant-publish-via-pubnub-origin-is-not-allowed-by-access-control-allow-origin,
the page it's from Stackoverflow but show a similar problem and it's solved
by PubNub staff, so I think it shows correctly how it works) that's the one
asociated with the database, and my proposition was more related on this
way, altohugh don't know up to what point it's not standard way to do
things.

Related to your proposition with meta-tags, content attribute would be
filled via Javascript so users would set the URL of the non-existent domain
(by hand or a pre-filled dropdown list)? Obviously, asking for permissionsn
before accessing to it...

And also regarding to permissions, it would be good to see about just allow
read access to the database on other domain (for example for backup and/or
copy it's content on the new domain database), take ownership of the
database from the old domain on the new one (like "upgrading" it with your "
previously-known-as" meta-tag example) or directly allow plain sharing of
the database between several web domains (like with your "same-as" meta-tag
example or a sharing "magic word", for example like
indexedDB.open('myAwesomeDatabase',
'Hocus Pocus magic word')). This last point would be the most dangerous
since would open a door por web advertising like the one that happened with
cookies, but maybe it would be solved allowing to the databases only be
opened as "shared" if they are invoked from the current page domain instead
of third party ones (something like the filter on the browser to don't
allow third party cookies).


-- 
"Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton
de sitios diferentes, simplemente escribe un sistema operativo Unix."
 Linus Tordvals, creador del sistema operativo Linux
Received on Wednesday, 9 January 2013 18:07:29 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT