Back to search
I'm a firm believer that a maintainer should be, at least in some part, a consumer of the thing they're maintaining. I built GGK for a personal project. That project's communication needs have grown considerably, beyond the point where Bluetooth LE is a viable option and I was forced to make the switch to an IP-based solution. As much as I've enjoyed building and using GGK, I no longer have a use-case for Bluetooh LE or a test-case for GGK.
Stars
1.3k
Forks
442
Watchers
1.3k
Open Issues
0
Overall repository health assessment
No package.json found
This might not be a Node.js project
No contributors data available
Improved handling of connection counts dealing with latent disconnects on startup. This includes a change to change to the behavior of change notifications for values, they no longer check for an active connection before transmitting - this is now up to the caller.
e11f8abView on GitHubCleaned up the deinitialization process to avoid inadvertent calls to shutdown
4718fd0View on GitHubFixed a race condition while waiting for command responses from the HCI adapter
d93d906View on GitHubImproved threading support, cleaner initialization process and added the ability to wait for threaded responses from HCI commands.
5d3fe52View on GitHub