> To your second point, Subscribers should never synchronously process > updates. They should be dumped immediately to a job queue for asynchronous > processing. This will help spread the processing load more evenly over time > instead of being clumped together which I gather is what you're against. So > it's receive update, verify it is an update (input validation), dump update > to queue, and respond with a 200 code. > > Actually I don't see anything wrong with handling the event synchronously. While it's courteous to the hub, the hubs will HAVE to be able to handle this because that's just how most people will do it. From the subscriber perspective, a job queue is unnecessary because their web server should already be handling the request asynchronously. Apache is generally already a big worker pool using incoming HTTP requests as the job queue.
-- Jeff Lindsay http://webhooks.org -- Make the web more programmable http://shdh.org -- A party for hackers and thinkers http://tigdb.com -- Discover indie games http://progrium.com -- More interesting things
