-
-
Notifications
You must be signed in to change notification settings - Fork 0
MSG
The MSG command allows sending messages to other nodes, including objects, in the cyberspace.
MSG | ' [node-name] ["Message"] [>>] [>>] [>>]
Node-name can be a peer on the network, an object in an application, or a GROUP that you've set up or to which you've been subscribed. They cannot go to functions.
Messages without a node name are considered your own news, broadcast to all who subscribe to your channel. OR will send the message upwards "!^" (if you are inside any nodes, otherwise this is identical as sending it out). They will receive a message on their console, demarcated with your own node name, along with your text message.
MSG without a message do a ping to see if node is presently online. Once the node is present, the output will be "NODE is online", otherwise it will wait for a timeout value (set in the OS) and print "NODE time-out value reached."
NSG without either parameter will output the number of messages sent since bootup.
If, in the event of sending a message with double-quotes, you can repeat the double-quotes at the beginning and end for the message.
MSGs can go directly to the node named, or be queued upwards with the ">>" symbols. The more >> symbols the more significant it should be, as it is going to larger arenas/domains/supernodes.
Consider a low-level msg function that communicates between nodes, so that an object might subscribe to another object and catch exceptions (for example).
Singularity