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
In Bluetooth Low Energy there is the concept of central and peripheral, whereas peripheral generally advertises and the central connects to it.
After connecting, the concepts transition to client and server, whereas the central typically becomes the client and the peripheral the server.
Currently in Kable, you create a Peripheral in order to connect to the remote peripheral, but this is somewhat nebulous as the object represents the remote. So, you're technically the central connecting to the peripheral — the Peripheral class does not make this clear. Especially considering the Peripheral has a connect function but it is really the central that is "connecting" to the remote Peripheral.
Even further confusion will likely be introduced if/when #51 is tackled.
It may make more sense to lean into the client/server nomenclature? Especially considering those are fairly well known concepts in internet related stacks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In Bluetooth Low Energy there is the concept of central and peripheral, whereas peripheral generally advertises and the central connects to it.
After connecting, the concepts transition to client and server, whereas the central typically becomes the client and the peripheral the server.
Currently in Kable, you create a
Peripheral
in order to connect to the remote peripheral, but this is somewhat nebulous as the object represents the remote. So, you're technically the central connecting to the peripheral — thePeripheral
class does not make this clear. Especially considering thePeripheral
has aconnect
function but it is really the central that is "connecting" to the remotePeripheral
.Even further confusion will likely be introduced if/when #51 is tackled.
It may make more sense to lean into the client/server nomenclature? Especially considering those are fairly well known concepts in internet related stacks.
0 votes ·
Beta Was this translation helpful? Give feedback.
All reactions