Re: Nothing new @Reg
Hey man, I'm just using your terminology:
" Hey, I've got an object storage system, and didn't know it! The "globally unique identifier" starts with "/home/peter/Media..." or some such, and each object has some metadata that can be seen using examination tools like "ls -l", "istat" and "file""
My point was that an object can be instantiated in one location with certainty that it will not clash with an object in another location. That is all.
Once it is instantiated it can be replicated to the other locations. If it needs to be accessed from another location BEFORE it has been replicated then it can be requested from the originating location (and now it has been replicated).
"How global is global? If it's really global, what is the arbitration system to make sure that there are no collisions with other systems and organizations? And are objects immutable so that you have to version them as part of their globally unique identifier?. I cannot really believe that there are people who believe that a non-hierarchical unique identifier is really possible at any scale."
I am just answering your questions. A local originator being part of the key prevents collision between locations (and a local arbitrator prevents local collisions). If they are immutable then replication is very easy.
I'm not detailing the working of any actual system. Just suggestions as to how they *could* work.
I'm not suggesting that you should use then for any particular workload, just that their properties may be useful some workloads.
Take it or leave it. Meh.