From e638a22341c9d3255ea600b37450a4d944106c88 Mon Sep 17 00:00:00 2001 From: Johan Hedberg Date: Fri, 29 Sep 2006 17:25:56 +0000 Subject: Remove RFCOMM.Connected and Disconnected signals since their proper implementation would require some extra bookeeping and events from the kernel --- hcid/dbus-api.txt | 16 ---------------- 1 file changed, 16 deletions(-) (limited to 'hcid/dbus-api.txt') diff --git a/hcid/dbus-api.txt b/hcid/dbus-api.txt index 8ee02218..3687000f 100644 --- a/hcid/dbus-api.txt +++ b/hcid/dbus-api.txt @@ -1023,22 +1023,6 @@ Methods string Connect(string address, string service) array{string} ListBindings() -Signals void Connected(string address, byte channel, string service) - - This signal will be issued once a RFCOMM connection - has been established through Connect or ConnectByChannel - and the service will be translated into a profile if - it is known. Otherwise the UUID will be listed. If - no UUID or service name is available it will be an - empty string. - - void Disconnected(string address, byte channel, string service) - - This signal will be issued if a RFCOMM connection - gets terminated through Disconnect or of the caller - application disconnects from the D-Bus. - - SDP hierarchy (experimental) ============================ -- cgit