| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
noexcept, include 'em in DirectBT.hpp
|
|
|
|
| |
or name to allow empty EUI48Sub for all devices
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
basic use cases
Universal methods use a 'matcher' interface (Java) or function pointer (C++),
which can be defined 'on the fly' using lambda expressions.
Basic use cases BTDeviceRegistry:
- use 'contains' in general to match for awaited, processed etc devices
Basic use cases BTDeviceRegistry:
- For getOrCreate() uses 'equals' for a 100% match
- For sec_level use getStartOf() with actual address and name
- For PASSKEY etc use getStartOf() with actual addess only - no fuzzy name
|
|
|
|
| |
(C++ and Java)
|
|
|
|
| |
Java)
|
|
|
|
|
|
|
| |
devicesInProcessing and devicesProcessed for O(1) processing.
Add hash_code()/hashCode() and equality operation to DeviceID using BDAddressAndType only,
allowing devicesInProcessing and devicesProcessed to be mostly operated within O(1).
|
|
to lib, support full EUI84Sub and name-sub pattern matching
Same naming-schema and functionality C++/Java
Due to using EUI48Sub and name-sub pattern matching,
we naturally had to drop the hash-set fast-lookup approach.
However, looking up device names via pattern-matching is essential
to handle device groups, i.e.
- specific security settings (level, passkey, ..)
- actually accepting them to connect (waitForDevices)
|