News for hackers. Stuff that matters.
Re:Principles of Content Addressing (2014) by falcolas on Tuesday August 04, 2015 @10:01PM (#10007650)
It strikes me that this is one of those "a square is a rectangle, but a rectangle is not always a square" moments. JCR seems like it fits into the content identification family; it uniquely identifies content by a hash (in the case of JCR that hash is also a path), but that hash is system dependent. That is, I can't go to a system B and ask for the hash(path) '/foo/bar' and expect to get the same content as I would on system A.

Cryptographic hashes, on the other hand, make it possible to use the same hash on multiple systems and get the same content (if that content is available).

Re:Principles of Content Addressing (2014) by chmike on Wednesday August 05, 2015 @04:26AM (#10008526)
You need an index to achieve that. The index will tell you where the information associated to the hash is stored. That index is in itself a distributed system.