network library
Classes
- CoordinationSession
- Abstract base class for coordination sessions.
- CoordinationSessionConfig
- CoordinationSessionConfigFactory
- CoordinatorNode
- Coordinator nodes can coordinate the network, and may also participate in data streams (if they have the capability).
- HierarchicalTopologyConfig
- HierarchicalTopologyConfigFactory
- Node
- Configuration for the LSL transport.
- NodeConfig
- NodeConfigFactory
- Factory for creating NodeConfig objects.
- NodeFactory
- ObserverNode
- A node that does not participate in the network at all. Observer nodes can only observe the network, and cannot participate in sending data or and cannot coordinate. They can receive coordination messages, but cannot send them.
- ParticipantNode
- Participant nodes can produce and consume data, but cannot participate in coordination (but will receive coordination messages).
- PeerMetadataKeys
- Keys for the node metadata the coordination layer itself reads.
- PeerRegistry
- The set of peers currently reachable on a relay-style transport.
- PeerSession
- A coordination session, independent of any transport.
- PromotionStrategy
- Promotion strategy
- PromotionStrategyFirst
- PromotionStrategyRandom
- RegistryDelta
- A change to the set of registered peers.
- RelayNode
- Relay nodes can relay data between nodes, but cannot produce or consume data (non-relayed) themselves.
- RelayRouting
- Who receives what, on a relay-style transport.
- TopologyConfig
- Represents the network topology used in the coordinator system. Currently, only hierarchical topology is supported.
- TransformerNode
- Transformer nodes are a special case of relay nodes that can also transform data as it passes through them.
Enums
- CoordinatorLossPolicy
- What a node does when the coordinator goes away.
- NodeCapability
- Represents the type of a node in the network. Type, in this case means essentially the MAXIMUM privileges and capabilities of the node in the network. An observer node, will never be allowed to produce data, while a coordinator node will be able to produce coordination messages, but will not be able to produce data in data streams.
- RegistryChange
- How a registered peer changed.
- SessionEndReason
- Why a session ended, as carried by SessionEndedEvent and SessionEndMessage.