From: Michael Terry <michael.terry@canonical.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
In-Reply-To: <1214834796.11537.42.camel@violet.holtmann.net>
References: <1214593557.6131.26.camel@bongo>
	<1214605438.11537.0.camel@violet.holtmann.net>
	<1214831713.6764.8.camel@bongo>
	<1214834796.11537.42.camel@violet.holtmann.net>
Date: Mon, 30 Jun 2008 11:57:55 -0400
Message-Id: <1214841475.6764.37.camel@bongo>
Mime-Version: 1.0
Subject: Re: [Bluez-devel] Wizard patch
Reply-To: BlueZ development <bluez-devel@lists.sourceforge.net>
Content-Type: multipart/mixed; boundary="===============1208316225=="
Sender: bluez-devel-bounces@lists.sourceforge.net
Errors-To: bluez-devel-bounces@lists.sourceforge.net


--===============1208316225==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-4rSM8ZbX+8nb3NLdsZHJ"


--=-4rSM8ZbX+8nb3NLdsZHJ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2008-06-30 at 16:06 +0200, Marcel Holtmann wrote:
> > It also adds a new function: bluetooth_client_cancel_call().  This
> > cancels the last client call made for the given adapter/address.
[snip]
> it only makes sense for the create bonding call, because the others
> can't really be canceled. So my proposal is to leave the others out of
> this change and implement create_bonding and cancel_bonding.

Except that one of my other patches adds a new cancelable function
_connect().  So we would need maybe specific cancel_bonding and
cancel_connect functions.

But why can't the others be canceled?  Just on the assumption that the
DBus communication will be so fast as to not really allow time for
canceling?  Or that by the time you send the message, it's all said and
done anyway?  I don't understand the nitty gritty details of dbus async
communication.

I figured that as a matter of principle, if you have an async API like
this, it ought to allow for canceling because the very nature of async
suggests a period of time in which your program is doing other things,
one of which could conceivably trigger a cancel.

But I agree it's largely a moot case for something like _remove_trust().
I just figured it would be cleaner to do the set of them.

-mt

--=-4rSM8ZbX+8nb3NLdsZHJ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIaQKD53i2YxNrdi0RAlCgAJwJMm7BxJnSw7oDWa1UJldQjiuq4QCg182U
+hTlPFjMUhThKn355Op0N9s=
=91D7
-----END PGP SIGNATURE-----

--=-4rSM8ZbX+8nb3NLdsZHJ--


--===============1208316225==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
--===============1208316225==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

--===============1208316225==--