ddsf:public:guidebook:06_append:glossary:w:wireprotocol
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
ddsf:public:guidebook:06_append:glossary:w:wireprotocol [2021/07/14 15:44] murphy ↷ Links adapted because of a move operation |
ddsf:public:guidebook:06_append:glossary:w:wireprotocol [2021/07/14 16:46] (current) murphy ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Wire Protocol ===== | ===== Wire Protocol ===== | ||
| - | [[ddsf:private:guidebook:06_append:glossary:start| Return to Glossary ]] | + | [[ddsf:public:guidebook:06_append:glossary:start| Return to Glossary ]] |
| - | **Wire Protocol** refers to a way of getting data from [[ddsf:private:guidebook:06_append:glossary:p:point-to-point|point-to-point]]: A Wire [[ddsf:private:guidebook:06_append:glossary:p:protocol]] is needed if more than one application has to interoperate. It generally refers to protocols higher than the [[ddsf:private:guidebook:06_append:glossary:p:physicallayer|physical layer]]. In contrast to transport protocols at the transport level (like [[ddsf:private:guidebook:06_append:glossary:t:tcp]] or [[ddsf:private:guidebook:06_append:glossary:u:udp]]), the term "wire protocol" is used to describe a common way to represent information at the Application Level of the [[ddsf:private:guidebook:06_append:glossary:o:osi]]. It refers only to a common [[ddsf:public:guidebook:06_append:glossary:a:applayer]] protocol and not to a common object semantic[clarification needed] of the applications. Such a representation at application level needs a common [[ddsf:private:guidebook:06_append:glossary:x:xml_infoset]] and a data binding (using e.g. a common encoding scheme like [[ddsf:private:guidebook:06_append:glossary:x:xsd]]). | + | **Wire Protocol** refers to a way of getting data from [[ddsf:public:guidebook:06_append:glossary:p:point-to-point|point-to-point]]: A Wire [[ddsf:public:guidebook:06_append:glossary:p:protocol]] is needed if more than one application has to interoperate. It generally refers to protocols higher than the [[ddsf:public:guidebook:06_append:glossary:p:physicallayer|physical layer]]. In contrast to transport protocols at the transport level (like [[ddsf:public:guidebook:06_append:glossary:t:tcp]] or [[ddsf:public:guidebook:06_append:glossary:u:udp]]), the term "wire protocol" is used to describe a common way to represent information at the Application Level of the [[ddsf:public:guidebook:06_append:glossary:o:osi]]. It refers only to a common [[ddsf:public:guidebook:06_append:glossary:a:applayer]] protocol and not to a common object semantic[clarification needed] of the applications. Such a representation at application level needs a common [[ddsf:public:guidebook:06_append:glossary:x:xml_infoset]] and a data binding (using e.g. a common encoding scheme like [[ddsf:public:guidebook:06_append:glossary:x:xsd]]). |
| It generally refers to higher layers, including [[ddsf:public:guidebook:06_append:glossary:e:ethernet|Ethernet]] and ATM (layer 2) and even higher layer distributed object protocols such as SOAP, [[ddsf:public:guidebook:06_append:glossary:c:corba|CORBA]] or RMI. | It generally refers to higher layers, including [[ddsf:public:guidebook:06_append:glossary:e:ethernet|Ethernet]] and ATM (layer 2) and even higher layer distributed object protocols such as SOAP, [[ddsf:public:guidebook:06_append:glossary:c:corba|CORBA]] or RMI. | ||
ddsf/public/guidebook/06_append/glossary/w/wireprotocol.1626291864.txt.gz · Last modified: 2021/07/14 15:44 by murphy
