[pubsubhubbub] Re: 6.1 sync/async

[Jay Rossiter]

I do have to agree with others in that the complexity isn't isolated to the hub.  Since it's clear that various hubs are implementing either sync or async (but rarely both, from the conversations here), it means that the subscriber is required to support both, if it wants interoperability with all hubs.     I think that at the hub, both sync and async should be mandatory, and the subscribers should be able to do whatever is easiest for them. On 10/18/2009 2:11 PM, Brad Fitzpatrick wrote: 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 <timb...@gmail.com> 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 -- Jay Rossiter | Software Engineer/System Administrator Pioneering RSS Advertising Solutions jrossi...@pheedo.com | Phone: 503.896.6187 | Fax: 503.235.2216 Website: www.pheedo.com | RSS: www.pheedo.info/index.xml