You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an exploratory issue which we will update as we learn more.
There are a couple of aspects to this.
Currently, machines do not have any form of identification. This will require some way of referring to other machines in a user-friendly way.
When a machine connects to a channel, it should send a status message with its id and state.
When a machine receives a status message with a tuple of id and state which it has not previously seen, it should probably send its own status message.
Then, these need to be communicated to the end users.
Should they be announced as they come in, non-interruptingly? Should we wait until we have as many messages as there are machines to report all at once?
What changes need to be made in client. In server? Do we need to add more state to channels in the server?
The text was updated successfully, but these errors were encountered:
I guess it is also desirable to have an additional menu item which shows a dialog with this information.
What would be the most user friendly way to identify a machine? Something like a nick name?
This is an exploratory issue which we will update as we learn more.
There are a couple of aspects to this.
Currently, machines do not have any form of identification. This will require some way of referring to other machines in a user-friendly way.
When a machine connects to a channel, it should send a status message with its id and state.
When a machine receives a status message with a tuple of id and state which it has not previously seen, it should probably send its own status message.
Then, these need to be communicated to the end users.
Should they be announced as they come in, non-interruptingly? Should we wait until we have as many messages as there are machines to report all at once?
What changes need to be made in client. In server? Do we need to add more state to channels in the server?
The text was updated successfully, but these errors were encountered: