JSON Sync Issues

[MichaelDavis3]

Congratulations on getting 10.2 out the door!

I wonder if someone at ESRI could give a brief explainer of the mechanics behind the sync process being used for the beta offline GDB functionality?

We have been using our own offline data collection and sync framework via JSON files; and from a cursory browsing of the new 10.2 docs it looks like the new version might be using JSON to sync as well?  I noticed there is mention of sync failing mysteriously, which is an issue we've encountered using JSON and the feature service REST endpoint.  We've enabled a number of workarounds to mitigate the issue but I'm wondering if perhaps we are seeing the same phenomena.

Thanks!

[DiveshGoyal]

I don't think the problem you're seeing is related. It probably needs to be investigated independently.

The 10.2 sync functionality uses sqllite databases as the transport for exchanging data between the the service and the client. When you sync, the API creates a temporary database containing just the deltas, and sends it up to the server. The server also sends back deltas for anything that changed since the client last synced/created the database.

[MichaelDavis3]

That is great news!

Looking forward to converting some of our apps over to 10.2 to see how they perform.

-Mike

[DiveshGoyal]

Awesome. Let us know how it goes.