ASP.Net Server-Side, Single-Request, User-Specific, Sharable Variable

Question

0.00/5 (No votes)

See more:

I'm looking for a server-side variable that only lives for the duration of a single request and that gets reset each request, and that is shared between multiple control instances, and that is specific to each user (rather than shared among multiple users).

A static variable persists too long (across multiple requests), a member variable isn't shared among multiple control instances, session persists across multiple requests, and cookies/view state go to the client (I only want it to reside on the server).

I could probably store something in session and reset it in Application_BeginRequest so that it is fresh for each request (and maybe erase it in Application_EndRequest), but I was wondering if there was a more standard way of doing this. How would you create such a variable?

Posted 11-Jan-13 6:55am

AspDotNetDev

Add a Solution

Comments

[no name] 11-Jan-13 14:03pm

Global variables for Page Class?? is that what you want?

AspDotNetDev 11-Jan-13 14:16pm

Not sure what you mean, but any variable (member or static) on the class for a given page would not work because it should be accessible from any control (and controls should have no knowledge of the specific page they are on, because they may reside on many pages). Though, maybe if I put it on the page and passed a delegate to the control so it knows how to get/set the page variable, that'd work. Seems complicated though.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)