3 ms·
To add to this: Microsoft recognized that third-party control developers were dumping too much info into the ViewState bag, and this was largely fixed in later
by jiggawatts 5y ago
To add to this: Microsoft recognized that third-party control developers were dumping too much info into the ViewState bag, and this was largely fixed in later versions.
It's also possible to store ViewState "on the server side" instead of on the client side. So instead of sending megabytes up and down with every request, the client just gets a unique identifier. The downside is increased memory usage, but that's often better, especially for internal enterprise apps.
- jolux 5y agoYeah, ironically the way people try to do stateless backends and heavy frontends with JWT is closer to the ViewState mess than normal MVC apps.