I just got word that localStorage and localDb data are no longer
persistent in iOS as of version 5.0.1. The files have been moved to a
location in cache which is regularly cleaned.
I am still wrapping my head around what this means for my app and for
my use of persistenceJS. First thought is that there is no rescue,
since even saveToLocalStorage won't help now.
Anyone with a more optimistic perspective, or should I now switch to
indexedDb for good?
My understanding is Persistence.js uses the WebSQL Database which in turn uses SQLite. I don't see how localStorage or localDb effects this.
Friday, March 23, 2012, 2:55:38 AM, you wrote:
W> I just got word that localStorage and localDb data are no longer W> persistent in iOS as of version 5.0.1. The files have been moved to a W> location in cache which is regularly cleaned.
W> I am still wrapping my head around what this means for my app and for W> my use of persistenceJS. First thought is that there is no rescue, W> since even saveToLocalStorage won't help now.
W> Anyone with a more optimistic perspective, or should I now switch to W> indexedDb for good?
-- Best regards, Neville Franks, Author of Surfulater - Your off-line Digital Reference Library Soft As It Gets Pty Ltd, http://www.surfulater.com - Download your copy now. Victoria, Australia Blog: http://blog.surfulater.com
If you read the linked post it also talks about WebSQL. Its data will still be persistent, but may be cleaned up whenever required. Effectively, on iOS, WebSQL is now a structured caching solution. Indeed disturbing. The only solution I see is sync. Sync your data to a server regularly and restore if necessary. If you don't store a lot of data you can use persistence.dump to create a large JSON object you could send to the sever and easily persistence.load again later.
But yeah. This kind of sucks.
-- Zef
Sent from my iPhone.
On Thursday 22 March 2012 at 20:21, Neville Franks wrote:
> My understanding is Persistence.js uses the WebSQL Database which in > turn uses SQLite. I don't see how localStorage or localDb effects this.
> Friday, March 23, 2012, 2:55:38 AM, you wrote:
> W> I just got word that localStorage and localDb data are no longer > W> persistent in iOS as of version 5.0.1. The files have been moved to a > W> location in cache which is regularly cleaned.
> W> I am still wrapping my head around what this means for my app and for > W> my use of persistenceJS. First thought is that there is no rescue, > W> since even saveToLocalStorage won't help now.
> W> Anyone with a more optimistic perspective, or should I now switch to > W> indexedDb for good?
> -- > Best regards, > Neville Franks, Author of Surfulater - Your off-line Digital Reference Library > Soft As It Gets Pty Ltd, http://www.surfulater.com - Download your copy now. > Victoria, Australia Blog: http://blog.surfulater.com
This brings me to a question for Zef... How difficult/easy would it be to modify persistence.js (for people who are already using it in their projects) such that persistence.js uses this DB file insted of the file stored in the cache (in iOS 5.1 and above)??? I'll be looking into it as well... but Zef you would be the right person to tell this...
On Friday, 23 March 2012 13:10:32 UTC+5:30, Zef Hemel wrote:
> If you read the linked post it also talks about WebSQL. Its data will > still be persistent, but may be cleaned up whenever required. Effectively, > on iOS, WebSQL is now a structured caching solution. Indeed disturbing. The > only solution I see is sync. Sync your data to a server regularly and > restore if necessary. If you don't store a lot of data you can use > persistence.dump to create a large JSON object you could send to the sever > and easily persistence.load again later.
> But yeah. This kind of sucks.
> -- Zef
> Sent from my iPhone.
> On Thursday 22 March 2012 at 20:21, Neville Franks wrote:
> My understanding is Persistence.js uses the WebSQL Database which in
> turn uses SQLite. I don't see how localStorage or localDb effects this.
> Friday, March 23, 2012, 2:55:38 AM, you wrote:
> W> I just got word that localStorage and localDb data are no longer
> W> persistent in iOS as of version 5.0.1. The files have been moved to a
> W> location in cache which is regularly cleaned.
> W> I am still wrapping my head around what this means for my app and for
> W> my use of persistenceJS. First thought is that there is no rescue,
> W> since even saveToLocalStorage won't help now.
> W> Anyone with a more optimistic perspective, or should I now switch to
> W> indexedDb for good?
> --
> Best regards,
> Neville Franks, Author of Surfulater - Your off-line Digital Reference > Library
> Soft As It Gets Pty Ltd, http://www.surfulater.com - Download your copy > now.
> Victoria, Australia Blog: http://blog.surfulater.com
It looks like the API is compatible with WebSQL, so I'd say it wouldn't be difficult at all. Just requires copying and adapting the WebSQL store a little bit.
-- Zef
Sent from my iPhone.
On Friday 23 March 2012 at 21:05, Sudhakar Fomra wrote:
> This brings me to a question for Zef... How difficult/easy would it be to modify persistence.js (for people who are already using it in their projects) such that persistence.js uses this DB file insted of the file stored in the cache (in iOS 5.1 and above)??? I'll be looking into it as well... but Zef you would be the right person to tell this...
> On Friday, 23 March 2012 13:10:32 UTC+5:30, Zef Hemel wrote: > > If you read the linked post it also talks about WebSQL. Its data will still be persistent, but may be cleaned up whenever required. Effectively, on iOS, WebSQL is now a structured caching solution. Indeed disturbing. The only solution I see is sync. Sync your data to a server regularly and restore if necessary. If you don't store a lot of data you can use persistence.dump to create a large JSON object you could send to the sever and easily persistence.load again later.
> > But yeah. This kind of sucks.
> > -- Zef
> > Sent from my iPhone.
> > On Thursday 22 March 2012 at 20:21, Neville Franks wrote:
> > > My understanding is Persistence.js uses the WebSQL Database which in > > > turn uses SQLite. I don't see how localStorage or localDb effects this.
> > > Friday, March 23, 2012, 2:55:38 AM, you wrote:
> > > W> I just got word that localStorage and localDb data are no longer > > > W> persistent in iOS as of version 5.0.1. The files have been moved to a > > > W> location in cache which is regularly cleaned.
> > > W> I am still wrapping my head around what this means for my app and for > > > W> my use of persistenceJS. First thought is that there is no rescue, > > > W> since even saveToLocalStorage won't help now.
> > > W> Anyone with a more optimistic perspective, or should I now switch to > > > W> indexedDb for good?
On Sunday, 25 March 2012 17:50:25 UTC+5:30, Zef Hemel wrote:
> It looks like the API is compatible with WebSQL, so I'd say it wouldn't > be difficult at all. Just requires copying and adapting the WebSQL store a > little bit.
> -- Zef
> Sent from my iPhone.
> On Friday 23 March 2012 at 21:05, Sudhakar Fomra wrote:
> This brings me to a question for Zef... How difficult/easy would it be to > modify persistence.js (for people who are already using it in their > projects) such that persistence.js uses this DB file insted of the file > stored in the cache (in iOS 5.1 and above)??? I'll be looking into it as > well... but Zef you would be the right person to tell this...
> On Friday, 23 March 2012 13:10:32 UTC+5:30, Zef Hemel wrote:
> If you read the linked post it also talks about WebSQL. Its data will > still be persistent, but may be cleaned up whenever required. Effectively, > on iOS, WebSQL is now a structured caching solution. Indeed disturbing. The > only solution I see is sync. Sync your data to a server regularly and > restore if necessary. If you don't store a lot of data you can use > persistence.dump to create a large JSON object you could send to the sever > and easily persistence.load again later.
> But yeah. This kind of sucks.
> -- Zef
> Sent from my iPhone.
> On Thursday 22 March 2012 at 20:21, Neville Franks wrote:
> My understanding is Persistence.js uses the WebSQL Database which in
> turn uses SQLite. I don't see how localStorage or localDb effects this.
> Friday, March 23, 2012, 2:55:38 AM, you wrote:
> W> I just got word that localStorage and localDb data are no longer
> W> persistent in iOS as of version 5.0.1. The files have been moved to a
> W> location in cache which is regularly cleaned.
> W> I am still wrapping my head around what this means for my app and for
> W> my use of persistenceJS. First thought is that there is no rescue,
> W> since even saveToLocalStorage won't help now.
> W> Anyone with a more optimistic perspective, or should I now switch to
> W> indexedDb for good?
> --
> Best regards,
> Neville Franks, Author of Surfulater - Your off-line Digital Reference > Library
> Soft As It Gets Pty Ltd, http://www.surfulater.com - Download your copy > now.
> Victoria, Australia Blog: http://blog.surfulater.com
