Download to read offline
![Open, *[Read | Write], Close](https://image.slidesharecdn.com/interactionprotocols-190522103250/75/Interaction-Protocols-It-s-all-about-good-manners-29-2048.jpg)
![Open, *[Read | Write], Close
1. Open: ...
2. Read: ...
3. Write: ...
4. Close: ...](https://image.slidesharecdn.com/interactionprotocols-190522103250/75/Interaction-Protocols-It-s-all-about-good-manners-30-2048.jpg)
Uploaded byJ On The Beach
Interaction Protocols: It's all about good manners
The document discusses the importance of interaction protocols in communications and computing, exploring their definitions, applications, and implications across various realms such as evolutionary biology and distributed systems. It emphasizes the need for rigorous standards and considerations in protocol design, including versioning, encoding, and error handling, while posing reflective questions about the significance and study of these protocols. Ultimately, it challenges the reader to consider the foundational role of protocols as a key human discovery amid a landscape of technological evolution.
More Related Content
Similar to Interaction Protocols: It's all about good manners
Interaction Protocols: It's all about good manners
- 1. Interaction Protocols Martin Thompson- @mjpt777
- 2.
- 5. Are protocols themost significant human discovery?
- 6. protocol noun ˈprō-tə-ˌkȯl Source: http://www.merriam-webster.com/
- 7. protocol noun ˈprō-tə-ˌkȯl : a code prescribing strict adherence to correct etiquette and precedence Source: http://www.merriam-webster.com/
- 8. protocol noun ˈprō-tə-ˌkȯl : a code prescribing strict adherence to correct etiquette and precedence : a set of conventions governing the treatment and formatting of data in an electronic communications system Source: http://www.merriam-webster.com/
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15. “What is acceptable” Rulesof Engagement
- 16. “What is acceptable” “Goodconditions to succeed” Rules of Engagement
- 17. “What is acceptable” “Goodconditions to succeed” “Jus ad bellum, Jus ad bello” Rules of Engagement
- 18.
- 19. How do componentsInteract?
- 20.
- 22.
- 27. How should wedocument our protocols?
- 28.
- 29. Open, *[Read |Write], Close
- 30. Open, *[Read |Write], Close 1. Open: ... 2. Read: ... 3. Write: ... 4. Close: ...
- 31. Think events andthen consider: pre, post, and invariant conditions
- 32. “What can possiblygo wrong?”
- 34.
- 35. ACK / NAKImplosion
- 38. Where should wefocus?
- 39. Many Aspects toConsider • Layering • Versioning • Encoding • Addressing • Error Handling • Flow Control • Congestion Control • Feedback • Sequencing • Batching • Sync/Async • Validation • Trust • Privacy
- 40. Who cares aboutwaste?
- 41. Encoding Don’t use textcodecs! Please use binary codecs
- 42. Encoding “…but it’s humanreadable…”
- 43. 0 1 23 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-------------------------------------------------------------+ |R| Frame Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ | Version |B|E| Flags | Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+ |R| Term Offset | +-+-------------------------------------------------------------+ | Session ID | +---------------------------------------------------------------+ | Stream ID | +---------------------------------------------------------------+ | Term ID | +---------------------------------------------------------------+ | Encoded Message ... ... | +---------------------------------------------------------------+
- 44.
- 45. Versioning/Identity • Protocols: Whatconversation?
- 46. Versioning/Identity • Protocols: Whatconversation? • Messages: What encoding?
- 47. Versioning/Identity • Protocols: Whatconversation? • Messages: What encoding? • State: What instance?
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 75.
- 76.
- 77.
- 78.
- 79. “But, but, synchronous isso much easier...”
- 80. ...it’s all aboutmanaging state via feedback
- 81. Events model thereal world, i.e. it’s distributed, in space and time
- 82. When designing anAPI, wrap Async with Sync if you must
- 83. RPC / HTTP/ TCP
- 84. TCP → TCPFast Open → QUIC HTTP/1.1 → SPDY → HTTP/2 TLS 1.2 → TLS 1.3
- 86. 0-RTT and replayattacks
- 87.
- 88. Etiquette of arequest
- 89.
- 90.
- 91. sndmmsg, rcvmmsg() Onload, VMA DPDK,ef_vi, RDMA Verbs Future of Syscalls
- 92. Natural Batching & MechanicalSympathy
- 93.
- 94.
- 95.
- 97. “Two-Phase Commit isnot fault tolerant because it uses a single coordinator whose failure can cause the protocol to block”
- 98.
- 99. Applications should have feedback& recovery protocols
- 100.
- 101. Protocol Layering Depend onbehaviour, not implementation
- 102. Know and takeyour responsibilities seriously
- 103.
- 104. Are protocols themost significant human discovery?
- 105.
- 107. Why are protocolsnot studied and practiced more?
- 108. Your next project=> 1. Frameworks? or Protocols? 2. ...
- 109. Code of Conduct TheGolden Rule
- 110. @mjpt777 https://github.com/real-logic/aeron “A distributed systemis one in which the failure of a computer you didn't even know existed can render your own computer unusable.” - Leslie Lamport Questions?