This YEP defines the transport layer for yaq daemon communication as a Transmission Control Protocol (TCP) Socket. The contents of the data transfer are defined in YEP 100.
This is a foundational piece of the yaq daemon infrastructure. TCP was chosen because it is ubiquitous, with interfaces in many languages and platforms. Additionally, the use of TCP/IP provides for the natural ability to use both local and remote daemons in the same experimental configuration.
Each Daemon opens up one TCP/IP port. This port SHOULD serve on ports 36000-39999. This range avoids collisions with most common port usage in other applications, however care should be taken to avoid conflicting with other programs on the host machinee. Additionally, yaq ecosystem tools which scan to identify daemons will only look in this range by default.
This port is specified in the configuration file YEP 102.
Discussion can be found on the gitlab issue for this YEP.
This document is placed in the public domain or under the CC0-1.0-Universal license, whichever is more permissive.
built 2020-05-20 22:19:23 CC0: no copyright