为什么 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屋！