One of the great things about ADO.NET Data Services is the flexibility around consuming it. Being able to create a single service that can in turn be leveraged by different applications in different environments makes it a very powerful feature. Currently there are three client-libraries available:
- Standard .NET (for the lack of a better term)
- Silverlight
- ASP.NET AJAX
I’m curious which client environment people feel will prove to be the most useful. If you were to adopt ADO.NET Data Services and begin implementing it in your applications, which scenario would you see a data service fitting into best?
Would the ease of data service creation and consumption enable you to begin creating more AJAX-enabled web applications? Does the Silverlight data service client library motivate you to begin looking into developing data-centric Silverlight applications?
I’m interested to hear your thoughts…
I have been considering the AJAX portions.
I think that the most often application will be from AJAX. My biggest reason for this is simply numbers. There will be 100 times more pure AJAX mashups out there for ever RIA.
I do believe that Astoria is bringing some great power in the form of data to Silverlight and “Standard .NET”, but I think that those uses will be secondary to an AJAX client end.
I meant to say “pure AJAX, and also mashups” up in my comment above.
I doubt we’ll be doing Silverlight development anytime soon, but AJAX development is a growing need that data services seems to make easier.