Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Backward compatibility Microsoft Sync Framework 3.0 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Will the new version of the framework be backward compatible?

     I have many WM6 devices and Windows Desktop PCs that are already using the older version of the framework for synchronisation. I need to add new devices running Android and the new version of the framework. Is it going to be possible to have both versions running together?

    I read: http://msdn.microsoft.com/en-us/library/dd936971(SQL.110).aspx that is about 2.0 and 2.1. What about 2.1 and (3.0 on Android) compatibility?

    Thank-you

     

    Tuesday, October 26, 2010 2:44 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    The sample you link will not work on Android - it will only work on Windows Systems, since it requires the Sync Framework to be installed on the Client.

    Ganeshan is talking about the Sync Framework 4.0 (not 3.0) release, that includes a new HTTP based sync protocol. We are releasing a public CTP of 4.0 very soon.

    With the CTP, you can create and deploy a service that accepts and sends changes with HTTP calls, with the data load in OData format.

    Unlike previous releases however, the client does not need to have Sync Framework installed on it to sync and cache data on it. The client only need to track changes with a "dirty bit" on each item. Change enumeration for the client will thus mean that it enumerates all items with the "dirty bit" set. The service/server does all the metadata manipulation on behalf of the client.

    We will also provide samples that work on Windows Mobile 6.x, Windows Phone 7, Silverlight, iPhone and HTML5 - that should help you with how you could do this on Android.

    Please watch our forums/blog for announcements on the CTP.

    Wednesday, October 27, 2010 4:46 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi roberto.altieri

    Sync Framework 3.0 defines a new HTTP based sync protocol that uses OData as the wire format. This enables us to develop applications on any platform without installing the sync runtime on the client. SyncFx 3.0 would require you to host a WCF based sync service head that talks OData over the wire. This approach is different from what you are using today. However it should be possible for both approaches to co-exist.

    Also, Sync Framework 3.0 is an invitation only mode. Please send your request to msf30ctp at microsoft dot com with the sync scenario/s you want to support. We will follow up with you soon.

    SDE, Sync Framework - http://msdn.com/sync/
    • Marked as answer by Ganeshan Tuesday, October 26, 2010 4:59 PM
    • Unmarked as answer by Ganeshan Tuesday, October 26, 2010 4:59 PM
    • Proposed as answer by Ganeshan Tuesday, October 26, 2010 4:59 PM
    Tuesday, October 26, 2010 4:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Dear Ganeshan, thank-you for your replay. Does that mean that there are no changes in the metadata? 

    My understanding is that the Android client is a kind of "partial participant" that means that it will store the local database and the metadata even if (as you said) it won't store the sync framework runtime. So it is not a "simple participant" and it will be able to handle changes in the local storage. Is that true?

    I found here: http://code.msdn.microsoft.com/sync/Release/ProjectReleases.aspx?ReleaseId=3423 something about synchronization by using WCF service. It uses .Net. Is there a library to simplify the development on Android? How is it possible to implement the synchronization with WCF on Android? Using Java? Using NDK? 

    Best regards

    Roberto

    PS

    I sent that email twice but I didn't get an answer yet.

    Wednesday, October 27, 2010 9:24 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    The sample you link will not work on Android - it will only work on Windows Systems, since it requires the Sync Framework to be installed on the Client.

    Ganeshan is talking about the Sync Framework 4.0 (not 3.0) release, that includes a new HTTP based sync protocol. We are releasing a public CTP of 4.0 very soon.

    With the CTP, you can create and deploy a service that accepts and sends changes with HTTP calls, with the data load in OData format.

    Unlike previous releases however, the client does not need to have Sync Framework installed on it to sync and cache data on it. The client only need to track changes with a "dirty bit" on each item. Change enumeration for the client will thus mean that it enumerates all items with the "dirty bit" set. The service/server does all the metadata manipulation on behalf of the client.

    We will also provide samples that work on Windows Mobile 6.x, Windows Phone 7, Silverlight, iPhone and HTML5 - that should help you with how you could do this on Android.

    Please watch our forums/blog for announcements on the CTP.

    Wednesday, October 27, 2010 4:46 PM