Data storage for remote content whitelist

Andrew Sutherland asutherland at
Tue Sep 6 21:39:24 UTC 2011

On 09/06/2011 02:29 PM, David Bienvenu wrote:
> Indexed DB is an other possibility -

IndexedDB would be a good choice, especially assuming we migrate to 
using LevelDB to back it sooner than later.  (It currently uses 
SQLite.)  Indeed, I would probably recommend using IndexedDB for 
everything instead of SQLite at this point.

An annoying glitch at this point in time is that IndexedDB is currently 
hooked up in such a way that it's only accessible from 'content' pages 
rather than chrome ( 
).  If you jump through some hoops, it's tractable, it's just slightly 
ugly.  It probably wouldn't take a ton of work to fix the deficiency.

> On the other hand, my understanding is we're moving it out of the AB so
> that you don't need a card in the AB in order to whitelist someone. That
> seems like that could be solved by having cards that don't show up for
> normal purposes...

Yeah, I was going to ask the rationale for not doing something along 
these lines, especially if the backend wants the answer synchronously.


More information about the tb-planning mailing list