Dave Platt feff2af5c0 NsdService does not clean up after exiting clients ...

When a client of the NsdService exits, NsdService should
clean up the requests it has sent to the mDNS daemon:
cancel any pending resource-discovery and resource-resolution
queries, and remove any services registered by this client.

If this isn't done, several bad things happen. The daemon will
continue to run unnecessarily, will report service discoveries
that can't be forwarded on to the client, and will continue to
advertise service ports for an application which is no longer
running until the device is rebooted (mDNS pollution).

Bug: 9801184
Change-Id: I0aa7311480322aefcff16f902fbbf34f50985d38

2014-03-13 23:16:30 +00:00

core

Harden NsdManager against null-dereference crashes

2014-03-04 13:25:02 -08:00

services

NsdService does not clean up after exiting clients

2014-03-13 23:16:30 +00:00

wifi/java/android/net/wifi/p2p

Add support for setMiracastMode

2013-03-28 10:27:17 -07:00

Description

android_packages_modules_Connectivity

189 MiB

Languages

Java 81.4%

Kotlin 7.7%

AIDL 4.5%

C++ 4.5%

C 1.7%

Other 0.1%