Are there ASP.NET Session design patterns? -
are there ways of structuring session storage in asp? put string key, i'm thinking of taking more stringent measures.
the issue has come because have application has use session heavily 2 reasons:
- the application has perform operations on data before presenting user.
- the application has validate choices before writing changes.
my strategy has been build lists , store them in session on page load.
i'm running several problems this. keep getting reports of things being 'entered users,' namely 1 of lists build , store in session shows values entered before they've had chance add them. i'm not sure why keeps happening, given rebuild lists stored in session on each load. suspect there lot of button pushing.
are there ways design session storage lists stored unique instance of page? or, failing that, way of designing session storage unique page?
generally, use session data can shared between pages, , specific user.
what you're describing not use of session. consider happens if user happens open 2 pages in separate tags - session data 2nd tab overwrite first, , you're on way data corruption.
there nothing wrong manipulating data before presenting user, , performed in business layer. if manipulation computationally expensive, consider sort of caching strategy.
and @mikek3332002 says, use build-in validation tools. again, there reason use session part of validation.
Comments
Post a Comment