Sessions is Class file

[phaseshift]

The following is an example of code that is not working. I am trying to write a class file that will set session variables as needed.

public static string ID
{
get
{
return HttpContext.Current.Session["ID"].ToString();
}

set
{
HttpContext.Current.Session["ID"] = value;
}
}

any ideas on how to get sessions to work with gets and sets?

thanks

 

[JurkMonkey]

HttpContext.Current.Session.Keys.Add("ID", value);

Does that work?

 

[phaseshift]

There is not a Key.Add avaliable.
I tried: HttpContext.Current.Session.Keys[0] = value;

and that didn't work either.

Thanks again

 

[JurkMonkey]

Session.AddKey?

I don't remember off hand.

 

[phaseshift]

I can't find anythin like addkey.

The problem seems to be because I am not adding the session to an aspx.cs file. If I try and add a session to a ascx.cs file(a custom control) I can't access the session vairable when I get back to the page code.

any thoughts

 

[JurkMonkey]

What are you trying to accomplish with this?

 

[phaseshift]

I have a login control that returns your id and access level upon a valid login. I need to store these values in a session for later use.

Whoever wrote the org. code used Cache which is not creating a problem since cache is shared with everyone accessing the server.

 

[JurkMonkey]

I understand now.

I'm assuming you're accessing a database that you can write to? You might want to consider doing all of your permissions on the server side.

Store the given SessionID in the database with the associated permissions level. When you make a server request, try pulling the permissions from the database using their SessionID. This allows you to hide the Username/Password and manage all permissions on the server side. This is much safer.

Your calls could then be something similar to:

http://www.mypage.com/updateRecord.aspx?SessionID=0021316542100321310321

IF you still need to add session keys, check out this link

http://www.csharphelp.com/archives/archive185.html

 

[chiph]

Another vote for storing session in the database.

When you add a second web server via MS network load balancing or a hardware load balancer (preferred), you need to handle the case where a returning user gets directed to the other server. If the session is stored on one server, it won't be available to the others in the web farm.

While MS NLB says it handles this, a friend's experience has been that NLB is more prone to blue-screening, thus the recommendation of a hardware load balancer.

Chip H.


____________________________________________________________________
Donate to Katrina relief:

http://s1.amazon.com/paypage/PELYGQVJ8Q7IB/103-6821258-5919825

If you want to get the best response to a question, please read FAQ222-2244 first