ASP.NET：Web服务设计方法。顶向下和自底向上。有什么不同？ [英] ASP.NET: web services design methodologies. top-down and bottom-up. what's the difference?

问题描述

能有人给我这两个方法的高度概括？什么是这两个，为什么你会选择一个比其他的区别？我只是想用自己的话一般的解释，我只是与Web服务开始。谢谢。

can someone give me a high level overview of these two methodologies? what's the difference between these two and why would you choose one over the other? i would just like a general explanation in your own words as i'm just starting with web services. thanks.

推荐答案

自顶向下的方法需要你写自己的WSDL和XSD，然后创建服务，得出WSDL和XSD。在自下而上的方法，你先写服务code，然后WSDL和XSD。在MS因为WSDL和XSD由工具为您生成世界自下而上是很容易的。第一种方法是更难，因为它具有较小的工具支持和开发人员，因为通常没有足够的技术来写WSDL（尤其是与WS-政策）。

Top down approach requires you to write your own WSDL and XSDs and then create service which follows that WSDL and XSDs. In bottom up approach you first write service code and then WSDL and XSDs. In MS world bottom up is very easy because WSDL and XSDs are generated for you by tools. The first approach is much harder because it has lesser support in tools and because developers are usually not skilled enough to write WSDL (especially with WS-Policies).

编辑：如果您先写服务，或者您对客户端和服务的控制，你总是会使用自下而上。如果你需要首先定义的合同，以便客户端和服务可以实现和单独测试（大集成项目照常），您将使用自上而下的。

If you write service first or if you have control over client and service you will always use bottom up. If you need to define contract first so that client and service can be implemented and tested separately (usual in big integration projects) you will use top down.

最好的问候，拉吉斯拉夫·

Best regards, Ladislav

这篇关于ASP.NET：Web服务设计方法。顶向下和自底向上。有什么不同？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！