This question is locked. New answers and comments are not allowed.
Hi, i have a need for an application with a desynchronized mode.
My application is a client-server application, with the Database on the server side (SQL SERVER).
and a SQL CE in client side.
I was planning to use Microsoft Sync Framework, but i saw that ORM had a "desync" functionality.
Can u explain me, what are the advantages of Telerik ORM Desync mode that Microsoft Sync Framework doesn't have ?
If i want to convice someone to use telerik ORM instead of MSF (which is free , simple to implement and full of example) what can i tell him?
Thx you.
My application is a client-server application, with the Database on the server side (SQL SERVER).
and a SQL CE in client side.
I was planning to use Microsoft Sync Framework, but i saw that ORM had a "desync" functionality.
Can u explain me, what are the advantages of Telerik ORM Desync mode that Microsoft Sync Framework doesn't have ?
If i want to convice someone to use telerik ORM instead of MSF (which is free , simple to implement and full of example) what can i tell him?
Thx you.
1 Answer, 1 is accepted
0
Hello Tgaud,
i think the main difference is that the MS Sync Framework is a much broader, thus more complex to use API. OpenAccess support for disconnected clients however uses only a few additional classes focusing on synchronizing offline changes to the connected world with the main API class being the ObjectContainer. This container implements a common interface with the main connected API, the ObjectScope. Therefore the gap between online and offline API is minimal. Also, the efforts needed to push changed, added and removed objects back into the connected world is minimized for you.
Regards,
Thomas
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
i think the main difference is that the MS Sync Framework is a much broader, thus more complex to use API. OpenAccess support for disconnected clients however uses only a few additional classes focusing on synchronizing offline changes to the connected world with the main API class being the ObjectContainer. This container implements a common interface with the main connected API, the ObjectScope. Therefore the gap between online and offline API is minimal. Also, the efforts needed to push changed, added and removed objects back into the connected world is minimized for you.
I also think, our API is more appropriate for limited environments as there is no dependency on file I/O.
Regards,
Thomas
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.