blocks|key|3309837|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3309838|我听说使用WCF我们一定会在客户端使用微软的一些技术|blockquote|3309839|3309840|3309841|好吧，那你被骗了！|3309842|许多供应商和开源库都支持SOAP+--它是一个W3C标准，而不是微软特有的想法。|3309843|RESTful服务的一个很好的替代方案是ASP.NET+MVC，我发现了一种非常简单的方法，可以将方法直接公开为URL。|3309844|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|O|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|P|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|R|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|S|7|@]|8|@]|9|$]]|$1|J|3|K|4|5|6|T|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|U|7|@]|8|@]|9|$]]]|M|$]]

<blockquote>
 I've heard that using WCF we're bound
 to use some Microsoft technology at
 the client side
</blockquote>

Well, then you've been lied to!

Many vendors and open source libraries support SOAP - it's a W3C standard, not a Microsoft-specific idea.

One great alternative for a RESTful service is ASP.NET MVC, which I've found a very easy way to expose methods directly as URLs.

blocks|key|334709|text|有关java+-+wcf的互操作性，请查看Sun的Project+Tango+link|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|334710|entityMap|0|LINK|mutability|MUTABLE|url|http://java.sun.com/developer/technicalArticles/glassfish/ProjectTango/^0|13|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

For java - wcf interopibility check Sun's Project Tango
<a href="http://java.sun.com/developer/technicalArticles/glassfish/ProjectTango/" rel="nofollow noreferrer">link</a>

blocks|key|3309970|text|WCF为您提供了关于您正在/想要进行通信的方式的抽象级别。因此，您可以选择特定于Microsoft绑定，但也可以使用SOAP协议，或者同时使用两者，以便非Microsoft客户端能够通过fe进行通信。SOAP和其他客户端可以使用更健壮的方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3309971|至于REST，你可以看看Hanselman在NDC+here上的演讲。它可能不会直接回答你的问题，但它可能会给你指出一些东西。|offset|length|3309972|至于替代方案，除了web服务之外，我没有看到任何可以在.NET上运行的东西(但是，因为WCF给你提供了所有这些，而且更多，所以我宁愿把它看作是一种更老的方式，而不是真正的替代方案)。|3309973|entityMap|0|LINK|mutability|MUTABLE|url|http://media01.smartcom.no/Microsite/go.aspx?eventid=4499&urlback=null&bitrate=1480329^0|0|Q|4|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

WCF gives you a level of abstraction over the way you are/want to communicate. So, you can choose binding that is Microsoft-specific, but you can also use SOAP protocol, or, you use both, so non-Microsoft client will be able to communicate through fe. SOAP, and other client can use more robust ways. 
As for REST you might want to look at Hanselman's talk on NDC <a href="http://media01.smartcom.no/Microsite/go.aspx?eventid=4499&amp;urlback=null&amp;bitrate=1480329" rel="nofollow noreferrer">here</a>. It might not answer you question directly, but it might point you something. 
As for alternatives, I don't see anything that would run on .NET, besides web services (but, because WCF gives you all this and much more, I would rather consider it as an older way, than real an alternative).

blocks|key|3097074|text|WCF是基于SOAP的(默认情况下也支持REST)，可以轻松地与任何能够理解和使用SOAP的客户端进行互操作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3097075|其中包括Java、PHP等语言和系统。|3097076|WCF是微软的实现-但这些标准都是国际标准和可互操作的标准。有关标准的任何内容都不是Mircosoft特定的。|3097077|Marc|3097078|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

WCF is SOAP-based (by default - also support REST) and can easily interoperate with any client that can understand and speak SOAP.

Those include languages and systems like Java, PHP and many many more.

WCF is Microsoft's implementation - but the standards are all international and interoperable standards. Nothing about the standards is Mircosoft specific.

Marc

blocks|key|3310050|text|我是维护ServiceStack的核心团队的一员，它是WCF的一个成熟的开源替代方案:现代的、代码优先的、模型驱动的、WCF替代web服务框架encouraging+code+and+remote+best-practices，用于创建简洁、干燥、high-perfomance,+scalable+REST+web+services。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3310051|它自动支持JSON、JSONP、CORS头文件以及form-urlencoded/multipart-formdata。在线演示是一个很好的开始，因为它们都使用Ajax。|3310052|此外，没有XML配置，也没有代码生成，而且您的“一次编写”C#+web服务提供了所有开箱即用的JSON,+XML,+SOAP,+JSV,+CSV,+HTML端点，如果需要，可以自动使用挂钩插入您自己的Content+Types。|3310053|它还包括提供快速、类型化的端到端客户端/服务器通信网关的generic+sync/async+service+clients。|3310054|这是创建一个简单web服务所需的所有代码的完整示例，该服务无需任何配置即可自动注册并在所有web+data+formats+on+pre-defined+and+custom+REST-ful+routes上可用|3310055|public+class+Hello+:+IReturn<HelloResponse>+
{
++++public+string+Name+{+get;+set;+}
}

public+class+HelloResponse+
{
++++public+string+Result+{+get;+set;+}
}

public+class+HelloService+:+Service+
{
++++public+object+Get(Hello+request)
++++{
++++++++return+new+HelloResponse+{+Result+=+"Hello,+"+%2B+request.Name+};
++++}
}|code-block|syntax|javascript|3310056|上面的服务可以用下面的代码行在C#中调用(不需要任何构建步骤/代码生成)：|3310057|HelloResponse+response+=+client.Get(new+Hello+{+Name+=+"World!"+});
response.Result.Print();+//+=>+Hello,+World|3310058|在jQuery中使用：|3310059|$.getJSON('hello/World!',+function(r){+
++++alert(r.Result);+
});|3310060|entityMap|0|LINK|mutability|MUTABLE|url|http://www.servicestack.net/|1|https://gist.github.com/1386381|2|http://www.servicestack.net/benchmarks/|3|https://stackoverflow.com/questions/8211930/servicestack-rest-api-and-cors/8215777#8215777|4|http://www.servicestack.net/ServiceStack.Northwind/|5|http://www.servicestack.net/ServiceStack.Northwind/vcard-format.htm|6|http://www.servicestack.net/ServiceStack.Hello/#clients|7|http://www.servicestack.net/ServiceStack.Hello/#predefinedroutes^0|4|C|0|1Z|16|1|3G|17|2|0|G|4|3|0|1B|V|4|2S|D|5|0|S|Y|6|0|19|1M|7|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1K|8|@]|9|@$A|1L|B|1M|1|1N]|$A|1O|B|1P|1|1Q]|$A|1R|B|1S|1|1T]]|C|$]]|$1|D|3|E|5|6|7|1U|8|@]|9|@$A|1V|B|1W|1|1X]]|C|$]]|$1|F|3|G|5|6|7|1Y|8|@]|9|@$A|1Z|B|20|1|21]|$A|22|B|23|1|24]]|C|$]]|$1|H|3|I|5|6|7|25|8|@]|9|@$A|26|B|27|1|28]]|C|$]]|$1|J|3|K|5|6|7|29|8|@]|9|@$A|2A|B|2B|1|2C]]|C|$]]|$1|L|3|M|5|N|7|2D|8|@]|9|@]|C|$O|P]]|$1|Q|3|R|5|6|7|2E|8|@]|9|@]|C|$]]|$1|S|3|T|5|N|7|2F|8|@]|9|@]|C|$O|P]]|$1|U|3|V|5|6|7|2G|8|@]|9|@]|C|$]]|$1|W|3|X|5|N|7|2H|8|@]|9|@]|C|$O|P]]|$1|Y|3|-4|5|6|7|2I|8|@]|9|@]|C|$]]]|Z|$10|$5|11|12|13|C|$14|15]]|16|$5|11|12|13|C|$14|17]]|18|$5|11|12|13|C|$14|19]]|1A|$5|11|12|13|C|$14|1B]]|1C|$5|11|12|13|C|$14|1D]]|1E|$5|11|12|13|C|$14|1F]]|1G|$5|11|12|13|C|$14|1H]]|1I|$5|11|12|13|C|$14|1J]]]]

I'm apart of the core team that maintains <a href="http://www.servicestack.net" rel="nofollow noreferrer">ServiceStack</a> - a mature Open Source alternative to WCF: modern, code-first, model-driven, WCF replacement web services framework <a href="https://gist.github.com/1386381" rel="nofollow noreferrer">encouraging code and remote best-practices</a> for creating terse, DRY, <a href="http://www.servicestack.net/benchmarks/" rel="nofollow noreferrer">high-perfomance, scalable REST web services</a>.

It has automatic support JSON, JSONP, <a href="https://stackoverflow.com/questions/8211930/servicestack-rest-api-and-cors/8215777#8215777">CORS</a> headers as well as form-urlencoded/multipart-formdata. The Online Demos are a good start to look at since they all use Ajax.

In addition, there's no XML config, or code-gen and your 'write-once' C# web service provides all <a href="http://www.servicestack.net/ServiceStack.Northwind/" rel="nofollow noreferrer">JSON, XML, SOAP, JSV, CSV, HTML</a> endpoints enabled out-of-the-box, automatically with hooks to plug in your own <a href="http://www.servicestack.net/ServiceStack.Northwind/vcard-format.htm" rel="nofollow noreferrer">Content Types</a> if needed.

It also includes <a href="http://www.servicestack.net/ServiceStack.Hello/#clients" rel="nofollow noreferrer">generic sync/async service clients</a> providing a fast, typed, client/server communication gateway end-to-end.

This is the complete example of all the code needed to create a simple web service, that is automatically without any config, registered and made available on all the <a href="http://www.servicestack.net/ServiceStack.Hello/#predefinedroutes" rel="nofollow noreferrer">web data formats on pre-defined and custom REST-ful routes</a>:

<pre><code>public class Hello : IReturn&lt;HelloResponse&gt; 
{
 public string Name { get; set; }
}

public class HelloResponse 
{
 public string Result { get; set; }
}

public class HelloService : Service 
{
 public object Get(Hello request)
 {
 return new HelloResponse { Result = "Hello, " + request.Name };
 }
}
</code></pre>

Above service can be called (without any build-steps/code-gen) in C# with the line below:

<pre><code>HelloResponse response = client.Get(new Hello { Name = "World!" });
response.Result.Print(); // =&gt; Hello, World
</code></pre>

And in jQuery with:

<pre><code>$.getJSON('hello/World!', function(r){ 
 alert(r.Result); 
});
</code></pre>

I'm currently implementing a Silverlight application using WCF for the communication between client and server. I've heard that using WCF we're bound to use some Microsoft technology at the client side, and can't easily replace this with "anything" - at least with the default SOAP implementation of WPF. 

So my questions are: 

<ul>
<li>Is this true? </li>
<li>What about Restful WCF services? I picture a plain REST implementation, and any client could communicate with this server side through REST. Yes? No? </li>
<li>What are the (good) alternatives to throwing out WCF? And why would I want to do that? </li>
</ul>

Alternatives to WCF

服务器

jQuery

JSON

Java

我目前正在使用WCF实现一个Silverlight应用程序，用于客户端和服务器之间的通信。我听说在使用WCF时，我们一定要在客户端使用一些Microsoft技术，并且不能轻易地用“任何东西”来代替它--至少用WPF的默认SOAP实现。所以我的问题是：是真的吗？关于Restful WCF服务呢？我设想了一个简单的REST...

问WCF的替代方案
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF的替代方案EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WCF的替代方案
EN