Protocol generator for on-wire and on-disk data formats for DAQ systems
https://ui.adsabs.harvard.edu/abs/2021APS..APRT20008B/abstra...



In computer networking, a wire protocol refers to a way of getting data from point to point: A wire protocol is needed if more than one application has to interoperate. It generally refers to communication protocols higher than the physical layer.[1] In contrast to transport protocols at the transport level (like TCP or UDP), the term wire protocol is used to describe a common way to exchange information at the application level. It refers to an application layer protocol and defines all the required attributes for the data exchange, like data types (units of data, message formats, etc.), communication endpoints[2] and capabilities (such as delivery guarantees, direction of communication, etc.). Usually, the data is represented at the application level as a common infoset (e.g. XML, JSON, YAML) and requires a mechanism of data binding (using e.g. a common encoding scheme like XSD).
https://en.wikipedia.org/wiki/Wire_protocol


Ceph on-wire encryption
https://access.redhat.com/documentation/en-us/red_hat_ceph_s...



This is a revision of the legacy Ceph on-wire protocol that was implemented by the SimpleMessenger. It addresses performance and security issues.
https://docs.ceph.com/en/quincy/dev/msgr2/

Q3: What is a 'wire-level' protocol?

A: A wire-level protocol can be thought of as the complement of an API. Instead of defining functions and creating libraries, you define the conversational byte sequences that pass over a network to make things happen.

When a protocol is specified at the wire-level and published, most technologies can use it, or be made to use it. Compare this to an API, where the actual implementation is specific to the platform.

JMS is an API. HTTP is a protocol. AMQP delivers the middleware equivalent of HTTP while leaving it up to others to provide implementations.
https://www.amqp.org/resources/developer-faqs#q3

As for what are "levels of protocol" search "OSI model".

Short of it:

"Total disks detected on-wire ..." would be "Total disks detected through on-wire protocols / some specific on-wire protocol ..."

IOW nothing much to do with any "physical wire" - it's got to do with "layers" of the OSI model.

No luck: no one bothered to make a French version of https://en.wikipedia.org/wiki/Wire_protocol




--------------------------------------------------
Note added at 9 hrs (2023-05-09 00:10:38 GMT)
--------------------------------------------------

Chapter 11 On-the-wire Protocols
http://ciaranmchale.com/corba-explained-simply/on-the-wire-p...


Definition of: wire protocol

(1) In a network, it is the mechanism for transmitting data from point a to point b. It often refers to a distributed object protocol such as SOAP, CORBA or RMI, which is software only and which invokes the running of programs on remote servers.

***The term is a bit confusing***, because it sounds like the physical layer (layer 1) of the network that places the bits "onto the wire." In some cases, it may refer to this layer; however, it generally refers to protocols higher than the physical layer or even the next higher data link layer (layer 2) such as Ethernet and ATM. See OSI model, communications protocol, data link protocol and distributed objects.

(2) In an electronic system, it refers to the control signals (start and stop transfer) and architecture (serial, parallel, etc.) of the bus or channel that transfers data.

https://web.archive.org/web/20121013111507/http://www.pcmag....