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?
bmw0128
问问题
3241 次
2 回答
6
Statefulness runs counter to the basic architecture of HTTP (ask Roy Fielding), and reduces scalability.
于 2008-09-18T17:26:28.227 回答
5
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.
于 2008-09-18T17:48:05.740 回答