Return-Path: Subject: Re: [RFC] Health Thermometer Profile API Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Elvis Pfutzenreuter In-Reply-To: Date: Mon, 27 Jun 2011 12:09:31 -0300 Cc: mike tsai , linux-bluetooth@vger.kernel.org Message-Id: References: <1308661408-8364-1-git-send-email-sancane@gmail.com> <544C7016-5346-4C99-AEA9-C91AA84E3A42@signove.com> <75C285AD-9C2B-4F57-A998-D1346A68AEEE@signove.com> <092E3C75-499E-4E78-A167-F2DB57A0051E@signove.com> To: Santiago Carot Sender: linux-bluetooth-owner@vger.kernel.org List-ID: >> (cut) >> >> Thing is, you need to show each client app process a different 'view' of >> those D-Bus properties. It is feasible, but it is a new trick, not >> employed in other APIs. > > I think that it may work for Final and Intermediate but not for the > Interval property that is common for all agents. Besides, this > characteristic can be readed/writed through the D-Bus attribute API > too as Anderson said. Agreed. Interval is unsolvable; there is only one per device.