Add driver override/selector about localforage

[peterbe]

If I'm not mistaken socket.io solves that by you settings an array as part of the options of the list of protocols to try (e.g. Websocket, Flash, long polling, etc) and it tries one at a time till they have all failed.

[jokeyrhyme]

I have a use case where I only want to use storage mechanisms with decent quotas. This is pretty much limited to IndexedDB and only WebSQL + Cordova. Browser-based WebSQL does not meet my needs.

As such, it would be terrific to be able to perform the necessary detection and force localForage to be limited to the desired set of drivers.

[tofumatt]

Yeah, in general I’ve considered the case that users want to opt-out of localStorage. I think I’ll start on said branch tonight ^_^

• tofumatt

On February 4, 2014 at 18:27:39, Ron Waldon ([email protected]) wrote:

I have a use case where I only want to use storage mechanisms with decent quotas. This is pretty much limited to IndexedDB and only WebSQL + Cordova. Browser-based WebSQL does not meet my needs.

As such, it would be terrific to be able to perform the necessary detection and force localForage to be limited to the desired set of drivers.

—
Reply to this email directly or view it on GitHub.

[fwenzel]

Cordova is an interesting use case because I seem to recall they wrap WebSQL for their storage API. Which means it'll never™ exist for Cordova + Firefox OS unless they change that API. Is "Cordova-based WebSQL" another storage adapter then?

[jokeyrhyme]

@fwenzel I already treat WebSQL in Cordova apps exactly the same as WebSQL in the browser, in terms of my API use. The only practical difference is that browsers have weird quirky quotas and related user prompts, whilst Cordova-enhanced WebSQL gives me more space than I would ever ask for.

So for my purposes, I wouldn't find any value in treating WebSQL differently within localForage based on the presence of Cordova.

[fwenzel]

Oh, I think I misunderstood you at first.