开发者

SOAP Web Service method naming conventions

Consider a Web Service (e.g. SOAP-based) that has an operation which accepts a bulk of data from the client. From the server's point of view it is receiving data, but from the client's point of view it's sending data. How should that operation be named? The options are

Is there a de facto standard for naming these things? How do web services usually name these?

Thank you for your opinions.


It's a service. It's there to serve. Name operations from the client's point of view.


Here are the W3C specifications for Simple Object Access Protocol (SOAP) v1.2 specifications: https://www.w3.org/TR/soap12/.

Section 3.1.1 says that a URI should be used to name a feature and should "[enable] the feature to be unambiguously referenced...".

Further, section 5 of this document says:

"All capability names SHOULD follow 'verb' + 'noun' + ['subject'] format, where:

  • 'verb' is the action that the consumer is performing; and
  • 'noun' is the name of the primary object on which the action is being performed."

Hope this helps someone (9 years later).

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜