"Webhooks are "user-defined HTTP callbacks".[2] They are usually triggered by some event, such as pushing code to a repository[3] or a comment being posted to a blog.[4] When that event occurs, the source site makes an HTTP request to the URI configured for the webhook. Users can configure them to cause events on one site to invoke behaviour on another. The action taken may be anything. Common uses are to trigger builds with continuous integration systems[5] or to notify bug tracking systems.[6] Since they use HTTP, they can be integrated into web services without adding new infrastructure.[7]"
ASP.NET WebHooks RC 1
Announcing ASP.NET WebHooks Release Candidate 1 | .NET Web Development and Tools Blog
Sending ASP.NET WebHooks from Azure WebJobs | .NET Web Development and Tools Blog
WebHooks.org
Webhooks | GitHub Developer Guide
Platform as a service(PaaS) using Docker and Github | Paxcel Labs
DraganSr: WebHooks (October 2015)
The semantics of callbacks is not standardized, so is just one more way to make HTTP API calls, different for each site. Is increasing complexity of web-based systems avoidable?
No comments:
Post a Comment