Nathan of Guardian: > > > On Mon, Feb 2, 2015, at 05:09 AM, Hans-Christoph Steiner wrote: >> >> Sounds intriguing. If you want to do the wifi service discovery on < >> android-16, there is jmdns. We had problems with the Android service >> discovery stuff when we added it to FDroid. It would randomly hang and >> things >> like that. jmdns seemed more reliable, but perhaps the Android SD stuff >> is >> somehow integrated into WiFi-Direct in a way that jmdns is not. > > I think this all works without being on a WiFi LAN of any kind. It is > similar to the code I have in Gilga.
WiFi-Direct just automatically sets up a WiFi then IP connection, with a link-local IP address. As far as I understand, it does not even introduce any new concepts to WiFi itself, it just is an automatic configuration of WiFi based on "Wi-Fi Protected Setup". For example, there needs to be only one device acting as the AP, that part is auto-negotiated. The non-AP devices just connect to it like a standard WiFi AP. The Android Service Discovery API uses mDNS for at least some of the discovery process, I don't know how its integrated with Bluetooth. .hc > >> >> .hc >> >> Michael Rogers: >>> Hi all, >>> >>> A few months ago I mentioned an idea for making peer-to-peer >>> connections between Android devices without user interaction. I've >>> finally had a chance to try it out, and it works - devices that >>> support wifi direct service discovery (API 16 and later) can discover >>> each other and connect via Bluetooth or ordinary wifi without user >>> interaction. >>> >>> The next step is to connect via wifi direct, which has higher >>> bandwidth than Bluetooth. One possible approach is to create a legacy >>> mode AP and advertise the SSID and password via service discovery; >>> another is to find out the device's self-assigned IP address and >>> advertise it in the same way as an ordinary wifi IP address. >>> >>> Code is here: >>> https://code.briarproject.org/akwizgran/peer-discovery >>> >>> Cheers, >>> Michael >>> _______________________________________________ >>> Guardian-dev mailing list >>> >>> Post: [email protected] >>> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev >>> >>> To Unsubscribe >>> Send email to: [email protected] >>> Or visit: >>> https://lists.mayfirst.org/mailman/options/guardian-dev/hans%40guardianproject.info >>> >>> You are subscribed as: [email protected] >>> >> >> -- >> PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81 >> https://pgp.mit.edu/pks/lookup?op=vindex&search=0x9F0FE587374BBE81 >> >> _______________________________________________ >> Guardian-dev mailing list >> >> Post: [email protected] >> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev >> >> To Unsubscribe >> Send email to: [email protected] >> Or visit: >> >> https://lists.mayfirst.org/mailman/options/guardian-dev/nathan%40guardianproject.info >> >> You are subscribed as: [email protected] >> Email had 1 attachment: >> + signature.asc >> 1k (application/pgp-signature) > > -- PGP fingerprint: 5E61 C878 0F86 295C E17D 8677 9F0F E587 374B BE81 https://pgp.mit.edu/pks/lookup?op=vindex&search=0x9F0FE587374BBE81 _______________________________________________ Guardian-dev mailing list Post: [email protected] List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev To Unsubscribe Send email to: [email protected] Or visit: https://lists.mayfirst.org/mailman/options/guardian-dev/archive%40mail-archive.com You are subscribed as: [email protected]
