WCF 与旧版 ASP.Net Web 服务
Possible Duplicate:
Web Services — WCF vs. Standard
Could anyone recommend me some documents to describe why WCF is better than legacy ASP.NET web services? I am especially interested in performance and security.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
WCF 是一个高度可配置的堆栈，具有几乎无限的序列化、安全性、传输等组合。
对于您的具体问题，WCF 实现 WS-* 协议，包括传输和消息安全。
WCF 数据契约序列化器比 acmx 中使用的 xmlserialzer 快得多。 Net.Tcp 传输也比基于 http 的传输性能更高。
我在这里找到了性能比较
http://msdn.microsoft.com/en-us/library/bb310550。 ASPX
WCF is a higly configurable stack with almost infinite combinations of serialization, security, transport etc.
For your specific question WCF implements WS-* protocols including both transport and message security.
WCF datacontract serializer is substantially faster than xmlserialzer used in acmx. The Net.Tcp transport is also more performant than http based transport.
I found a performance comparison here
http://msdn.microsoft.com/en-us/library/bb310550.aspx
Microsoft MSDN 上有很好的概述：
《基于开发的 ASP.NET Web 服务与 WCF 的比较》
http://msdn.microsoft.com/en-us/library/aa738737.aspx
Very good overview on Microsoft MSDN:
"Comparing ASP.NET Web Services to WCF Based on Development"
http://msdn.microsoft.com/en-us/library/aa738737.aspx
WCF 更加灵活：
而且：还可以通过 NetTCP、MSMQ、wsHttp 等使用
WCF 服务可以托管在 IIS 中（如旧版 ASMX）
但 WCF 服务也可以在控制台应用程序中自托管、Windows NT 服务等
，
WCF 提供比 ASMX 更多的安全功能和安全级别（消息安全等） .)
在 WCF 中，几乎所有内容都可以在配置文件中进行配置 - 更是如此与 ASMX 相比。
我手头没有任何现成的文件来描述这一点 - 但这确实是它的本质，我想说。
马克
PS：不确定这是否包含对您有用的任何内容：
http ://whitepapers.techrepublic.com/abstract.aspx?kw=remoting&docid=270830
PPS：您可能会认为微软会拥有大量这些白皮书来说服人们 - 但是不..... ：-）
WCF is much more flexible:
but also: can be used over NetTCP, MSMQ, wsHttp and so on
WCF services can be hosted in IIS (like legacy ASMX)
but WCF services can also be self-hosted in a console app, Windows NT Service, etc.
WCF offers a lot more security features and security levels than ASMX (message security etc.)
In WCF, almost anything is configurable in a config file - much more so than with ASMX.
I don't have any ready-made documents at hand that describe this - but that's really the essence of it, I'd say.
Marc
PS: Not sure if this one would contain anything useful for you:
http://whitepapers.techrepublic.com/abstract.aspx?kw=remoting&docid=270830
PPS: you would think that Microsoft would have heaps of these white papers to convince folks - but no..... :-)
乔治，
我手头没有任何此类文档，因为 WCF 更好的原因显而易见。
首先，因为微软：ASMX Web 服务是一项“传统技术”< /a>. 他们还公开声明不会对 WSDL.EXE 和 ASMX 技术的其他部分进行更改。 在这个行业中，我们在遗留技术和应用程序方面遇到的麻烦已经够多了——今天创建一段新的遗留代码是没有意义的。
其次，WCF 抽象了 ASMX、Remoting 和 WSE 的概念。 “他们能做的任何事情，WCF 都能做得更好”。
George,
I don't have any such documents handy, because it's so obvious why WCF is better.
First, because of Microsoft: ASMX Web Services are a “Legacy Technology”. They're also publicly stating that they will not be making changes to WSDL.EXE and other parts of the ASMX technology. We have enough trouble in this Industry with legacy technology and applications - it makes no sense to create a new piece of legacy code today.
Second, WCF abstracts the concepts that are part of ASMX, Remoting, and WSE. "Anything they can do, WCF can do better".
简而言之，你的问题相当于“为什么.NET比VB6更好”。 如果有足够的时间，任何遗留技术都将成为维护/财务负担。
当您特别询问安全性和性能时，我会说“这取决于”。 可以使任一选项都安全，并且性能很大程度上取决于您编写的代码。 WCF 性能的一个优点是您不必将其托管在 IIS 中 - 因此您有更多选项和灵活性来提高其性能。
To put it simply, you're question is the equivalent of "Why is .NET better than VB6". Given enough time, any legacy technology will become a maintenance / financial burdon.
As you've asked about security and performance in particular, I would say "it depends". It is possible to make either option secure and performance is largely down to the code you write. One plus side for WCF performance is that you don't have to host it within IIS - so you have more options and flexibility to make it performant.