CosmosDb WrongExpectedVersionException Resync semantics about equinox HOT 3 CLOSED

Update this issue:
We can override consistency level after upgrade Document.Core to 2.0.0 preview.
However, strong consistency is not supported for cosmosDB with multi-region right now.
The consistency level which is stronger than session consistency(what we are using right now) is bounded staleness but It doesn't have a guarantee that one can read their own write while session consistency does. Without the guarantee that one can read their own write, We can not pass the integration test in Foldunk.
So for resync, we can only do retry for equinox right now.

from equinox.

Another opportunity (which is probably goldplating, as conflict is not a frequent thing...), is to have the write operation include the conflicting data in the response immediately to avoid an immediate roundtrip to obtain the data.

from equinox.

Fixed (and implemented second idea) in #42 - all writing is now through a stored procedure which gates the adding of items; this same stored procedure also emits the conflicting events.

from equinox.