Is there need for subscription based status updates from the device?

[TimEvWw]

No description provided.

[roryaronson]

What do you mean by subscription based? Would any of the following examples be considered subscription based? If not, what would be?

• Device sends update every day at 3pm and the web-app "subscribes" to these updates
• Device sends update with each completed command and the database subscribes to these updates to maintain synchronization
• Device sends update every time there is an error, the web app subscribes to this and sends an email to the user with each update

[TimEvWw]

When you connect with the site, you request the status from the bot to put
it on screen. Does the device has to send the same message every x seconds
so the site can display the latest status?? (moving now, next command
scheduled at ...)

On Fri, Jun 20, 2014 at 10:12 AM, Rory Aronson notifications@github.com
wrote:

What do you mean by subscription based? Would any of the following
examples be considered subscription based? If not, what would be?

• Device sends update every day at 3pm and the web-app "subscribes" to
  these updates
• Device sends update with each completed command and the database
  subscribes to these updates to maintain synchronization
• Device sends update every time there is an error, the web app
  subscribes to this and sends an email to the user with each update

—
Reply to this email directly or view it on GitHub
#13 (comment)
.

[RickCarlino]

I would like this feature. It would be nice to have for interacting with the UI layer.

[roryaronson]

I agree with Rick, it would be nice to see a console of everything happening on the device in near real time

[TimEvWw]

Now, what does the protocol looks like?

I was thinking for now of sending a message_type "read_status_subscription"
with parameter keep_alive = 15 minutes and period = 5 seconds. The status
message can be extended with a value subscription_timeout that is set to
true in the last minute so the site can send a new subscription to the bot.
This way the bot doesn't keep sending messages forever, only when it's
needed. There are probably better way but I can't think of them right now.

On Fri, Jun 20, 2014 at 8:08 PM, Rory Aronson notifications@github.com
wrote:

I agree with Rick, it would be nice to see a console of everything
happening on the device in near real time

—
Reply to this email directly or view it on GitHub
#13 (comment)
.

[RickCarlino]

I think this feature has been implemented. Closing this issue.