TechEd - The new ADO.NET sync framework
Just enough time to blog this great new tool comming in some version of Ocra's (So that you know the timeprojectory :-) )
A session from Steve Lasker
Its a couple of classes on the server and on the client that you can derive you're own class from. The baseclass implements a lot of code to do basic synchronisation between server and client based on a couple of database constraints like mandatory columns (Who you can name youreself, so thay are not bad).
The ADO.NET is one piece of the puzzle; The synchronisation should in the future also include Files, XML, etc, etc. Although i don't know how they are thinking about synchronisation of XML or even worse, just regular files.
There are still a couple of (standard) things not implemented, like:
- How collisions between client and server updates are handled. There are a few build-in but they are the simple onces like "Last one wins" scenarios.
- Cascading changes. No comment on that one, but maybe i run into him later and ask him about that (Or find it on his blog I suppose.)
- Schema changes.
Witch i hate, because you would expect Microsoft to come up with some guidelining and implement that. I mean, they have the experience with outlook, activeSync, right?
The good thing is that the goals are (My interpretation btw):
- to produce a outlook like feeling for the user
- Do something between RDA and merge replication
- Listen to the developers while developing the framework.
Al-and-al i am very excited about this and just wanted to be te first to blog about it :-)