feat(interpose): route peripheral GATT server#10
Merged
Conversation
Swizzle CBPeripheralManager to route a guest's GATT-server calls (publish, advertise, respond, notify) to the host, and deliver the host's peripheral events as the guest's delegate callbacks. Adds the seven peripheral client-transport functions and the peripheral shadow objects.
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
2 participants
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.
Build the interposer side of the peripheral (GATT server) role, mirroring the central role. Swizzle
CBPeripheralManagerso a guest app's publish, advertise, respond, and notify calls route to the host, and deliver the host's peripheral events back as the guest's ownCBPeripheralManagerDelegatecallbacks on its queue. Adds the seven peripheral client-transport functions, the peripheral shadow objects (CBMutableService/CBMutableCharacteristictracking, shadowCBCentralandCBATTRequest), and extends the C tests. A non-managed CoreBluetooth user passes through untouched; the wire protocol and the fence are unchanged.