标记 Web 服务端点
Web 服务端点通常是在项目的早期阶段定义的。 由于它遵循“合同第一”的原则，因此在传达给客户端系统后不应更改。
因此，以良好的方式标记 Web 服务至关重要。
您如何标记 Web 服务？
例如
http://my.domain.com/businessProcess/services/concreteServiceName
其他想法？
将此问题视为一项民意调查...请随意投票选出最佳想法。
The web service endpoint usually is defined in an early stage of a project. Since it follows the "contract first" principle, it shouldn't be changed after communicated to client systems.
Therefore, it is vital to label the web service in a good way.
How would you label web services?
e.g.
http://my.domain.com/businessProcess/services/concreteServiceName
Other ideas?
See this question as a poll... Feel free to vote for the best idea.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们通过与开发人员、业务人员和支持人员交谈来决定名称。 我们成立了一个名为“界面控制委员会”的委员会，我们的处理方式有点像您在问题中描述的那样。 我们希望服务名称具有描述性，反映它们支持的流程，并满足技术和业务利益相关者的需求。
当我们召开 ICC 会议时，我们也会讨论模式以及如何开发它们。 业务人员也是其中的关键，因为他们知道想要公开哪些数据以及原因。
K A
We decide on names by talking to the developers, business guys, and support guys. We formed a committee called the "interface control committee", and we approach it kind of like you described in the question. We want service names to be descriptive, reflect the processes they support, and fit the needs of the technical and business stakeholders.
When we have ICC meetings, we also talk about schemas and how they should be developed. The business guys are key in this as well since they know what data they want to expose and why.
KA
我会在 URL 中包含版本号。
I would include a version number in the URLs.