public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Terry <michael.terry@canonical.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Wizard patch
Date: Mon, 30 Jun 2008 11:57:55 -0400	[thread overview]
Message-ID: <1214841475.6764.37.camel@bongo> (raw)
In-Reply-To: <1214834796.11537.42.camel@violet.holtmann.net>


[-- Attachment #1.1: Type: text/plain, Size: 1294 bytes --]

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

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 247 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

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

  reply	other threads:[~2008-06-30 15:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 19:05 [Bluez-devel] Wizard patch Michael Terry
2008-06-27 19:18 ` Michael Terry
2008-06-27 19:38 ` David Stockwell
2008-06-27 19:42   ` Michael Terry
2008-06-27 22:24     ` Marcel Holtmann
2008-06-27 22:23 ` Marcel Holtmann
2008-06-30 12:51   ` Michael Terry
2008-06-30 12:57     ` Marcel Holtmann
2008-06-30 13:20       ` Michael Terry
2008-06-30 14:07         ` Marcel Holtmann
2008-06-30 13:15   ` Michael Terry
2008-06-30 14:06     ` Marcel Holtmann
2008-06-30 15:57       ` Michael Terry [this message]
2008-06-30 16:03         ` Marcel Holtmann
2008-06-30 18:53           ` Michael Terry
2008-07-01  1:10             ` Marcel Holtmann
2008-07-09 14:28               ` Michael Terry
2008-08-19 17:33                 ` Michael Terry
2008-06-30 13:51   ` Michael Terry
2008-06-30 19:58     ` Michael Terry
2008-06-30 20:01       ` Michael Terry
2008-06-30 20:38         ` Bastien Nocera
2008-06-30 20:42         ` Mario Limonciello
2008-07-01  1:16     ` Marcel Holtmann
2008-06-30 15:48   ` Michael Terry
2008-07-01  1:24     ` Marcel Holtmann
2008-06-27 22:44 ` Bastien Nocera
     [not found]   ` <031301c8da4d$0bce3720$6701a8c0@freqonedev>
     [not found]     ` <1214813891.4435.149.camel@cookie.hadess.net>
2008-06-30 13:15       ` David Stockwell
2008-06-30 22:27         ` Luiz Augusto von Dentz
2008-07-01 18:56           ` David Stockwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1214841475.6764.37.camel@bongo \
    --to=michael.terry@canonical.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox