[pulseaudio-discuss] [RFC v0 10/15] bluetooth: Parse media transport's properties

Tanu Kaskinen tanuk at iki.fi
Mon Jan 7 21:03:46 PST 2013

On Mon, 2013-01-07 at 16:37 +0100, Mikel Astiz wrote:
> Hi Tanu,
> On Mon, Dec 31, 2012 at 12:47 PM, Tanu Kaskinen <tanuk at iki.fi> wrote:
> >  * When parsing any optional property, never fail on parse errors, just
> > pretend that the property isn't set (when parsing the initial
> > properties) or that the property value didn't change (when parsing a
> > PropertiesChanged signal).
> If a parsing of a property fails, regardless of whether it's optional
> or not, it means BlueZ is misbehaving. I see no reason to be more
> relaxed with optional properties.

Yes, you're right.


More information about the pulseaudio-discuss mailing list