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
Bond's local API supports triggering scanning on demand for OOK signals as well as transmitting arbitrary data over OOK or (I think) GFSK.
I'm looking to build out support for these in the library and already got started on a PR, but before I submit it, I could use some feedback on different contracts:
Options:
Just separate async functions for begin scan, check current scan status, and get scan result data (this is the most flexible, but most annoying to use and wrap)
1 function for "scan for signals (optional frequency specification), and async keep polling for the scan to complete, and then surface the resulting data" (this is easiest to use with a single call to gather signal data)
Hybrid approach: Separate functions for each endpoint/behavior, but create a helper/utility function that wraps them up into a single async call.
Any of these options would also include a dedicated endpoint for the transmit signal endpoint.
Any preferences on these 3 options?
The text was updated successfully, but these errors were encountered:
Bond's local API supports triggering scanning on demand for OOK signals as well as transmitting arbitrary data over OOK or (I think) GFSK.
I'm looking to build out support for these in the library and already got started on a PR, but before I submit it, I could use some feedback on different contracts:
Options:
Any of these options would also include a dedicated endpoint for the transmit signal endpoint.
Any preferences on these 3 options?
The text was updated successfully, but these errors were encountered: