One solution to the user recognition problem has been to write and read browser cookies, but cookies have
when they are used for session tracking.
offers another possible solution by passing data back-and-forth through hidden fields, but this also has limitations as the data becomes more complex.
Because managing a user's state during a session is important, ASP includes features to make this task easier for you.
Without custom programming, ASP's Session object enables you to track variables for a user's session through a file that is stored on the server, not the user's browser.
The next lesson describes how ASP's Session object maintains user information.
If you need to set up communication between two applications, whether they are co-located or separated by thousands of miles, rest assured WCF can do it.
And if its out-of-the-box features do not suffice, WCF’s tremendous extensibility model provides ample opportunity for plugging in just about anything you can think of.
And this is where we will take a bit of a left turn, off the evolutionary path of ever greater capability and flexibility and towards something simpler and more targeted at a small set of specific scenarios.
As this books is about building RESTful services with the ASP.NET Web API, we want to start looking at the need for such services (in contrast to SOAP/RPC style services), and also what types of features and capabilities they provide.
This concept of routing is critical to understanding how the ASP.NET Web API can be used for building services, so let us look at an example. In this book, you will learn how to develop
a simple task-management service. You can imagine having a SOAP-based service method to fetch a single task.
This method would take a task’s TaskId and return that task. Implemented in WCF, the method might look like this: