On Fri, Dec 01, 2006 at 11:46:41PM -0800, Ken Taylor wrote:
I think this is definitely needed and may even be worth getting a sketch of
it into s5 if possible. Even something simple, like being able to
temporarily lock an object for editing, would make programming in a
distributed writable
Let me contribute one more animal to the vobject graph language
zoo... In my own framework I currently map VOS to RDF (Resource
Description Format). The mapping is somewhat ad-hoc, but works nicely
for me. I'd appreciate comments and suggestions!
Mapping VOS graphs to RDF is
Oops, sorry for the weird formatting. Apple Mail somehow messed up my
copy/paste action there.
Reviewing this, I remember a few things that struck my attention
while I was working with barebones VOS (e.g. without the official
codebase). Maybe it is not too late to consider this for the s5
Peter Amstutz wrote:
We probably need some kind of locking and/or transactions eventually
anyhow. That's another can of worms.
I think this is definitely needed and may even be worth getting a sketch of
it into s5 if possible. Even something simple, like being able to
temporarily lock an object
