Answer Posted / hrdiya

Page processing begins on a thread-pool thread, but that
thread is returned to the thread pool once an asynchronous
I/O operation begins in response to a signal from ASP.NET.
When the operation completes, ASP.NET grabs another thread
from the thread pool and finishes processing the request.
Scalability increases because thread-pool threads are used
more efficiently. Threads that would otherwise be stuck
waiting for I/O to complete can now be used to service
other requests. The direct beneficiaries are requests that
don't perform lengthy I/O operations and can therefore get
in and out of the pipeline quickly. Long waits to get into
the pipeline have a disproportionately negative impact on
the performance of such requests.

How dataadapter.fill works?

1075

---

What is masterpage?

997

---

What is the equivalent of date() and time() in asp.net?

1026

---

What is State Management in .Net and how many ways are there to maintain a state in .Net? What is view state?

1105

---

How asynchronous call can be implemented using delegates?

1038

---

Is asp net front end or backend?

1050

---

What is ViewState? What does the "EnableViewState" property do? Why would I want it on or off?

1171

---

What is difference between session and viewstate?

959

---

What are validator? How do you disable them?

1201

---

How is session id generated?

980

---

What is web api vs wcf?

1061

---

How you can access the values from the Repeater control in ASP.NET?

1106

---

What is the use of session state and application state and difference between them?

960

---

What is dynamic web page with example?

1011

---

How do I publish my asp.net application to my isp's web server?

1125

---