sync is a bit simpler for subscribers. For example, I have a function that I call to subscribe to a topic through PuSH - it's really convenient to know, when it returns, whether or not the subscription was successful. With async, I'd either have to wait for the response in that function (eww), or move that logic into higher layers of my implementation. --Ravi
On Sat, Oct 17, 2009 at 11: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 >
