drive-db

Nice one, I made something initially very similar to what I see you made with grille in drive-db[1]. However I changed from an 'update the data when you call a function' to 'set a maximum-life for the data' format now as I just found myself making that new version manually in every project. The name will be changed from `timetout` to `cache` though as the name is confusing even for me. When do you normally update the data? Are you using it in any public-facing project? Also a couple more of differences I've seen: - I store it in a file then retrieve from file or remote depending on the last time it was retrieved. This gives a mixed performance locally, but remotely not so much as server-server is quite fast. I might try storing in memory as you though, that should be way faster - I use a mongodb-like syntax for finding, which allows for (

I made a node.js package that does exactly this, a local cache in json with few hooks for data modification, and you can control when to update it to avoid timeouts [1] Then we used it as backens for a blog for my University team as we were already using Drive, being each entry a google docs document [2] [1] https://github.com/franciscop/drive-db [2] http://www.makersupv.com/