Programming Distributed Erlang Applications Pitfalls and分布式程序设计的陷阱.pptVIP

下载本文档

3
0
约3.12千字
约 16页
2017-03-08 发布于上海
举报
版权申诉

Programming Distributed Erlang Applications Pitfalls and分布式程序设计的陷阱.ppt

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

Programming Distributed Erlang Applications Pitfalls and分布式程序设计的陷阱

Programming Distributed Erlang Applications: Pitfalls and Recipes+A More Accurate Semantics for Distributed Erlang Hans Svensson Chalmers University of Technology Lars-?ke Fredlund Universidad Politécnica de Madrid Erlang Workshop, Freiburg, 5 Oct. 2007 Two Papers One Talk!? Talking to the Dead Talking to the Dead Talking to the Dead Behind the scene N2 was stopped and restarted A new process managed to get exactly the same pid Since the pid data structure is finite, this is expected, however… The magic number is 3! This ‘feature’ can not be modeled even in the more accurate semantics Losing messages Behind the scene N1 and N2 was disconnected and later reconnected Easily discovered by using links Never rely on distributed communication without supervision This scenario can be correctly modeled in the improved semantics Distributed communication Distributed communication Behind the scene Only one (TCP-)connection between N1 and N2 A rather obscure guarantee Not recommended to exploit this guarantee in application, future runtime systems might break it This communication guarantee is not reflected in the semantics, there only the weaker guarantee holds Practical considerations There is always a difference between any model and the actual runtime system Artifacts of the OTP implementation of the runtime system should not be exploited Changes in the Semantics New rules for node disconnect Simplified rules for node failure and restart A more compact formulation of fairness Properties of the distributed semantics Extension Message reordering and node disconnect Expressiveness Finite systems stays finite Survey! Summary The possibility of reusing a Pid should not be neglected Distributed communication should always be supervised 3 is quite a small number, is it possible to use a larger number? A message from Lars-?ke He is at home, working on a new runtime system He has not figured out the complete semantics, yet! * Message passing guarantees McErlang Pitfalls A