document api and its guarantees about antidote

[cmeiklejohn]

Assigning to the first milestone. Who wants to pick this one up?

[bieniusa]

Started with documenting the API, but there is not enough information available.... See branch spec_fix.

Chris: You suggested removing the type from the read such that it resembles the append.
But it seems that the type is needed in order to materialise the object.
One solution would be to add the type to the stored object.
What do you think?

One other issue:
What about creation of CRDTs? Is it done during read or during append?

[aletomsic]

right now the creation of the crdt is done in the read.
I think it would be good to set the type on create (as manuel had suggested in the beginning) or just add an update operation with the type. In this last case, I think we have two options:

1. insert the type in every update.
2. just insert the type in the update that creates the crdt (this would be like a create).
   what do you think?
   best,

Alejandro Z. Tomsic
[email protected]

On Jun 23, 2014, at 0:10, bieniusa [email protected] wrote:

Started with documenting the API, but there is not enough information available.... See branch spec_fix.

Chris: You suggested removing the type from the read such that it resembles the append.
But it seems that the type is needed in order to materialise the object.
One solution would be to add the type to the stored object.
What do you think?

One other issue:
What about creation of CRDTs? Is it done during read or during append?

—
Reply to this email directly or view it on GitHub.

[runesl]

We should not distinguish initial update from subsequent updates in the API, as CRDTs are all about ensuring the same behaviour nomatter the order of operations... So specify type on all updates.

To avoid different types with same id clashing, we can use a combined key internally: key_type. This would allow CRDTs with the same (external) key and different types to coexist.

[cmeiklejohn]

#69, just merged, provides this support. Document @bieniusa is authoring is addressing this issue in the subversion repository.