There was a lot of interest around the reference data caching "delta" feature for OData when we shared it last year. We got pretty far in the design, but there were a few key questions around functionality and scoping that we really couldn't comfortably
answer without having some early implementations, and the community was not there yet. So we did not include this feature as part of OData V3.
However, the feature remains important to us, and continues to generate interest from the community. We are even aware of a few early implementations of the functionality. So it appears this is a great time to pick it back up and finish it off.
Did you get a chance to read the specification? How well does it address your scenarios?
In response to your question on two-way synchronization, the feature was designed around having a single "master" source of the data, with many local copies, as opposed to a true multi-master system like the Microsoft Sync Framework provides. However, OData
already has a mechanism for local copies to submit updates to a server, so it is certainly possible to build a read/write solution where the local data is maintained through deltas and local changes are optimistically submitted through existing update mechanisms.
Would that address your scenario, or do you need true multi-master synchronization?
Michael Pizzo Software Architect, Microsoft
Note that we've largely moved to the release forum for data services questions; we’re shutting down this pre-release forum and consolidating on the release forum for practicality, so if you have follow-up on this feature (or questions/comments on other features
of data services), please post there for a more timely response...
This posting is provided "AS IS" with no warranties, and confers no rights