[RFC] should we ignore unknown key in match rule?

[Yang Chengwei]

Hi List,

I just found that the *new* dbus-monitor can't run with the *old"
dbus-daemon. The error output like below:

Error: Unknown key "eavesdrop" in match rule

This is cause by "eavesdrop" is newly added to dbus to fix an issue:
https://bugs.freedesktop.org/show_bug.cgi?id=37890

So it introduced a compatibility issue.

Meanwhile, as D-Bus specification suggests for message header parse like
below.

{quote}
Again, if an implementation sees a header field code that it does not
expect, it must ignore that field, as it will be part of a new (but
compatible) version of this specification. This also applies to known
header fields appearing in unexpected messages, for example: if a signal
has a reply serial it must be ignored even though it has no meaning as
of this version of the spec. 
{/quote}

So I think it's applicable to the match rule, say: ignore unknown keys
in match rule.

This should avoid this kind of compatibility issue occurs again in
future if any new key introduced.

Any comment?

--
Thanks,
Chengwei
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.freedesktop.org/archives/dbus/attachments/20130624/df3b2115/attachment.pgp>