Re: [PATCH] Notify to device drivers when the SDP records change

["José Antonio Santos Cadenas" <santoscadenas@gmail.com>]

Hi, 

El Tuesday 03 August 2010 13:42:15 Luiz Augusto von Dentz escribió:
> Hi,
> 
> On Tue, Aug 3, 2010 at 12:12 PM, José Antonio Santos Cadenas
> 
> <santoscadenas@gmail.com> wrote:
> > The different with a2dp is that the application will decide the end point
> > to connect to, because there can be more than one matching the source.
> > This end point is represented by a path that is passed to the
> > HealthAgent when is discovered. If the remote record changes it is
> > possible that new end points are available so the application needs
> > something to discover the available end points. That is why I think that
> > we need something like this.
> 
> I guess we already suggest you guys to take a look in the
> MediaEndpoint interface, which can be found here:
> 
> http://gitorious.org/~vudentz/bluez/vudentzs-clone/commit/2af3d2821f0aaafae
> 12be10522c82dea6a701688.patch
> 
> It doesn't expose the remote endpoints it basically do the best
> matching, if the application requesting the connection has local
> endpoint they have priority, and then the 'agent' or in case of audio
> the endpoint will be notified with the remote endpoint capabilities.
> 
> Also while looking the health API it seems you guys missed a very
> important point, HealthAgent only knows about the remote services
> since there is no signal for announcing a new HealthApplication nor
> the application knows the about HealthService, so the only way make
> this to work is that the HealthApplication and HealthAgent leaves in
> the same process but this defeats the point of having them separated.
> So either we have the applications and services being announced to
> everyone and then anyone can do the matching or we don't announce them
> at all and make bluetoothd do the matching itself, I guess the latter
> is better so we don't have to split the logic in many place (with
> potential code duplication + bugs).
> 
> Another important thing is that dbus introspection does not have any
> way to notify changes, so it really need to be signal to notify
> applications about new services.

Can we have an IRC session to talk about the API and continuing this 
discussion? I think that this thread is changing too much from its original 
topic.


Regards.