Keeping IDs between pages throughout the day?

Question

I need to store identifiers (contact identifiers, claim identifiers, etc.) between multiple .aspx pages.

Currently, I save the identifier in the session and set the session timeout to 300 minutes. However, I still get errors because users try to perform operations after the session expires.

I think that users leave their web browsers open, lock their computers, go home in the evening, arriving the next morning and trying to pick up where they left off.

I do not want to use Querystring. Cookies are more for user identifiers than contact identifiers and claim identifiers. Viewstate is only supported on the page. The constant session in the database seems unnecessarily complicated. I do not want to increase the session timeout too much.

I would ideally like them to pick up where they left in the morning.

What are the best practices for storing identifiers between pages? How can I do this without receiving a message that their session has expired? I don’t notice anything obvious ?!

Answer 1

, " ", MRU. cookie. , , , 7- .

Answer 2

. , , .

cookie , , . .

, . .

Answer 3

@David, .

, "" ( ), :

• , , , .
• XML, , ( base64 ..), .
• ​​, # 2 , .
• .:)

, , XML base64 50% , (100 ), - .

, , , . , .

Answer 4

viewstate , , , . ID.

You are right, storing this type of data in a session is not quite what it is intended for. Viewstate is the best mechanism for this.