Such approach is not feasible for the following reasons:
Very similar "technology" is Data.Heap
IReplicable will necessitate double abstracting everything multiple times
It is hard to replicate something too abstract, as IReplictable does not have enough logical constraints to make it work
How do you write something too abtstract? If it is not DataDoc
If it is datadoc then why not just build Heap?
How do you implement server replication for "any" technology - thats what essentially Heap is
The conclusion is simple: this namespace Data.Replication is probably not needed and instead the data.Heap project should be continued instead with all of its concretions (e.g. use HeapObject, CRDT) , then Adlib et al may use DataHeap under the hood.
It is very expensive and complex to move "data replication" out of Data.Heap as it is a senseless endeavor.
Such approach is not feasible for the following reasons:
The conclusion is simple: this namespace
Data.Replicationis probably not needed and instead the data.Heap project should be continued instead with all of its concretions (e.g. use HeapObject, CRDT) , then Adlib et al may use DataHeap under the hood. It is very expensive and complex to move "data replication" out ofData.Heapas it is a senseless endeavor.