Add ANY_SERVER registration - #339
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
registerWorker()now will acceptANY_SERVERas a server ID.This is potentially dangerous, as it will catch all requests to server IDs that are not covered by explicitly defined workers!
Explicitly registered workers for combinations of a distinct server ID and a function code (also
ANY_FUNCTION_CODE) will have preference to the generic worker at all times.It may be needed for some devices in the wild, though, that are (mis)using the server ID for functional purposes.
Be warned again: using
ANY_SERVERmay break your server's function!ANY_SERVERstill is invalid for issueing requests or attaching server IDs to a bridge.