4 ms·
Why? What's so limiting about calling remote services over HTTP?
by mythz 8y ago
Why? What's so limiting about calling remote services over HTTP?
- londons_explore 8y agoHttp is pretty bad for long running requests (run this code which takes 6 hours), or bidirectional streaming (eg. Video conferencing) Other RPC mechanisms have no trouble with that.
- mythz 8y agoHooks are a popular approach for implementing notification callbacks for long running requests over HTTP. Bidirectional streaming is irrelevant here, the question is what's so limiting about using HTTP for this use-case? (i.e. by far the most popular protocol used for invoking remote service requests).
- bitcurious 8y ago>Hooks are a popular approach for implementing notification callbacks for long running requests over HTTP. Can you post an example/blog post of this approach?
- mythz 8y agoA good example is GitHub's Web Hooks which is common for notifying GitHub PR's of completed CI results: - https://developer.github.com/webhooks/ https://developer.github.com/webhooks/ There's also a Community WebHook plugin for ServiceStack: - https://github.com/jezzsantos/ServiceStack.Webhooks https://github.com/jezzsantos/ServiceStack.Webhooks