CODEWITHSUNDEEP
asp.netasp.net-mvcsessioncookies
Nate
Nate

Reputation: 30666

Standard way to persist data between requests in ASP.NET-MVC

What is the most standard or best way to persist data between requests?

Should I use cookies or session variables? I'm interested in keeping data like sort order, sort column, and page number (for paginiation).

I'm coming from a webforms background so normally this type of thing was automatically handled for me in the viewstate of the controls I was using.

update

I like the querystring idea, for searching and more meaningful URLs; however, I'm working on an "index/list" view, which consists of a View with header, and "control" options, like DDLs for filtering and a partial view that renders the table of data.

The DDLs use a $.load() to call an ActionResult on the controller, which returns the partial view, passing parameters there in the querystring, but since these are ajax requests the main page url of the user's browser does not get updated.

Is there a best-practice for taking querystrings off the main-page URL and using them in ajax requests to other ActionResults?

Upvotes: 5

Views: 12514

Answers (7)

Ricardo Sanchez
Ricardo Sanchez

Reputation: 6289

Cookies is a fast and simple way to persist data between requests, and you can also make them live only for a limited time depending on your needs.

Upvotes: 0

Zhaph - Ben Duguid
Zhaph - Ben Duguid

Reputation: 26976

In response to your update, a nice way to achieve that for pages would be to have links to "Previous" and "Next" pages of results (or better yet, a list of all pages in the list), output on the page, with the page numbers, that you then hide with JavaScript.

This way users should see your nice, AJAXy behaviour, and search engines (and users without JavaScript - mobile, or those using older screen readers for instance) will still be able to get access to all your pages - this will help your pages to degrade gracefully, or use "Progressive Enhancement".

Upvotes: 1

Zhaph - Ben Duguid
Zhaph - Ben Duguid

Reputation: 26976

It depends on how permanent you want the information to be:

  • Things like the page number should indeed be in the URL (as others have pointed out) - this helps with bookmarking, etc, but remember that if you add more content to the list, then that bookmarked result set will not always be what the user wanted...
  • If you're happy for these values to be lost when a session times out (by default around 20 minutes), then put them in Session.
  • If you think that sessions are going to timeout before the next request, or you want to save it across visits then you should be storing them in either cookies, or a profile (potentially allowing "Anonymous" profiles, which work with the users cookies, so they would lose them across machines).

Personally, I'd think very carefully about putting sort order and columns in the URL if you do you could actually end up really confusing search engines:

  1. Lots of pages with very similar content (page 1, sorted by date desc, page 1 sorted by date asc, etc) - search engines don't like duplicate content, and nor should you as Google (for instance) will only show two pages from your site in a default result set, you want them to be valid, not duplicates.
  2. Search engines will spend lots more time crawling your site, and potentially give up - If on every page they find links to "Sort by this column", they will attempt to follow them, resulting in more work on the server, higher bandwidth use, etc.

These can be mitigated through the use of a Robots.txt file denying access to sorted versions of the page, but if this is generated almost dynamically that will be very complex to maintain going forward.

Upvotes: 1

ScottS
ScottS

Reputation: 8553

Things that were previously in viewstate should probably be put back in the clients hands via either hidden fields or cookies.

Session is "too" easy. In a dev environment it works great, pretty much no matter what you put in it. In production scalability and persistence become a problem. In-process session is likely to disappear unexpectedly if you have crashing bug in your site, and requires server affinity when load balancing. Out-of process session fixes the durability and affinity issues, but can still be a performance bottle neck if too much stuff is put in session. A VERY common problem is that each page will put 1 or 2 items into session but never take them out again when they are done. And even if a page removes it session data when it is no longer needed, the data can still get orphaned if a user starts a process and never completes it.

Upvotes: 0

Chad Ruppert
Chad Ruppert

Reputation: 3680

If you want it to survive only through one request/redirect TempData is your friend.

However, for things like your pagination, URL is the best method, for the ability to share links alone.

Upvotes: 6

Turnkey
Turnkey

Reputation: 9416

A standard way is to pass those sort of things via URL Query Parameters. You can modify your routing to expect certain URL variables. That way the pages become more search engine friendly as well.

Upvotes: 3

Dustin Laine
Dustin Laine

Reputation: 38553

Session are easiest.

Upvotes: -1

Related Questions