Integrate Network Shared Memory into a Complete Workflow
This is the original FrogNet journey. Build the network first. Watch each mechanism work. Shared Memory arrives after you understand the problems that caused it to exist.
The progression is deliberate.
You are not asked to accept a new distributed-programming model on page one. Each stage gives you something running and introduces only the next problem.
The videos belong beside the stage they explain.
These are desk demonstrations: the system running, the code on screen, and the engineering reason for what is being done. They are evidence and instruction, not a polished sales presentation.
Installation
Hardware, installation parts 1 and 2, broker installation and first bring-up.
Discovery
Discovery deep dive and follow-up material while the network is still understandable as a network.
Semantic path
Proxy/daemon and semantic compression before the programming model asks the reader to depend on them.
Security
Security and Security by Architecture at the point the path leaves one local network.
Memory
Shared Memory and tuple material after the reader has seen why the state exists.
Communicator
Bring networking, shared state and adaptive media together in one application.
Sensors lead to state. State leads to Memory. Memory changes the program.
The long path keeps that discovery intact. The short Internet RAM path merely lets somebody enter from the other end.