storing my own information in the Request object

[Andy Fish]

Hi,

Is there anywhere inside the HttpRequest object that I can use to store my
own information? from what I can see things like ServerVariables are made
read-only.

If not, does anyone else have a sensible strategy for storing information
that pertains to a particular request so that it can be shared between
global.asax handlers and the page itself? I cannot use session state for
this.

TIA

Andy

 

[Just Me]

viewstate("yourValiableNameWhichPersistsDuringPostback")
session("VariableAvailableOnlyToYouForYourSession")
application("availableToAnyoneUsingTheApp")

 

[Andy Fish]

thanks but none of those help me

i want something that is specific to this request - specifically

(a) I can set in the global.asax Application_BeginRequest handler and
retrieve in the page itself

(b) is not shared between concurrent requests on the same session

 

[Mark Rae [MVP]]

i want something that is specific to this request - specifically

(a) I can set in the global.asax Application_BeginRequest handler and
retrieve in the page itself

That's what the Session object is for...

(b) is not shared between concurrent requests on the same session

When you put something in the Session object, it isn't *shared* between
concurrent requests per se - it is *available* to all requests, which is not
the same thing...

 

[bruce barker]

you want the HttpContext.Items collection. it designed for this.

-- bruce (sqlwork.com)

 

[Andy Fish]

Thanks bruce, sounds perfect

surprised I didn't spot this one when RTFMing

 

[Andy Fish]

session state is not available in the BeginRequest handler

 

[Mark Rae [MVP]]

session state is not available in the BeginRequest handler

You're quite correct - sorry for the confusion...