Say I have the following situation:
- A paginated View displays a list of contacts with the following route: Contacts/Index/Page/2.
- The View gets its paginated data ViewModel object.
- The View also gets its filter properties from the ViewModel, like the Contact Category.
I would like to store the page number and the filter properties somewhere in such a way that when the user returns to Contacts/Index page, the same page number and filters are applied.
Is it good practice to store these properties within a Session variable? Should the ViewModel be handling these Session variables?
Is there another way to tackle this type of situation?