I thought about introducing the sync framework to a wider audience of developers. CodeProject is my favorite code sharing site, I’ve been a member for almost six years now. I remember when I first joined it was really small, but growing rapidly and I liked it a lot back then and still do now. CodeGuru is another site that I used to track but not so much recently; it is a great site but the sheer amout of ads per page and the poor organization of cotent is too much for my reading apptatie. Anyways, in this article, I give a quick overview to the sync services architecture, target scenrios, and brief description of different framework components. The sample application for the article is basically the very first demo of the offline-application series.
I am not sure you agree with me, but I tend to believe that developing sync application is a progressive process, you start by get things to work first. Better be a quick exercise. Seeing changes flow back and forth is very exciting, even to me, which encourages you to expand and add more application logic along with sync logic like conflict detection, client registeration, filtering… etc. That’s the way I structured the demo series and by the way it is not over yet; there are more demos for more advanced sync functionalities coming up.
My aim is to get more developers attention to sync and the value-add that sync brings to their data application. I am also enjoying the feedback I am receiving from developers through fourm, direct email, and other blogs. It is helping me understand the scenrios that they are targeting, their pain points, and what they like to see in future iterations of the framework. Keep them coming …
Feedback: Visit Sync Services Forum