Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That document says that their messages were synchronous by default, and that asynchronous was something extra built on top just for distributed objects, not how they worked normally and not part of a uniform message passing interface.


Yes, it was up to you to change the behavior on doesNotUnderstand: methods, but the feature was available, just a matter of defaults.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: