Which One Is Best for this Task (TempData vs Session Or Other else)

Question

2.00/5 (1 vote)

See more:

Hi Everybody,

In my MVC Application i am getting List of products from the service. and Now i want to store that response to in State Variables (Temp Data or Session or other else ).

I know that temp data have some limitation temp data stores only records for one time reading. but we can use TempData.Keep() for store long time.

TempData["Products"] = serviceobj.GetAllProducts();    // 7000 products in one time.

So Please suggest me any good idea about it. Is Client side storage is good option for that...

Posted 23-Jul-13 6:21am

Anubhava Dimri

Updated 23-Jul-13 6:22am

v2

Add a Solution

Comments

RomilGandhi 25-Jul-13 5:55am

use @ViewBag to store list of Products. You can also use TempData but ViewBag is better option to store records.

Anubhava Dimri 25-Jul-13 6:11am

View data is only for passing the value from the controller to view and visa varsa.

I need to store data for long time. in which have i need to apply filtering shorting etc-etc.

so i can't use view data or view bag.

RomilGandhi 25-Jul-13 6:15am

than it's better that you use session for that.

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)