Bloodhound: Results returned when LS cache is empty.

[richardkmichael]

Instead of lowering the ttl of a BH prefetch, I wanted to try allowing the user to empty the cache. At first, I naively tried clearing localStorage out from under BH, then also tried keeping a reference to the BH engine and using the PersistentStorage public API to clear it:

• <button onclick='localStorage.clear();'>
• <button onclick='engine.storage.clear();'>

Neither "work"; after clearing the storage, TA still displays suggestions.

I've looked through the code only a bit so far, and I'm guessing this is happening from memory (probably not flushed, although the cache itself is).

I hoped TA would cache miss, and fire another "prefetch" request. Failing a fired prefetch, I would expect 0 suggestions (empty cache, therefore no matches). I'm wondering if displaying suggestions when the cache is empty is a "bug"; or, more likely, a misunderstanding on my part? :-)

[jharding]

Hmm so it sounds like you're looking for the ability to refetch prefetch data on-demand? Is that correct?

[richardkmichael]

Yes, that's right.

On Mon, Feb 17, 2014 at 5:52 PM, Jake Harding [email protected]:

Hmm so it sounds like you're looking for the ability to refetch prefetch
data on-demand? Is that correct?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/694#issuecomment-35330557
.

[jharding]

Alright, cool. I've seen a handful of requests for that sort of ability so I'm thinking I may prioritize it for the next release.

[richardkmichael]

Wow, great, thanks!

Regarding "on-demand"; I could see this going a few ways:

• empty the cache, which would induce a fetch [when because of the cache miss]; or,
• an API method to do a fetch (I actually didn't think of this; maybe that's possible now?)

I'll wait to see your implementation.

On Mon, Feb 17, 2014 at 6:09 PM, Jake Harding [email protected]:

Alright, cool. I've seen a handful of requests for that sort of ability so
I'm thinking I may prioritize it for the next release.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/694#issuecomment-35331686
.