TCP
1. TCP  tcp
properties
ID: a2c33f5d-8e07-4122-98df-72d321ae313bCREATED: <2025-01-18 Sat 20:42>
1.1. WebSocket
properties
ID: 52a7cb9d-5b78-4681-9146-2d8f5707c1a3CREATED: <2025-02-16 Sun 20:41>
- layer on top of TCP
- The WebSocket API (WebSockets) - Web APIs | MDN
1.2. HTTP  http
properties
ID: 5c9b8b56-6c37-4171-8da1-ac6e4e3cd0a1CREATED: <2025-01-18 Sat 20:42>
Hypertext Transfer Protocol (HTTP) is an application-layer protocol for transmitting hypermedia documents, such as HTML. It was designed for communication between web browsers and web servers, but it can also be used for other purposes. HTTP follows a classical client-server model, with a client opening a connection to make a request, then waiting until it receives a response. HTTP is a stateless protocol, meaning that the server does not keep any data (state) between two requests. Though often based on a TCP/IP layer, it can be used on any reliable transport layer, that is, a protocol that doesn't lose messages silently like UDP does. RUDP - the reliable update of UDP - is a suitable alternative.
1.2.1. HTTP/1.1
properties
ID: 95274690-c607-4c94-9416-707f478814aeCREATED: <2025-09-30 Tue 15:40>
1.2.2. HTTP/2
properties
ID: 2d727cb5-b30c-47f8-b208-eccd1d32d40dCREATED: <2025-09-30 Tue 15:40>
1.2.3. HTTPS  tls
properties
ID: 81e78198-a5ed-4fdd-b487-1bb3874ffa71CREATED: <2025-02-16 Sun 20:40>
edges
– The HTTPS-Only Standard - The HTTPS-Only Standard
– HTTPS - MDN Web Docs Glossary: Definitions of Web-related terms | MDN
<< QUIC
- HTTPS consists of HTTP with the addition of TLS
- HTTP/S is used as a blanket statement for both HTTP and HTTPS
1.2.4. REST
properties
ID: c0cc13d2-f8c2-4772-9a1e-86e406e118bfCREATED: <2025-09-29 Mon 19:40>
1.2.5. GraphQL
properties
ID: 3cf5d8cb-c70b-4ba3-a166-d69e740a5505CREATED: <2025-09-29 Mon 19:40>
1.3. DICT
properties
ID: 407f25fd-aab0-4aa5-a994-abb1be11fae5CREATED: <2025-10-11 Sat 22:30>
AKA: Dictionary Server Protocol
Query/Response protocol which allows a client to access dictionary definitions from a set of natural language dictionary databases.
port 2628
For many years, the Internet community has relied on the "webster" protocol for access to natural language definitions. The webster protocol supports access to a single dictionary and (optionally) to a single thesaurus. In recent years, the number of publicly available webster servers on the Internet has dramatically decreased.
Fortunately, several freely-distributable dictionaries and lexicons have recently become available on the Internet. However, these freely-distributable databases are not accessible via a uniform interface, and are not accessible from a single site. They are often small and incomplete individually, but would collectively provide an interesting and useful database of English words. Examples include the Jargon file, the WordNet database, MICRA's version of the 1913 Webster's Revised Unabridged Dictionary, and the Free Online Dictionary of Computing. (See the DICT protocol specification (RFC) for references.) Translating and non-English dictionaries are also becoming available (for example, the FOLDOC dictionary is being translated into Spanish).
The webster protocol is not suitable for providing access to a large number of separate dictionary databases, and extensions to the current webster protocol were not felt to be a clean solution to the dictionary database problem.
The DICT protocol is designed to provide access to multiple databases. Word definitions can be requested, the word index can be searched (using an easily extended set of algorithms), information about the server can be provided (e.g., which index search strategies are supported, or which databases are available), and information about a database can be provided (e.g., copyright, citation, or distribution information). Further, the DICT protocol has hooks that can be used to restrict access to some or all of the databases.