Can my .NET web services be considered a RESTful frontend?
Happy New Year.
I have a bunch of SOAP Web Services. They all have HTTP POST and GET interfaces along with SOAP interface. I believe POST and GET are provided by default when building SOAP web services in .NET / Visual Studio.
These methods: (1) get information, for example, provide your username, password and transaction ID → get XML with your transaction status; (2) create a transaction by providing your username, password and some data -> get XML with transaction id.
My question is, would it be correct to say that I have a RESTful webservice for those Ruby guys?
source to share
Well, it could be POX, but for true REST, the URIs themselves will be representative of the requested data, eg / Orders / 12345; is this the case?
Also, the data returned will be data-oriented rather than performance-oriented (which is usually the norm for SOAP-based services). that is, the results will usually be directly related to the data.
Note that you can create REST services in .NET using ADO.NET Data Services (aka Astoria). This is part 3.5 SP1 and uses WCF under the hood. By default, full REST is available to Entity Framework, or request-only for any IQueryable
API. But you can also enable full REST in LINQ-to-SQL (or whatever for that matter) by implementing IUpdatable
. I'll cover this in a series starting here .
source to share