Could you give a few answers for this comment you made "The problem with OpenAccess free clients is that you loose all change tracking and lazy loading capability. Also the generation of minimal change sets is something you have to do by yourself."
Is there any obvious benefit over "change tracking" for disconnected/distributed client or is there any drawback lacking of change tracking at client?
What role does lazy loading play at client, since we need to load all objects in object graph once we retrieve from server? it would give exception at client if we didn't.
What do you mean minimal change sets to be done by myself? Could you give a sample?
I have to get these answers from you, because telerik is influencing over our architecture, unnecessarily, even overwrote WCF architecture, you know telerik always put their binaries in WCF objects, instead of pure serialized xml, so it is not possible to have telerik free service client. And if we force to use additional mapping layer between telerik powered data access layer and service layer, there are no more obvious benefits using telerik. we are just moving object data mapping task to object telerik mapping task.
Please let us have a few suggestions, it would be most valuable to us.