Distributed Object Store
From Entuura
These are notes on a way to use the payload transport system to maintain a loosely coupled distributed database across all the nodes, where every node eventually has a local copy of the global database.
It is 1/10th baked.
Distributed object library (wild idea...)
Key -> data
key = hash(data)
data is a dictionary (Bencoded?)
well known attributes
date
creator
signature
lat/long/alt
prevver back pointer to the previous version
type
any app can create new attributes
New keys arrive from the network
Display frontends:
* Select all objects where , put on locally generated map
* Distributed view of Blog Objects
* Phone directory
Catchup request: "I have these" -> sends you the others
Questions
No security (except known authorship)
What if encrypted objects are only delivered to those who can read them?
Could underlie file dist service? New obj arrival
triggers scan of all objects and update of read-only file store
view of objects. Read-write?
(wild idea...)
* One way replication via iterations of patches
* Each iteration, a patch is made and dispatched via underlying system
* Center holds the patches, can't read them
* to subscribe, pull down all patches and apply them
(but you can only see them if A wants you to)
* If A is setup to share to B,C and D wants to see the repository later,
one of A,B,C declares a "restart", and makes a unified patch
visible to B,C,D and then A starts making patches for B,C,D from now on
What we really need is subversion where the central server can't see the content.
So, what if we relax that constraint for now? No, no, no. Start systems with as much security as possible, lose it inevitably later.
