I think the complexity cuts into the Subscriber just as much. See R P's last few emails about asynchronous support in a Subscriber. The trend, which is barely a blip this early in Pubsubhubbub's life, seems to be towards synchronous support as the sole exclusive option. I'd prefer async since it uses less resources, and it's easy (then again, I use a framework which makes it that easy), but it's obviously not in wide use judging from my experiences so far.
Paddy Pádraic Brady http://blog.astrumfutura.com http://www.survivethedeepend.com OpenID Europe Foundation Irish Representative ________________________________ From: Brad Fitzpatrick <[email protected]> To: [email protected] Sent: Sun, October 18, 2009 10:11:46 PM Subject: [pubsubhubbub] Re: 6.1 sync/async We debated this for a long time. There are groups of people adamant about both ways. :-/ In keeping with the overall design goal of keeping pub+sub simple and pushing complexity to the hub, we chose to push complexity to the hub here. On Sat, Oct 17, 2009 at 9:45 PM, Tim Bray <[email protected]> wrote: >>I read this one and I'm thinking YAGNI. It seems like the flexibility >>here adds complexity and doesn't really buy that much. Why not just >>settle on async and leave it at that? > >> -T >
