Emulating the Essence of Erlang in RVI
summary
RVI claims to emulate core Erlang semantics on a store‑and‑forward IoT transport by implementing temporary internal reply service handles, JSON‑RPC wrappers that block until replies, and a record‑route style reply path so replies traverse the same relays. It uses signed JWT‑style credentials, an RV I event log for error replies, and multi‑node relay logic. There is a working prototype—version 0.50 available—with Debian packages, Android and iOS SDKs and Python libraries; not yet production ready.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:35What is Genivi
- 2:05What is RVI
- 4:47RVI Architecture
- 5:33handshake protocol
- 6:50access control
- 7:57asynchronous routing
- 9:25synchronous dialogues
- 10:21asynchronous dialogues
- 12:45different implementations
- 14:01clientserver calls
- 15:30delayed response
- 19:10MQTT
- 22:27Semantics
- 28:19Multinode relay
- 30:32Reply path
- 33:16Status
- 35:32Questions
- 37:16JSON Web Tokens
- 38:34Any Car
related talks
45mElixir and the Internet of Things
01h 03mThinking Erlang in a connected world
20mBuilding an IoT Demand Response solution with Elixir
27mDistributed Robots with Elixir
49mConnecting the Internet of Things
06mIntroducing Raxx, an Elixir Webserver Interface
42mMessage passing for actors and humans with Raxx
44mElmrang Connect