so the cache has 2 parts, the cache itself and a method ("the loader method") that populates the cache. So if i lookup "foo" in the cache and it doesn't have it, the loader method is called "getFoo" to retrieve that method and the cache automagically caches it for you

Hmm, I'm having trouble wrapping my head around this one. You don't have an example you could share? I'm imagining something like this:

cache.getCache({ name: 'testcache' })
        .get({
            key: 'testkey',
            loader: function(value) {
                return 'somevalue';
            }
        })

In the netsuite example it seems like they are loading a file from the file cabinet and searching for a specific value in the file. That seems like it defeats the purpose of the cache if you have to load the file cabinet file very time anyway.

I haven't used it since i switched jobs so i dont have an example but the loader method is only called if the value doesn't exist in the cache and once the function returns the value, it automagically caches it for you behind the scenes

Ok I got it. In case the cache gets removed after it's initially set the loader is called and repopulates it.

yeah the cache should always be populated through the loader method but thats the idea

Is there any good reason for using the

Cache.put(options)

method to populate the cache even when you have a loader on the

.get(options)

method?

its so you CAN do manual population

Got it, thanks.

yep np.. just make a simple script and give it a go. It took me longer than i'll admit to get it figured out.