4 ms·
I found this discussion a bit incomplete as it didn't really discuss the consequences or costs or benefits of modelling things one way or another. Suppose we d
by shoo 8y ago
I found this discussion a bit incomplete as it didn't really discuss the consequences or costs or benefits of modelling things one way or another.
Suppose we didn't use REST or HTTP for our API. What would be a good way to model this kind of thing?
- realthing 8y agoI suppose one way of modeling a solution to this space is to look back at goold 'ol fashioned RPC's
- jmts 8y agoThis is essentially just an asynchronous response to some request. I expect there are probably three cases: 1. Response is unimportant: do nothing 2. Response timing is not important: client polls 3. Response timing is important: server calls back into the client somehow The article describes an implementation of point 2. Depending on the technologies available at the time, I'd argue 3 is probably more versatile. Both cases 1 and 2, and the blocking case can be implemented with case 3, if the available technology allows it.