goog.storage.Storage vs localStorage

439 views
Skip to first unread message

John Munro

unread,
May 14, 2013, 12:00:00 PM5/14/13
to closure-lib...@googlegroups.com
In the same way that the common availability of JSON.parse obviates goog.json.parse, is localStorage ubiquitous enough to use instead of goog.storage.Storage?

Assuming I don't care about IE6 etc...

Nathan Naze

unread,
May 14, 2013, 12:02:25 PM5/14/13
to closure-library
much of Closure that wraps native APIs is attempting to abstract
browser differences. If you know you're working a set of browsers
where localStorage is present, no need to use.

Nathan
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Closure Library Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to closure-library-d...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Johannes Nel

unread,
May 14, 2013, 12:04:31 PM5/14/13
to closure-lib...@googlegroups.com
A little side flung info; I saw this a while ago. 

I have not used it, but a quick glance told me it was written for AO, which made me pretty excited.


On Tue, May 14, 2013 at 5:00 PM, John Munro <ghos...@gmail.com> wrote:
In the same way that the common availability of JSON.parse obviates goog.json.parse, is localStorage ubiquitous enough to use instead of goog.storage.Storage?

Assuming I don't care about IE6 etc...

--
 
---
You received this message because you are subscribed to the Google Groups "Closure Library Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to closure-library-d...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
j:pn
\\no comment

John Munro

unread,
May 14, 2013, 12:22:57 PM5/14/13
to closure-lib...@googlegroups.com
The expiration and encryption functionality that Closure adds are useful additions to the base localStorage


On Tuesday, May 14, 2013 12:02:25 PM UTC-4, Nathan Naze wrote:
much of Closure that wraps native APIs is attempting to abstract
browser differences.  If you know you're working a set of browsers
where localStorage is present, no need to use.

Nathan

On Tue, May 14, 2013 at 12:00 PM, John Munro <ghos...@gmail.com> wrote:
> In the same way that the common availability of JSON.parse obviates
> goog.json.parse, is localStorage ubiquitous enough to use instead of
> goog.storage.Storage?
>
> Assuming I don't care about IE6 etc...
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Closure Library Discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to closure-library-discuss+unsub...@googlegroups.com.

Daniel Steigerwald

unread,
May 14, 2013, 9:05:24 PM5/14/13
to closure-lib...@googlegroups.com
Using of goog.storage.mechanism.IEUserData should be determined by compiler define.


To unsubscribe from this group and stop receiving emails from it, send an email to closure-library-d...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages