<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: googlecodehosting</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/googlecodehosting.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2009-02-04T10:22:06+00:00</updated><author><name>Simon Willison</name></author><entry><title>Post-Commit Web Hooks for Google Code Project Hosting</title><link href="https://simonwillison.net/2009/Feb/4/webhooks/#atom-tag" rel="alternate"/><published>2009-02-04T10:22:06+00:00</published><updated>2009-02-04T10:22:06+00:00</updated><id>https://simonwillison.net/2009/Feb/4/webhooks/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://google-code-updates.blogspot.com/2009/01/post-commit-web-hooks-for-google-code.html"&gt;Post-Commit Web Hooks for Google Code Project Hosting&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I really, really like web hooks (which I’ve been calling “callback APIs”, but it looks like “web hooks” is the term that’s sticking). I’m interested in their scaling challenges—I’ve heard XMPP advocates argue that a web hook style model simply won’t scale for really large sites.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://bitworking.org/news/405/webhooks"&gt;Joe Gregorio&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/googlecodehosting"&gt;googlecodehosting&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/webhooks"&gt;webhooks&lt;/a&gt;&lt;/p&gt;



</summary><category term="google"/><category term="googlecodehosting"/><category term="webhooks"/></entry></feed>