Access status on a device

[rsiewert]

Per the registration of a device, it should have communicated to any other device the messaging protocol and endpoint for publishing/queuing. Any device on the network is entitled to know what the status of another device is. So for this issue the device should be able to respond to a message asking for status of any particular device on the network.

[rbgodwin]

I think we might need some kind of authentication. Should every device should be able to know about all the endpoints of all other devices? Perhaps devices could function like chat nodes operate where a device could request permissions from another device to perform particular things such as ask for status, but could not control the device. Others might have permission to read and control a device.

[rsiewert]

yes this is a major area that needs to be addressed once we have devices talking/controlling each other...this really needs to have a major discussion/research and probably several sprints to accomodate

On Tuesday, March 4, 2014 2:40 AM, rbgodwin notifications@github.com wrote:

I think we might need some kind of authentication. Should every device should be able to know about all the endpoints of all other devices? Perhaps devices could function like chat nodes operate where a device could request permissions from another device to perform particular things such as ask for status, but could not control the device. Others might have permission to read and control a device. — Reply to this email directly or view it on GitHub.

[rbgodwin]

Device currently registers and provides a protocol that any other device can subscribe to. The device publishes status messages with a period of 1 second. Any other device can subscribe to this heartbeat status message to obtain status of the device.