The main benefit of using WCF Data Services (formerly ADO.NET Data Services, codename "Astoria) is that this is interoperable, which means it can be accessed from clients created in different technologies. Moreover standard WCF services offers the only exposed set of methods. Data Services, as implementation of OData protocol, offers the Resource to be queried and altered …
Let’s assume there is an application database and the various client applications developed in Windows Presentation Foundation, Silverlight, Windows Phone 7 and ASP.NET MVC 3. The database is either MS SQL Server or MS SQL Server CE. Now the potential customer may use one or many of these applications/platforms so the connections to the database must be performed from all of these clients. The following scenarios are considered. I tried to list some points that should be considered when choosing particular connection approach. The pictures represents the general architecture of the approach.
In this article I would like to show you my implementation and approach for using abstract repository no matter if the client is connecting directly to the database using Entity Framework, over WCF service or WCF Data Services (WCFDS) service.
Recently I needed to do some research on the topic of authentication, authorization and related stuff. After spending quite some time on it, I was pretty depressed – one would imagine, that a topic so common has already been handled in a standardized, common and comfortable (both for the user and the developer) way – well, it hasn’t, or do I demand to much?