REST-based HTTP API - should I use WCF?

Question

I would like to encode REST-based HTTP APIs available from .NET and any other language like Python.

Should I use WCF for this? Or will it make it difficult for other languages ​​to interact with my API?

I want the server to have no state at all, and I want to be able to use persistent HTTP connections because a typical clinic will make many HTTP calls in a row. (maybe 2 hours in a row)

I am allowed to use .NET 4.

Answer 1

WCF has new material for supporting HTTP and REST. See http://wcf.codeplex.com/

intro http://www.bizcoder.com/index.php/2010/10/28/wcf-http/

Answer 2

WCF , , . REST Starter Kit Microsoft .

.NET REST - OpenRasta - , .

Answer 3

WCF, ASP.NET MVC WCF. :

http://weblogs.asp.net/cibrax/archive/2010/10/08/asp-net-mvc-wcf-rest-and-data-services-when-to-use-what-for-restful-services.aspx

. SO: ASP.NET MVC WCF

Answer 4

WCF. - ( ) , . . .