有状态的网络服务 [英] Stateful Web Services

问题描述

我正在构建一个 java/spring 应用程序，我可能需要合并一个有状态的 Web 服务调用.如果我应该完全摆脱有状态的服务调用，或者可以完成并且企业准备好了吗?

I'm building a java/spring application, and i may need to incorporate a stateful web service call. Any opinions if i should totally run away from a stateful services call, or it can be done and is enterprise ready?

推荐答案

有状态的 Web 服务很难维护.我为他们看到的机制是让第一个调用返回一个在后续调用中使用的 id(基本上是一个事务 id).一个问题是 Web 服务并不是真正有状态的，因此它必须为每次调用从某个其他数据存储加载它需要的所有信息.

Stateful web services are a pain to maintain. The mechanism I have seen for them is to have the first call return an id (basically a transaction id) that is used in subsequent calls. A problem with that is that the web service isn't really stateful so it has to load all the information that it needs from some other data store for each call.

这篇关于有状态的网络服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！