4 ms·
There is absolutely no problem implementing undo on the web with restful interfaces. I just built a quite complex data management application where almost anyth
by kika 13y ago
There is absolutely no problem implementing undo on the web with restful interfaces. I just built a quite complex data management application where almost anything is undoable in a very Photoshop way (you see the "History" pane in your UI and can undo whatever you desire). If something is not undoable there it's either a bug or NIY (not implemented yet).
The product is hardcore JS single page application backed by document oriented database, JSON, REST, buzz, buzz, buzz, etc.
- gizzlon 13y agoHow do you avoid that the users action have a cascading effect through the system? Was the undo/history option built in from the start? For example, your app inserts a new doc, some other process sees the new doc and updates a table or inserted into a message queue, it gets picked up by Foo and..
- kika 13y agoBuilt from the start, yes. and... what? you mean what would happen if I undo the creation of the doc? Like I was deleting the doc - the system either would not allow me because of the linked docs/events/objects or would do a cascade delete, if it can.
- gizzlon 13y agoMeant and.. a cascading effect resulting in 100 other actions you're only half-aware of, maybe on other systems =) So building the whole system with this in mind is probably a good idea.
- Piskvorrr 13y agoMoreover, that other proces need not be on the same server, or even on a server that you control; worse, it could trigger a meatspace effect. "User now authorized, access granted, door opened. [five minutes pass] Oops, that was a mistake." How do you undo _that_?