Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Its a well know fact that webservices are stateless. Its written in every text that deals with WCF basics. But I need to know, Are they truely stateless.
I was reading about the PerCall WCF webservice, which destroy the service instance for every call. I am not able to comprehend the use of Percall service. If webservices are stateless, then what is the need of destroying service instance for each call.
WCF has several instance models.
The PerCall model is truly stateless. With the singleton model it depends on how you write it (but stateless is strongly advised). The PerSession model is not stateless at all.
There are trade-offs regarding memory use, concurrency, latency and security.