I've been trying to get my head around ADO Data Services and although I can see it is very compelling way to get/set raw data directly from a UI based client I'm uncertain how it should work in the Enterprise. If we ignore the end-user client for the moment and consider the business tier then I could see that in SOA you've got a nice abstraction based upon a very simple URI format. Ok, so we've got a number of choices about how we provide that abstraction but this is compelling because it's platform/language independent. Now if we bring the client back into the picture then I start to get a little confused. The majority of the examples are all about speed of development, "look how fast you can CRUD your data, drop this and wow off we go". Now this is nothing new, it's taken an age for binding to start talking to objects rather than data tables so I shouldn't expect the examples to change, however I'm not sure what the story is with ADO.DS. E.g. If I used MVC would the I call the busine ...
Go to the complete details ...