Re:Introspected REST: An alternative to REST and GraphQL
by jayd16 on Saturday December 22, 2018 @01:50PM
(#18741890)
How does a websocket solve this? You still have multiple commands going through your websocket which could still conflict with another user's actions.
If you make the actions atomic, you could use REST. If you use a transaction, you could use REST even still. Letting client code consume locks is frowned upon, but doing it through a websocket doesn't make it better.
My point is REST is the worst solution except for all the other solutions.
If you make the actions atomic, you could use REST. If you use a transaction, you could use REST even still. Letting client code consume locks is frowned upon, but doing it through a websocket doesn't make it better.
My point is REST is the worst solution except for all the other solutions.