Needed if more than one application has to interoperate.- Wire protocol
8 related topics
Open standard application layer protocol for message-oriented middleware.
Unlike JMS, which defines an API and a set of behaviors that a messaging implementation must provide, AMQP is a wire-level protocol.
In computing, D-Bus (short for "Desktop Bus" )
The D-Bus specification defines the wire protocol: how to build the D-Bus messages to be exchanged between processes within a D-Bus connection.
Type of DNS transaction.
Zone transfer operates in terms of "wire format" resource records, i.e. resource records as they are transferred using the DNS protocol.
Binary protocol designed for working with message-oriented middleware.
It is the native wire format of ActiveMQ.
Free and open-source cross-platform data format used to serialize structured data.
Canonically, messages are serialized into a binary wire format which is compact, forward- and backward-compatible, but not self-describing (that is, there is no way to tell the names, meaning, or full datatypes of fields without an external specification).
Simple text-based protocol, designed for working with message-oriented middleware (MOM).
It provides an interoperable wire format that allows STOMP clients to talk with any message broker supporting the protocol.
Creating a copy of an existing object, a unit of data in object-oriented programming.
This is typically used for persistence and wire protocol purposes, but it does create copies of objects and, unlike clone, a deep copy that gracefully handles cycled graphs of objects is readily available with minimal effort from a programmer.
Information that passes over computer and telecommunication networks defining communications between client and server devices.
It is the result of decoding wire and transport protocols containing the bi-directional data payload.