Where are the WCF and ADO.Net Data services?

I am a little confused about ADO.Net data services.

Is it just for creating RESTful web services? I know that WCF is running in the SOAP world, but now I heard that it has good REST support. The same goes for ADO.Net data services, where you can make it work in the RPC model if you cannot look at everything from a resource-oriented view.

At least from the demos I saw recently, it looks like ADO.Net Data Services is built on the WCF stack on the server. Please correct me if I am wrong.

I'm not going to start a discussion of REST and SOAP, but I think things are not so crystal clear.

Any suggestions or recommendations for use where?

+5
source share
3 answers

In my opinion, ADO.Net data services are designed to create quiet services that are closely related to your domain model, that is, the models themselves are published, and then they talk about some form of DTO, etc.

Using it for RPC style services seems to be bad, although, unfortunately, even some very simple functions, such as the ability to perform filtered calculations, etc., are not available, which often means that you end up using some kind of RPC to meet the requirements of your customers i.e. you can display the paged grid, etc.

WCF 3.5 pre-SP1 RESTful, SP1 Uri, ATOMPub, , , , JSON, XML, ATOM , , , , CSV, URL , munging .., / .

WCF - , , .. URL-, , - - ADO.Net AtomPub.

-, , , , ADO.Net Data - (, ajax, silverlight), URL , ... REST (, MVC ), , , API ..

2 !

+2

WCF , . HTTP .

+1

, , .

:

0

All Articles