Which is the best method to store a session, in a HashTable or define single by single. Need more advice from you guys

Question

0.00/5 (No votes)

See more:

Hi Guys ! I have some confusion over best way to store multiple session values. One of my friend told us that define session 3-4 times is heavy rather then define in a HashTable. Like below scenario : The question is which is better one & why.

C#

Hashtable ht = new Hashtable();
ht.Add("UserID", txtUser.Text);
ht.Add("Type", type.Text);
ht.Add("PaypalID", paypal.Text);
Session["hashtab"] = ht;          //-- Is this better way or below one.

C#

Session["UserID"] = txtUser.Text;
Session["Type"] = type.Text;
Session["PaypalID"] = paypal.Text;

Please light over that in upper scenario my TL told me that hashtable takes minor memory on the server (suppose it takes 500 kb) rather than one by one (suppose it takes 3MB).

Any Suggestions really appreciate ! I really need more advice from you guys.

Posted 3-Apr-13 20:30pm

Mas11

Updated 5-Apr-13 2:07am

v4

Add a Solution

1 solution

Add a Solution

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)

Abhinav S · Answer 1 · 2013-04-03T20:34:00

Solution 1

The hashtable would just be an additional overhead, so I don't see any use for it.

The only minor advantage could be if you need to store a particular group of session values together for tracking.
But other than that, I don't see any use for an additional hashtable.

Posted 3-Apr-13 20:34pm

Abhinav S

Comments

Mas11 4-Apr-13 2:45am

Thanks Abhinav for the answer. Please light over that in upper scenario my TL told me that hashtable takes minor memory on the server (suppose 500 kb) rather than one by one (suppose 3MB).

Abhinav S 4-Apr-13 3:04am

I'm not sure what he is talking about. I don't believe using a hashtable will provide any benefit in terms of space.

Mas11 4-Apr-13 3:14am

Thanks Abhinav ! It means I was right.

Abhinav S 4-Apr-13 3:19am

Well yes. But don't argue with your TL.

Sergey Alexandrovich Kryukov 4-Apr-13 9:29am

I agree, my 5. It's funny that someone voted 2.
—SA

Abhinav S 4-Apr-13 9:50am

Thanks SA. Well whoever voted 2 thought otherwise and I would have appreciated him posting why that was so.