3 ms·
Hmm. This would require a representation of the complete state history in resource urls, wouldn't it? I can only come up with something like /image/edit1/edit2/
by strictfp 13y ago
Hmm. This would require a representation of the complete state history in resource urls, wouldn't it? I can only come up with something like /image/edit1/edit2/edit3/edit4 where going back would bring you to /image/edit1/edit2/edit3.
I suppose you can also do something state-based
like /image/state4 going back to /image/state3. This would push the storage of the edit stack to the server.
Is this what you mean?
- barrkel 13y agoYes; with request / responses reanimating a continuation, and with a copy-on-write tree of activation records instead of a stack. But the usability probably wouldn't be fantastic.