public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@nokia.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Achim Bohnet <ach@mpe.mpg.de>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] D-BUS fixes for hcid
Date: Thu, 17 Jun 2004 12:48:02 +0300	[thread overview]
Message-ID: <20040617094802.GA4566@kone> (raw)
In-Reply-To: <1087399222.4309.26.camel@pegasus>

Hi Marcel,

On Thu, Jun 17, 2004, Marcel Holtmann wrote:
> > It would be nice to know how the D-BUS designers have thought about
> > this kinds of problems.
> 
> feel free to come up with a solution for this.

Unfortunately I don't have one. Would it still be possible to add the
dbus_message_set_auto_activation function call to the code? This will
not change the behaviour in any way if the service is already aquired
(i.e. bluez-pin is running), but will allow more flexibility if someone
decides that they want to use D-BUS activation (for example in an
embeded system where you only have one display and don't want to have
unecessary processes taking up memory all the time).

Johan

  reply	other threads:[~2004-06-17  9:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 11:27 [Bluez-devel] D-BUS fixes for hcid Johan Hedberg
2004-06-16 11:37 ` Marcel Holtmann
2004-06-16 11:57   ` Johan Hedberg
2004-06-16 12:05     ` Johan Hedberg
2004-06-16 12:18     ` Marcel Holtmann
2004-06-16 12:45       ` Johan Hedberg
2004-06-16 13:06         ` Marcel Holtmann
2004-06-16 13:46           ` Johan Hedberg
2004-06-16 13:53             ` Marcel Holtmann
2004-06-16 13:58           ` Achim Bohnet
2004-06-16 14:18             ` Johan Hedberg
2004-06-16 23:06               ` Marcel Holtmann
2004-06-17  9:48                 ` Johan Hedberg [this message]
2004-06-17 12:05                   ` Marcel Holtmann
2004-06-17  7:27               ` Sjoerd Simons
2004-06-18  7:30                 ` Achim Bohnet

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=20040617094802.GA4566@kone \
    --to=johan.hedberg@nokia.com \
    --cc=ach@mpe.mpg.de \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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