为什么WADL吸收缓慢? [英] Why the slow WADL uptake?

问题描述

我一直在研究WADL，想知道为什么它没有被更广泛地采用?

I've been researching WADL and am wondering why it isn't more widely adopted?

随着REST使用率的增长，令我惊讶的是更多的开发工作没有使用它.

With the rate at which REST usage seems to be growing, I'm surprised that more development efforts don't use it.

其设计是否存在根本缺陷，是不是与通常围绕RESTful Web服务的文化很好地匹配?还是完全其他的东西?

Is there are fundamental flaw in its design, is it not a good match for the culture that typically surrounds RESTful web services, or is it something else entirely?

推荐答案

我认为WADL未能获得普及的主要原因是，它可能使我们在SOAP和WSDL中遇到的所有问题都复活.对我来说，互操作性是Web服务最重要的一个方面.
通过遵循使用纯HTTP标准的RESTful方法，您可以免费"获得互操作性.一旦需要一个文档来描述服务，就会有不同的客户端框架(或不同的服务器框架)来不同地解释该文档. 一旦不同的框架从WADL自动生成代码，您将不得不再次处理互操作性问题.

I think the main reason why WADL doesn't gain popularity is that it might bring back to life all those problem we had with SOAP and WSDL. To me, the interoperability aspect is the single most important aspect of web-services.
By following the RESTful way of using pure HTTP standards you get interoperability "for free". Once you need a document to describe the services, there will be different client frameworks (or different servers frameworks) that will interpret this document differently. Once different frameworks auto-generate code from WADL you will have to deal with the interoperability problems again.

缺乏标准是RESTful方法的弱点和优势，让我们为简单的方法提供一个机会. (即使我们真的很喜欢自动代码生成:-))

The lack of standards is the weakness and strength of the RESTful way, let's give the simple approach a chance. (even though we really enjoy automatic code generation :-) )

这篇关于为什么WADL吸收缓慢?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！