Re: [Bluez-devel] non persistent sdp records

Marcel Holtmann
2007-05-11T08:24:00Z

Hi Frederic,

> > actually using the standalone is a race condition. You should really
> > consider switching to hcid -s. It also saves you some memory footprint.
> >
> Well, I'm lazy, I would like not to rewrite code...

actually for this you don't have to rewrite anything. Simply use
--disable-sdpd and then then call hcid -s on startup. That gives you the
same SDP API as before. Except you have one daemon less to start and you
no longer have race-conditions between hcid and sdpd.

> >> We will probably consider dbus as is sounds much easier, but it is
> >> important to be able to do as much as what can be done through sdp api.
> >>
> > Why?
> >
> I wasn't clear, I meant having no regression in regards to what we
> actually use, doing exactly the same sdp records we have in pand, a2dpd, ...

Since pand and sdpd will be removed at some point (don't worry, they
will be around for quite some time), you might seriously consider the
D-Bus API.

Anyhow, I think you found a real bug and might wanna fix the persistent
versus non-persistent SDP record creation.