4 ms·
Message-passing better than STM? Wonder why?
by DanielBMarkham 14y ago
Message-passing better than STM? Wonder why?
- matthavener 14y agoI think two reasons: 1) VxWorks directly supports message passing (http://www.vxdev.com/docs/vx55man/vxworks/ref/msgQLib.html http://www.vxdev.com/docs/vx55man/vxworks/ref/msgQLib.html). 2) They seem to prefer simple, obvious, "less magic" interfaces. STM is nice for its "magic", but message creates very well defined, documented interfaces between code.
- deno 14y ago> STM is nice for its "magic", but message creates very well defined, documented interfaces between code. The author’s previous post has a good overview of how message passing contributes to that as well. http://jlouisramblings.blogspot.com/2012/06/protocols-in-kingdom-of-distribution.html http://jlouisramblings.blogspot.com/2012/06/protocols-in-kin...
- jlouis 14y agoDifferent. If you squint your eyes enough, the Erlang mnesia application is an implementation of (distributed) STM. STM and MP are not a priori against each other. You can have both and sometimes one is better than the other for a certain kinds of problems.