There does not seem to be any actual need for this method. The current implementation calls Cancel when a pending NewConnection() or RequestDisconnection() method call fails. Additionally it calls Cancel() when the remote client has disconnected. In either case BlueZ calls shutdown on the file descriptor associated with the agent and issues a Cancel() method call. The closing of the file descriptor will trigger a HUP on the agent side, which will trigger normal cleanup procedures. The received Cancel() method call is redundant in both cases. --- doc/profile-api.txt | 8 -------- 1 file changed, 8 deletions(-) diff --git a/doc/profile-api.txt b/doc/profile-api.txt index 96cfce9..ec18034 100644 --- a/doc/profile-api.txt +++ b/doc/profile-api.txt @@ -145,11 +145,3 @@ Methods void Release() [noreply] Possible errors: org.bluez.Error.Rejected org.bluez.Error.Canceled - - void Cancel() - - This method gets called to indicate that the profile - request failed before a reply was returned. - - All request are queued and there will be only one - pending pequest at a time per profile. -- 1.8.1.5 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
