Wire protocol

In <a href="/facts/Computer_networking/3w5RM99p">computer networking</a>, a wire protocol refers to a way of getting <a href="/facts/Data/AUBFN97o">data</a> from point to point: A wire protocol is needed if more than one application has to interoperate. It generally refers to <a href="/facts/Communication_protocol/5uady7cB">communication protocols</a> higher than the physical layer. In contrast to <a href="/facts/Transport_protocol/UmIGUCeK">transport protocols</a> at the transport level (like <a href="/facts/Transmission_Control_Protocol/WW4sPrt9">TCP</a> or <a href="/facts/User_Datagram_Protocol/dxLU0D6q">UDP</a>), the term wire protocol is used to describe a common way to exchange information at the application level. It refers to an <a href="/facts/Application_layer/FAFhLruA">application layer</a> protocol and defines all the required attributes for the data exchange, like data types (units of data, message formats, etc.), communication endpoints and capabilities (such as delivery guarantees, direction of communication, etc.). Usually, the data is represented at the application level as a common <a href="/facts/Infoset/xcvm1e1A">infoset</a> (e.g. <a href="/facts/XML/clNgUfWk">XML</a>, <a href="/facts/JSON/bs1rUAhd">JSON</a>, <a href="/facts/YAML/mAY10H2Y">YAML</a>) and requires a mechanism of data binding (using e.g. a common encoding scheme like <a href="/facts/XSD/X6Uly3dm">XSD</a>).
The wire protocol may be either text-based or a <a href="/facts/Binary_protocol/Nmj0lyxI">binary protocol</a>. Although an important architectural decision, this is a separate matter from the distinction between wire protocols and programmatic APIs.
In <a href="/facts/Electronics/E4JhgISq">electronics</a>, a wire protocol is the mechanism used to transmit data from one point to another.

Wire protocol open-in-new

Wire protocol