URSYS Message Distribution Rules

[dsriseah]

There are subtleties in how messages are routed. In this version of URSYS, there both "local" and "network" message.

Local messages are defined on the local Endpoint only, and do not go out to the server

Call      ('MESSAGE', data).then( response => {} );
Send      ('MESSAGE', data).then( success => {} );
Signal    ('MESSAGE', data);
Ping      ('MESSAGE').then( count => {} );

Network (or SRV:) messages are send to the message dispatcher on the URNET server.

NetCall   ('NET:MSG', data).then( response => {} );
NetSend   ('NET:MSG', data).then( success => {} );
NetSignal ('NET:MSG', data);
NetPing   ('NET:MSG').then( uaddr[] => {} );

Messages can have multiple handlers, so URNET has to figure out who gets what.

The distinction between each type:

• Call is used for data transactions, and currently invokes all message handlers defined for the message
• NetCall probably should not invoke the same message from the originator.
• Send is a one-way data send with confirmation
• NetSend probably should work like NetCall and not invoke the originating caller
• Signal is used for BROADCASTED data, like state changes
• NetSignal should invoke all implementors, including the caller
• Ping is used to see if a message handler exists, returning a count
• NetPing returns the list of UADDR that implement the message

TO RESOLVE

• [ ] Update NetCall to not route to originator
• [ ] Update NetSend to not route to originator