.net - Are web services truly stateless? -


It's well-written that the web server is serviceless, written in every text that works with WCF origin

I was reading about PerCall WCF webservice , which destroys the service example for each call. I understand the use of the Percall service I'm not able. If webservices are stateless, then what is the need to destroy the service frequency for each call?

WCF has many example models

  • single (singleton) Where 1 example handles all requests.
  • Per call model where each call receives a different example
  • Per session model where each customer gets an example (stateful)

PerCall model is actually Stateless, with a singleton model depending on how you write it (but Staltace is strongly advised). There is absolutely no per session model.

There is trade-off in relation to memory usage, concurrency, latency and security.


Comments

Post a Comment