All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Claudio Takahasi <claudio.takahasi@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/2] Add Proximity Reporter API
Date: Wed, 18 Jan 2012 14:17:31 +0200	[thread overview]
Message-ID: <20120118121731.GC6655@x220> (raw)
In-Reply-To: <1326485995-707-1-git-send-email-claudio.takahasi@openbossa.org>

Hi Claudio,

On Fri, Jan 13, 2012, Claudio Takahasi wrote:
> +Proximity Reporter hierarchy
> +===========================
> +
> +Service used by Proximity Path Loss and Find Me. Allows per device
> +alert level handling.
> +
> +Service		org.bluez
> +Interface	org.bluez.ProximityReporter
> +Object path	[variable prefix]/{hci0,hci1,...}
> +
> +Methods
> +
> +
> +Signals		ImmediateAlertLevelChanged(object device, string value)
> +
> +			This signal indicates that Immediate Alert Level
> +			characteristic was changed by the remote device.
> +			Values: "none", "mild", "high".
> +
> +Properties

Shouldn't ImmediateAlertLevel and LinkLossAlertLevel be defined as
properties and then you'd have PropertyChanged instead of these custom
signals?

Johan

  reply	other threads:[~2012-01-18 12:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 21:04 [RFC BlueZ] Add Proximity Reporter interface - Proposal 1 Claudio Takahasi
2012-01-09 21:04 ` [RFC BlueZ] Add Proximity Reporter interface - Proposal 2 Claudio Takahasi
2012-01-13 20:19   ` [PATCH BlueZ 1/2] Add Proximity Reporter API Claudio Takahasi
2012-01-18 12:17     ` Johan Hedberg [this message]
2012-01-18 12:49       ` Anderson Lizardo
2012-01-19 18:21         ` Claudio Takahasi
2012-01-19 18:36           ` Claudio Takahasi
2012-01-23 11:00             ` Johan Hedberg

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=20120118121731.GC6655@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=claudio.takahasi@openbossa.org \
    --cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.