-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for events to accessory server #160
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nice one! |
One little addition:
It is no problem if |
This could do the trick:
What do you think? |
Looks good - i have applied that change to my branch with a tiny flake8 fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first step towards #51, but arguably not a complete solution. I have pulled it out of #154 so it can be reviewed in isolation. It doesn't have tests on its own (but there are tests that make use of this in #154).
If you have 2 active connections open to an accessory then a put_characteristic on connection 1 will now trigger events on connection but not its own connection (and vice versa).
This refactors the part of handle_one_request that writes a HTTP response to the wire out into its own function and ensures that only one task can write to the socket at once (otherwise there is a race when there are multiple tasks encrypting and writing to the network).
Then there is a write_event helper on the request handler that writes a single HTTP Event Response to the wire. There is a variant of this on the HTTPServer that can write an event to all active connections.
Right now events are only triggered from put_characteristic HTTP handlers. If you were writing an accessory with homekit_python you could manually call write_event on the HTTPServer when you are recording a change. To fully close #51 we should probably integrate a bit better than this, though.
To see it working I run a demoserver.py in on terminal, pair with it in another then do:
Then in a third terminal