State Management

Re: what prevents the confliction in HttpContext?

Anas_Aljabri — Mon, 06 Jul 2009 18:14:02 GMT

Thanks Alot for this help now it's clear in my brain.

Re: what prevents the confliction in HttpContext?

anas — Sat, 04 Jul 2009 22:41:09 GMT

Anas_Aljabri:
if the application can serve multiple Requests, what prevents the confliction in the following code

HttpContext context = HttpContext.Current;
context.Items.Add("UserID", "11");
Server.Transfer("AnotherForm.aspx");

and in AnotherForm.aspx

string UserID = HttpContext.Current.Items["UserID"];

what guarantee that this Application is not serving a new Request.

It serve more than a request at the same time and there will be no conflict because each request will have it's own HttpContext object.

For example, let's say that 2 users requested your website at the same time, then each user will be given a seprate HttpContext which encapsulates the data related to each user request.

what prevents the confliction in HttpContext?

Anas_Aljabri — Sat, 04 Jul 2009 18:56:12 GMT

Hi all i just joined this group. and i will start bothering you by question :D

As i know HttpContext Object is an object which contains most of the common details about an HttpRequest and we can ask about the current HttpRequest using the following code

HttpContext context = HttpContext.Current;

does that mean always in the application only one Request will be serving at a time ??

if the application can serve multiple Requests, what prevents the confliction in the following code

HttpContext context = HttpContext.Current;
context.Items.Add("UserID", "11");
Server.Transfer("AnotherForm.aspx");

and in AnotherForm.aspx

string UserID = HttpContext.Current.Items["UserID"];

what guarantee that this Application is not serving a new Request.