Then you are dealing with client timeouts or the fact that a lot of endpoints do not support url callbacks (for good reasons) or maybe clients that cannot be called back (for good reasons too).
Cannot say much about REST constraints outside of HTTP so excuse my ignorance on that. But I think it was clear the parent was referring to HTTP, or most possibly, GET and POST HTTP calls returning JSON.
Re:Post-REST
by icebraining on Monday November 19, 2018 @03:48PM
(#18489641)
You always have to deal with timeouts and other network issues, regardless of protocol.
Rather than retry every second, you retry on timeout.
And yet most HTTP APIs are going to give you a response with an status instead of holding it. I guess because it's much easier to implement and also assumes less on the consumer part. Then there was Comet and what resulted from that, websockets and server side events.
(That's assuming HTTP, which btw is not the only protocol which can implement REST constraints)