byte-oriented protocol
≈ 2 min read
Names in other languages
- Русскийбайт-ориентированный протокол
- УкраїнськаБайт-орієнтований протокол
- Englishbyte-oriented protocolbyte-oriented framing protocol, character-oriented protocol, octet-oriented protocol
- ČeštinaZnakově orientovaný
- eobajtema protokolo
- 한국어바이트 지향 프로토콜
- 中文面向字节的协议基于字节, 面向字节协议
- 繁體中文基於位元組面向位元組協議
- 中文基于字节面向字节协议
- 简体中文基于字节面向字节协议
Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.
Byte-oriented framing protocol is "a communications protocol in which full bytes are used as control codes. Also known as character-oriented protocol." For example UART communication is byte-oriented. The term "character-oriented" is deprecated, since the notion of character has changed. An ASCII character fits to one byte (octet) in terms of the amount of information. With the internationalization of computer software, wide characters became necessary, to handle texts in different languages. In particular, Unicode characters (or strictly speaking code points) can be 1, 2, 3 or 4 bytes in UTF-8, and other encodings of Unicode use two or four bytes per code point.
Byte-oriented framing protocol is "a communications protocol in which full bytes are used as control codes. Also known as character-oriented protocol." For example UART communication is byte-oriented. The term "character-oriented" is deprecated, since the notion of character has changed. An ASCII character fits to one byte (octet) in terms of the amount of information. With the internationalization of computer software, wide characters became necessary, to handle texts in different languages. In particular, Unicode characters (or strictly speaking code points) can be 1, 2, 3 or 4 bytes in UTF-8, and other encodings of Unicode use two or four bytes per code point.
See also
Bit-oriented protocol
References
Text derived from https://en.wikipedia.org/w/index.php?oldid=1374163875 under CC BY-SA 4.0; modifications have been made.