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
While I would love if the only way the LIFX lights were changed was via lightsd and a single light-sd client, I know that around my house, there are others who will use the app to make changes. I can also see cases where there could be multiple lightsd clients all making changes.
This brings up the idea of being able to get change notification events from lightsd whenever a light changes. I'm guessing (!!!) internally this wouldn't be too difficult as it appears it's pretty good about tracking light changes in something close to real-time.
I think it would mostly come down to supporting something like "unsolicited" messages from the lightsd to open/existing clients (maybe after that client turns on event subscriptions, to allow for compatibility). Then clients can be notified fairly quickly when things change outside of the client itself.
Pie in the sky? ;-)
The text was updated successfully, but these errors were encountered:
This is totally part of the plan but I haven't prioritized it yet. I was thinking of writing a small JSON-RPC extension specification to implement that in a nice way since notifications from server to clients aren't part of the JSON-RPC standard.
There is a few things I'd like to do before that (add instrumentation, setup continuous integration, automate my release process, implement the new grouping API) but I'll think about it and prioritize according to what people are asking for!
Howdy,
While I would love if the only way the LIFX lights were changed was via lightsd and a single light-sd client, I know that around my house, there are others who will use the app to make changes. I can also see cases where there could be multiple lightsd clients all making changes.
This brings up the idea of being able to get change notification events from lightsd whenever a light changes. I'm guessing (!!!) internally this wouldn't be too difficult as it appears it's pretty good about tracking light changes in something close to real-time.
I think it would mostly come down to supporting something like "unsolicited" messages from the lightsd to open/existing clients (maybe after that client turns on event subscriptions, to allow for compatibility). Then clients can be notified fairly quickly when things change outside of the client itself.
Pie in the sky? ;-)
The text was updated successfully, but these errors were encountered: