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

2013-01-28 Thread pira...@gmail.com
Another perspective about the problem: what about doing so with SharedIndexedDB in the same way of SharedWorkers? They allow to be accessed using a name, so it would be useful also here... If you need a better use case, I've been last saturday on the FirefoxOS App Days here at Madrid and talking

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

2013-01-16 Thread Kyle Huey
On Tue, Jan 15, 2013 at 3:57 PM, pira...@gmail.com pira...@gmail.comwrote: Ideas? Doubts? Comments? :-) The use case here is not compelling enough for this amount of complexity. IndexedDB is not guaranteed to be persistent so you can't really have a server-less webapp if you want reliability.

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

2013-01-15 Thread pira...@gmail.com
I have keep thinking about this topic and found a good solution: implement a CORS-like functionality. This way, when an IndexedDB database is created for the first time (like when browser ask to the user if s/he allow that the page store data on this machine) the developer could define an

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

2013-01-15 Thread Kyaw Tun
It will need to address limiting quota. How about ad firm collect data from multiple origins? Since user agent can delete IndexedDB data anytime, duplicate copy of IndexedDB data to be more persistant is not much meaningful. I think it is too much complex in security and privacy issue, but very

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

2013-01-09 Thread Kyaw Tun
In this situation, I will go with CouchDB. If used with IndexedDB, I will send data back JSON data to blob storage server like Google Cloud Storage or S3.

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

2013-01-09 Thread SULLIVAN, BRYAN L
:37 AM To: Todd Blanchard Cc: public-webapps@w3.org Subject: Re: [IndexedDB] How to recover data from IndexedDB if the origin domain don't exist anymore? Hacky, but nice trick (really, I like it :-) ). My question was more related about looking for a solution available for non-techies users

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

2013-01-09 Thread pira...@gmail.com
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

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

2013-01-08 Thread Todd Blanchard
As a practical matter, you could just make an entry in your /etc/hosts mapping the domain to localhost and write a web page that dumps the indexeddb as json. Serve that from your local web server and hit it with your browser. On Jan 8, 2013, at 7:08 AM, pira...@gmail.com wrote: I have been

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

2013-01-08 Thread pira...@gmail.com
Hacky, but nice trick (really, I like it :-) ). My question was more related about looking for a solution available for non-techies users, or give a warning about a (valid?) corner-case on the specification. (I'm going to add an issue on my project tracker to remind me to develop your idea, it's