Fair points, got me convinced. Guess I just began wondering when I started blocking the running thread in the code :-)
On 06 Feb 2009, at 13:44, Alex Miller wrote: > It seems to me that most of the time, you are going to have a > question and want the answer before proceeding. Certainly the synch > model is easier and cleaner to program against (with the downside of > blocking the calling thread). Although you mention that it's easier > to layer sync on top of async, I don't think there's anything that > would prevent you from providing sync now and exposing async later > as well. > > I would rather err on the side of easy to program and explain right > now and open up for a non-blocking implementation later if it's > needed. > > While I can invent an async use case in my head, I don't see a > compelling need for it right now at the cost of complexity. -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Flytecase Band - http://flytecase.be Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
