EVERYTHING on the Web is disconnected. ASP.NET is disconnected; Web services are disconnected; HTML is disconnected. In the HTTP world of the Web, there's no living connection between a client (browser) and a server (IIS or whatever). Each request is served and thrown to the client and then both remain disconnected from each other until the next Request is issued by the client. It applies to all Web applications you can possibly create. Most of ASP.NET features such as ViewState, PostBack, Session and Application State, etc., are designed precisely to make this disconnected nature the less disturbing as possible, so that you can program the application as if there were a continuous interaction between the client and the server, where there is not.
Dig Deeper on Win Development Resources
Related Q&A from Daniel Cazzulino
Here Daniel Cazzulino explains how to load a DSL (domain specific language) domain model instance file programmatically. This requires the .NET type ... Continue Reading
Here we offer a glimpse at 12 of .NET development expert Danny Cazzulino's top ASP.NET questions and answers. Continue Reading
C# developers should NOT be modifying InitializeComponent method in the code-behind (or any of the variable definitions) by hand. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.