Protocol
A protocol is a defined set of rules and conventions governing communication or interaction among systems, components, or participants.
Real-World Cryptography
A prescribed set of communication rules and computational steps followed by participants to achieve a specified outcome.
- How it is used
- Frames protocols as step-by-step recipes for participants pursuing shared outcomes under adversarial conditions.
- How deep it goes
- Moves from plain-language steps to cryptographic composition and misuse warnings without formal mathematical treatment.
- Examples
- Uses an unattended magic sword, confidential messages, and Lego-like primitive composition to illustrate protocol design and failure.
- What you can do after
- Evaluate/understand protocol security by identifying goals, adversaries, cryptographic ingredients, composition risks, and safer implementation choices.
Functional Design and Architecture: Examples in Haskell
A communication protocol is a defined set of rules and message formats governing interactions between communicating software components.
- How it is used
- Coordinates actor interactions by hiding the environment behind a request–response contract.
- How deep it goes
- Defines contracts and demonstrates an MVar implementation, while stopping short of prescribing one response to invalid messages.
- Examples
- Uses spaceship actors, real-versus-virtual environments, FizzBuzz workers, and mismatched calculation responses.
- What you can do after
- Build it from scratch with MVars, request–response workers, and typed request and response data.
Read how Functional Design and Architecture: Examples in Haskell explains protocol →
Lead Developer Career Guide
A defined set of rules governing how information is reported, shared, updated, and escalated during an incident.
- How it is used
- Coordinates emergency reporting, updates, decision-making, and escalation among team members and stakeholders.
- How deep it goes
- Defines channels, roles, timing, contacts, and escalation backups, stopping short of detailing a particular technical implementation.
- Examples
- Uses email groups, chat platforms, emergency numbers, timed updates, central contact documents, and a Confluence emergency plan.
- What you can do after
- Operate/configure an emergency communication routine with assigned roles, channels, update intervals, and team-based escalation.
Related concepts
- contractkind of · An API contract is a specification of the operations, data, and behavioral expectations that govern interactions between software components.
- HTTPincludes · HTTP is a standardized application-layer protocol that defines request-and-response messages for transferring resource representations between networked systems.
- Online Certificate Status Protocolincludes · The Online Certificate Status Protocol is a protocol for querying an authority about the current revocation status of a digital certificate.
- TLSincludes · Transport Layer Security (TLS) is a cryptographic protocol that protects network communications through confidentiality, integrity, and authentication of communicating endpoints.
- A2Aincludes · A2A is an interoperability protocol that enables software agents to discover, communicate, and coordinate with one another across systems.
- two-phase commitincludes · Two-phase commit is a distributed transaction protocol that prepares participating systems and then coordinates their collective commitment or abortion.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.