Protocol
A protocol is a defined set of rules and conventions governing how participants communicate, exchange information, or coordinate interactions.
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 →
Hidden Influences
A technical specification defining shared rules for how actions or communications are performed so independently provided services can interoperate.
- How it is used
- Frames shared protocols as an alternative to closed platforms that enables interoperability and service choice.
- How deep it goes
- Defines protocols through email interoperability and portability, without detailing technical implementation.
- Examples
- Uses email between different services and compares consistent calls across telephone carriers.
- What you can do after
- Understand how shared email rules let different services exchange messages and make switching services easier.
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.
Also covered in
- ActiveMQ in Action
- Acing the CCNA Exam: Volume 1 Fundamentals and Protocols
- Type-Driven Development with Idris
- Fundamentals of CybersecurityIn early access (MEAP)
- Designing AI SystemsIn early access (MEAP)
- Software Security for Developers
- Digital Twins in Action
- Quarkus in Action
- The Joy of JavaScript
- Designing Deep Learning Systems: A guide for software engineers
- Data-Driven Cybersecurity
- Rust in Action: Systems programming concepts and techniques
What to know first
- HTTPHTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems.
- JSONJSON is a language-independent text-based data-interchange format that represents structured values using objects, arrays, strings, numbers, booleans, and null.
- audit trailAn audit trail is a chronological record of actions, events, decisions, or changes maintained to support accountability, review, or investigation.
- clientA client is a person, organization, device, or software component that receives or uses a product, service, resource, or functionality provided by another party or system.
Related concepts
- transport connectorimplemented by · A transport connector is a broker component that exposes a connection endpoint to clients and accepts their connections.
- UDPincludes · The User Datagram Protocol (UDP) is a connectionless transport-layer protocol that sends datagrams without guaranteeing delivery, ordering, or duplicate suppression.
- contractkind of · A contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
Questions about protocol
What is protocol?
A protocol is a defined set of rules and conventions governing how participants communicate, exchange information, or coordinate interactions.
Which Manning books explain protocol?
Real-World Cryptography, Functional Design and Architecture: Examples in Haskell, Hidden Influences and Lead Developer Career Guide.
What should I know before learning protocol?
Manning books that teach protocol usually introduce HTTP, JSON, audit trail and client first.
What kinds of protocol are there?
Kinds of protocol include OpenWire, STOMP, UDP and binary protocol.
What is protocol a kind of?
Protocol is a kind of contract. A contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
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.



