On Sat, Aug 20, 2011 at 1:41 AM, BGB <cr88...@gmail.com> wrote: > either, it is a reference to a method call, having no obvious differences, > or it is referring to something different, and the "issues" with this other > thing are not an issue in the context of a method call.
You present a false dichotomy. The 'issues' have a shared root cause that holds for method calls and other messaging mechanisms. > > IRL, many protocols are built on top of UDP, and as such are designed to > deal with matters of packet loss/duplication/ordering/... Ability to implement other communication models atop messaging (and vice versa) does not counter any flaws of messaging. > > a well designed API is also designed to hold up to some level of > abuse The amount of effort, foresight, and expertise it takes to design a robust API is significantly affected by the computation and communication models, and language. If developers have to work really hard for a nice property, especially if across multiple libraries, it simply won't happen except in project-specific ways. _______________________________________________ fonc mailing list fonc@vpri.org http://vpri.org/mailman/listinfo/fonc
