Idea: keep clientside js in localStorage

#1

Post by dominictarr » Tue, Apr 24, 2012, 4:27 AM UTC

client side javascripters aim for minimal code, to optimise load times; but what if you didn't have to worry about that? My idea is to store slowly changing assets in localStorage and then just have a tiny js that loads them into the page.

has anyone attempted this before?

Re: Idea: keep clientside js in localStorage

#2

Post by daegloe » Tue, Apr 24, 2012, 4:37 AM UTC

Is this really necessary when you already have browser caching? Which is fairly robust/mature across the market.

Re: Idea: keep clientside js in localStorage

#3

Post by willscott » Tue, Apr 24, 2012, 4:37 AM UTC

Why would this be preferable to an application cache manifest?

http://www.html5rocks.com/en/tutorials/appcache/beginner/

Re: Idea: keep clientside js in localStorage

#4

Post by dominictarr » Tue, Apr 24, 2012, 4:55 AM UTC

willscott wrote: post #3

Why would this be preferable to an application cache manifest? http://www.html5rocks.com/en/tutorials/appcache/beginner/

Ah, I didn't know about that. It might not be worthwhile since that already exists.

Except to give more precise, granular, control over updates. for example, (for example, with a merkle tree)

Re: Idea: keep clientside js in localStorage

#5

Post by dominictarr » Tue, Apr 24, 2012, 4:56 AM UTC

daegloe wrote: post #2

Is this really necessary when you already have browser caching? Which is fairly robust/mature across the market.

the problem with browser caching is that you cannot control when you want it to update, except with a timeout.

Re: Idea: keep clientside js in localStorage

#6

Post by abend » Tue, Apr 24, 2012, 5:09 AM UTC

dominictarr wrote: post #5

daegloe wrote: post #2

Is this really necessary when you already have browser caching? Which is fairly robust/mature across the market.

the problem with browser caching is that you cannot control when you want it to update, except with a timeout.

Timeout isn't the only way. You could set a version variable on pageload, and have a conditional version check on init. If the versions match and localstorage exists, load from localstorage, if not, grab from the server and update.