Ok, do you know how tmsu stores it's metadata? I found references to sqlite3 in the source. ROOT actually uses the filesystem AS database, it has no separate i

Ok, do you know how tmsu stores it's metadata? I found references to sqlite3 in the source. ROOT actually uses the filesystem AS database, it has no separate index files except the "link" ones and those only store a binary list of long id's to other files. ROOT has some features that are missing from tmsu though; like distributed real-time replication over async. HTTP (scales across continents). HTTP API with JSON support. User management and security. All of that within ~4000 lines of code. I built it to have a MMO database that doesn't need manual moving of data for region switching and backup while avoiding the sync. bottleneck of all other databases. Here are two sites that use it: http://talk.binarytask.com http://talk.binarytask.com and http://fuse.rupy.se http://fuse.rupy.se