MV System - modrpc/info GitHub Wiki
- RPC task call can fail -- MV provides way to handle failures.
- Some systems already allows to add to callbacks - success callback + failure callback.
- Can we make this more naturally fit sequential programming model (not reactive model).
- The server is responsible for maintaining a persistent table of device names.
- A device must register its name to the server (just like "userid" in a website) and server will grant the name only when there is no such device name at the time.
- A device must also provide a password, which will be used when signing on to the Meadow network.
- The server is responsible for maintaining a transient table of device addresses.
- For example, an IP address of a device, say "DEV0" can change. When a device signs on to the network, it must inform the device of its address. A device which wants to use the services of "DEV0" must contact the server to get the latest device address.
- Like NPM (Node.js), it manages (installs, uninstalls, etc.) MV modules.