On Thu Mar 20 17:35:21 2025 +0000, Vibhav Pant wrote:
Ah. I've been relying on MSDN's Bluetooth specific [documentation for Winsock here](https://learn.microsoft.com/en-us/windows/win32/bluetooth/bluetooth-and-wsal...). According to that, `LUP_NOCONTAINERS` is entirely ignored (the docs explicitly say that any flags except for `LUP_CONTAINERS` and `LUP_FLUSHCACHE` are ignored for `NS_BTH`). If flags to `WSALookupServiceBegin` are supposed to act like filters, the Bluetooth-specific functionality for this method is completely different. Device and service discovery are mutually exclusive, and which one of the two is going to happen seems to be set in stone after the first `WSALookupServiceBegin` call, which is why I went for the unions. I've added to the `protocol.c` tests in the latest revision which demonstrate this behavior a little more clearly. As to `NS_ALL`, you're right, I'm not sure how this fits in with that. But given `NS_BTH`'s behavior, I'm not even sure if `NS_ALL` would include Bluetooth data in the first place.
Okay, that's fine then.