How acridgold/netlabs works
This Kotlin application discovers live instances on an IPv4 or IPv6 multicast network. The workflow is: an operator supplies multicast settings, the command-line entry point validates them and selects an interface, then the discovery service sends and receives heartbeats, tracks peers, expires stale entries, and prints changes. Protocol handles heartbeat encoding and decoding; PeerRegistry holds the current peer state. Source excerpts show these runtime calls; no README content was provided.
Main entry points: SelfDiscovery.kt Discovery service · AppRunner.kt App runner · Main.kt Program entry · Config.kt Argument config
Components 9
Startup and configuration
- Program entry
lab1/src/main/kotlin/Main.kt - App runner
lab1/src/main/kotlin/AppRunner.kt - Argument config
lab1/src/main/kotlin/Config.kt
Peer discovery
- Discovery service
lab1/src/main/kotlin/SelfDiscovery.kt - Heartbeat protocol
lab1/src/main/kotlin/Protocol.kt - Peer registry
lab1/src/main/kotlin/PerRegestry.kt
Other components
- Operator
- Multicast network
- Peer instances
Connections 8
- Operator → Program entry: provides arguments
lab1/src/main/kotlin/Main.kt - Program entry → App runner: calls
lab1/src/main/kotlin/Main.kt - App runner → Argument config: parses settings
lab1/src/main/kotlin/AppRunner.kt - App runner → Discovery service: starts
lab1/src/main/kotlin/AppRunner.kt - Discovery service → Heartbeat protocol: formats and parses
lab1/src/main/kotlin/SelfDiscovery.kt - Discovery service → Peer registry: updates and prunes
lab1/src/main/kotlin/SelfDiscovery.kt - Discovery service → Multicast network: sends and receives
lab1/src/main/kotlin/SelfDiscovery.kt - Peer instances → Multicast network: exchanges heartbeats