CODEWITHSUNDEEP
.netasp.netweb-servicesjsonsoap
Patrick Kafka
Patrick Kafka

Reputation: 9892

Best way to implement a Generic Web Service API

What is the best way to implement a open/cross platform web service API to an existing .NET App? Not being a strictly .NET friendly API. It already has ASP.NET exposed web services, but need to be built into an generic API allowing inserts, updates and deletes and returning results based on user criteria in standard SOAP, JSON or other common formats, similar to Google's Data API's.

Are there any frameworks designed for this or is it a build it from scratch project implementing each format/protocol manually?

Thanks.

Upvotes: 4

Views: 1694

Answers (4)

Atometa
Atometa

Reputation: 111

I don't think Agatha is what you are looking for. Don't get me wrong - it is great at it's intended purpose as a service layer for your app, but I don't think it works as well as a public api.

For any outward facing web api stuff on .NET I would strongly recommend ServiceStack.net. It meets all your requirements and then some.

The newly released ASP.Net Web API from Microsoft is looking to be a good choice in the future if you are on a project that constrains you from using third party options such as ServiceStack.

Upvotes: 2

Rob Fonseca-Ensor
Rob Fonseca-Ensor

Reputation: 15621

Leverage WCF Data Services (formerly ADO.Net Data services, formerly Astoria). If you need your own data service provider (instead of Linq to Entities for example), see Alex James' blog

Upvotes: 0

BennyM
BennyM

Reputation: 2856

Agatha Request Response service layer.

Upvotes: 2

Pablo Castilla
Pablo Castilla

Reputation: 2741

Take a look at RIA services.

http://code.msdn.microsoft.com/RiaServices

Upvotes: 0

Related Questions