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

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

From: <piranna@gmail.com>
Date: Wed, 16 Jan 2013 21:17:22 +0100
Message-ID: <CAKfGGh2DyGKjKwYVaDGy_HUB9Wd1JYRn46yB28xvPzt5k1RJ4g@mail.gmail.com>
To: "SULLIVAN, BRYAN L" <bs3131@att.com>, Todd Blanchard <toddvblanchard@gmail.com>, public-webapps@w3.org
Good point. You are right about the fact if you a server somewhere it's
fairly simple just to popula it, but if you don't have it I don't know what
would be a good solution. Maybe the problem is that I misconsidered the
posibility that databases can be removed at any time? IndexedDB is designed
just for remote server cache purposes? I know my use case (although real)
it's very extreme related to IndexedDB usage, but maybe others would be in
the same situation... Do you think it's better to do a local backup of the
database from time to time?

Sent from my Android cell phone, please forgive the lack of format on the
text, and my fat thumbs :-P
El 16/01/2013 13:34, "Kyle Huey" <me@kylehuey.com> escribió:

On Tue, Jan 15, 2013 at 3:57 PM, piranna@gmail.com <piranna@gmail.com>wrote:
>
>> 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.  Once you have server-side
> state there's no point in jumping through all these hoops if you switch
> domains, just repopulate the DB from the server.
>
> - Kyle
>



-- 
"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, 16 January 2013 20:18:10 GMT

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