Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 04, 2008 04:29 PM by cibrax
Nov 10, 2008 07:50 PM|LINK
Nov 11, 2008 06:13 AM|LINK
I have to say that sessionful services are not very RESTful. Remember the point of REST is to build services that work the way the web works and the web is typically not session oriented. You can integrate ASP.NET security with membership in your solution
so you don't need to store username and password. The use of in-memory variables like this is probably not the right idea.
What is it you are trying to accomplish with the session? It sounds like you want to retain the username / password in memory so you can authenticate/authorize the call.
Nov 11, 2008 06:24 AM|LINK
You can see a screencast about using ASP.NET membership with your WCF service at
Dec 04, 2008 04:29 PM|LINK
PerSession mode does not work with WCF REST services, you can enable ASP.NET compatibility mode for the service and use the regular Http Session to store those variables. By the way, single means singleton, only one instance of the service will be available
on the service, and it will be shared among all the users.