<div>
each user will have an instance as a link but it is only one web application<br />
<br />
see this url <br />
<a href="http://www.codeproject.com/Articles/121096/Web-Server-and-ASP-NET-Application-Life-Cycle-in-D" rel="ugc">http://www.codeproject.com/Articles/121096/Web-Server-and-ASP-NET-Application-Life-Cycle-in-D</a>
</div>


each user will have an instance as a link but it is only one web application

see this url
http://www.codeproject.com/Articles/121096/Web-Server-and-ASP-NET-Application-Life-Cycle-in-D [http://www.codeproject.com/Articles/121096/Web-Server-and-ASP-NET-Application-Life-Cycle-in-D]

<div>
When you indicate each user has an instance, you mean a <b>copy of the application</b>?<br />
<br />
However, that one application can keep count of that user instance in its Application OBject?
</div>


When you indicate each user has an instance, you mean a copy of the application?

However, that one application can keep count of that user instance in its Application OBject?

<div>
<div class="content wysiwyg-content">
I know when you call a web application, Session Objects are created. &nbsp;Am I correct by saying there is only one instance of the &nbsp;Web Application running at all times? <br />
<br />
If so, are the users coming in and processing on a thread of the web application?
</div>
</div>


I know when you call a web application, Session Objects are created.  Am I correct by saying there is only one instance of the  Web Application running at all times? 

If so, are the users coming in and processing on a thread of the web application?

Web applications running

Web applications are systems that run in browsers that perform functions normally associated with other client-based programs. One of the most commonly used web applications is email; instead of downloading individual emails to a local machine, the data is shown through a website. Other examples of web applications are collaborative systems like a wiki or an online game.