Protocols
Saved & recent

Capability negotiation

Also called: feature negotiation, capability exchange

Capability negotiation lets communicating programs discover which optional features they can use together. Version numbers alone may not reveal whether a particular implementation supports compression, streaming or a specialized operation. A protocol can exchange feature declarations and parameters, then define how to choose mutually usable behavior.

Imagine a client supporting compression and batching, while a server supports compression and streaming. Under a simple agreed selection rule, they can use compression but cannot assume the other two features. Real protocols must define defaults, required features and incompatible settings. DAP, for example, uses explicit capability flags for optional features. These declarations describe abilities; access to an operation still depends on separate authorization rules.

Read first
Protocol extensibility
Related
Version negotiation, LSP initialization, MCP capability negotiation
Further reading
compression batching compression streaming client server compression shared capability separate permission check hypothetical intersection rule
An agreed negotiation rule selects shared functionality; unsupported features and access permissions require separate handling.

View in the full Protocols collection