howardg

lol secure your own shady office network first before putting Android users at risk.

Huge kudos to Google for stopping a shady studio that can hardly secure its own network from releasing possibly security compromised apps to Android users!

The license is 2-clause BSD license.

Indeed, its wiki pages should have mentioned ACID properties, I noted the issue down here:

https://github.com/HouzuoGuo/tiedot/issues/4

Currently, tiedot's stance on ACID is similar to MongoDB's.

I have not spent enough time on the project to support redundancy in it, sorry. I totally agree that redundancy is a must-have if someone wants to use tiedot in serious scenarios, so I will definitely spend time on making this feature available.

Scalability on symmetric multiprocessing architectures has been seriously considered and implemented - basically, tiedot can demonstrate that more CPUs = more performance. However scaling by replication has not been considered yet.

Thanks for noticing the typo, it's been fixed and will commit shortly.

Regarding point 2, I made a note here:

https://github.com/HouzuoGuo/tiedot/wiki/Embedded-Usage

I experiment with different GOMAXPROCS settings on three machines and noticed that 1CPU does not run tiedot to its full potential, 3CPU seems to be slower than 2*CPU.

Thank you for the feedback! I noted down your recommendation here:

https://github.com/HouzuoGuo/tiedot/issues/3

And actually `go fmt` prefers to use tab over spaces ;)

Much appreciated! I will soon configure my web server to be compatible with `go get`.

according to my (limited) understanding, camlistore is a generic BLOB storage - which is not something tiedot addresses. tiedot is a generic unstructured data storage - more like CouchDB/Cassandra, it stores serialized JSON data rather than BLOB.

thank you, will do