Skip to content
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

Question about Bt.open #29

Closed
mrleavitt opened this issue Dec 25, 2012 · 2 comments
Closed

Question about Bt.open #29

mrleavitt opened this issue Dec 25, 2012 · 2 comments
Labels

Comments

@mrleavitt
Copy link
Collaborator

It seems like there is a missing section of the description of Bt.open (around p. 77). Using the parameter can determine whether to "listen for a secure or insecure connection. If no parameter is given or if the parameter is 1, then a secure connection request will be listened for. Otherwise, an insecure connection will be listened for."

What if the programmer wants the device to listen for any connection--secure or insecure? It would seem like that might be an option, after which the programmer might (but might not) wish to check for whether the connection that has been opened is secure or insecure. Of course there might be something in the underlying BT code that doesn't permit it, but in either case, it would seem useful to add a few sentences. If it can be done, how; if it can't be done, why.

@RFO-BASIC
Copy link
Owner

The Android API requires declaring a specific secure/insecure open and thus BASIC! must. I do not know why the Android OS requires this.

@mrleavitt
Copy link
Collaborator Author

OK. I added some words saying that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants