3 ms·
Isn't one component of this that so many people develop for web now? And that HTTP is inherently stateless. That means we have to resort to hacks to store stat
by cimmanom 9y ago
Isn't one component of this that so many people develop for web now? And that HTTP is inherently stateless.
That means we have to resort to hacks to store state (databases, cookies) - and like most hacks, those are fragile (such as assuming a single instance of state and then breaking when the user opens another copy of the site in a tab).
With the rise of single page apps, there's a more coherent concept of state on the front end, but that doesn't fix the fragility of the server side portions.
- naasking 9y ago> That means we have to resort to hacks to store state (databases, cookies) - and like most hacks, those are fragile (such as assuming a single instance of state and then breaking when the user opens another copy of the site in a tab). In principle, there's nothing fragile about the types of state you describe, but most web frameworks don't impose enough restrictions to ensure this state is used correctly [1]. [1] something like this would work, but it's not the only option: http://cs.brown.edu/~sk/Publications/Papers/Published/mk-int-safe-state-web/ http://cs.brown.edu/~sk/Publications/Papers/Published/mk-int...