4 ms·
> So each screen has the previous screen the user visited, to allow the user to go “back” and get the exact screen they were in before (state, scrolling positio
by preseinger 4y ago
> So each screen has the previous screen the user visited, to allow the user to go “back” and get the exact screen they were in before (state, scrolling position, validation notices etc).
this is the actual problem, a clear design error if the entire screen "stack" is part of per-request or per-session state while also being unbounded
the backslashes encoding stuff is a symptom
- preseinger 4y agodownvotes? what? nothing i wrote is in any way controversial? obviously you can't embed unbounded history in session state directly?
- mkl 4y agoYou can store a heck of a lot more states if you don't double the storage required with each additional state. That's the actual problem.