3 ms·
Ideally, this is how state management should work all the time, regardless. Holding too much state server-side breaks bookmarks and shares. EDIT: Hmm. Is this
by torstenvl 1y ago
Ideally, this is how state management should work all the time, regardless. Holding too much state server-side breaks bookmarks and shares.
EDIT: Hmm. Is this comment controversial? Obviously some people disagree strongly. Mind sharing why?
- patates 1y agodidn't down-vote you but perhaps you mean tech which holds nearly all client state on the server like JSF or webforms and I think that may be not so clear to some :) for front-end frameworks, not storing the state on the URL usually means storing it on the memory or sessionstorage and server is usually not involved