Bus definition

[antoineDeRengerve]

• Where is given the config ?
• Choice of comm type ?
• How bus are related to peers or channels ? (one2one ? many2one ?) Is it possible to define UDP and TCP in parallel to the same peer ?

[nilpotence]

The bus's purpose is to establish a signaling channel/negociation channel between peers. the only configuration needed should be for example the broadcast address the bus is backed by Ivy.

The negociation is the process by which two peers determine the best way to connect their I/O. Each peer exchange information about which transport is available (for example shm/tcp/udp) and the remote peer chooses among these transports the best one depending on whatever constraint it has (shm if local and async, udp if local and sync, etc).

If a peer declares an output, multiple remote peers should be able to connect to it, using whatever transport is available (so two peer connecting at the same time with different transport should work).
If a peer declares an input, then only the first remote peer that tries to connect to it can do so, using whatever transport is available.
If we decide to implement InputOutput channels, then I guess we should let the library user decide which policy to use.