"IPv6.Settings" in interface "org.ofono.ConnectionContext" is not a valid name

"IPv6.Settings" in interface "org.ofono.ConnectionContext" is not a valid name

[vicamo]

[-- Attachment #1: Type: text/plain, Size: 462 bytes --]

Hi all,

I happen to find a strange property "IPv6.Settings" in ConnectionContext.
According to DBus specification [1], dbus member names can only be
consisted of character set "[A-Z][a-z][0-9]_" and may not begin with a
digit. Any plan to get rid of it? Or is a patch to this welcomed? It will
certainly break compatibility to existing programs.

[1]:
http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names

Regards,
Vicamo

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 657 bytes --]

Re: "IPv6.Settings" in interface "org.ofono.ConnectionContext" is not a valid name

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]

Hi,

On 12/15/2014 09:57 PM, vicamo(a)gmail.com wrote:
> Hi all,
>
> I happen to find a strange property "IPv6.Settings" in
> ConnectionContext. According to DBus specification [1], dbus member
> names can only be consisted of character set "[A-Z][a-z][0-9]_" and may
> not begin with a digit. Any plan to get rid of it? Or is a patch to this
> welcomed? It will certainly break compatibility to existing programs.
>
> [1]:
> http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names
>

Properties are not member names, so the restrictions you mention do not 
apply.  See the DBus Specification:

"Strictly speaking, D-Bus property names are not required to follow the 
same naming restrictions as member names, but D-Bus property names that 
would not be valid member names (in particular, GObject-style 
dash-separated property names) can cause interoperability problems and 
should be avoided. "

Since the oFono DBus API is currently frozen, there are no plans on 
"fixing" this particular property.

Regards,
-Denis

Re: "IPv6.Settings" in interface "org.ofono.ConnectionContext" is not a valid name

[vicamo]

[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]

Hi,

Thank you for the quick correction. I did find this problem when trying to
generate interface binding code by gdbus-codegen from gio. It generates
functions with a period character in their names which are certainly not
valid c function names.

Vicamo


2014-12-16 13:12 GMT+08:00 Denis Kenzior <denkenz@gmail.com>:
>
> Hi,
>
>
> On 12/15/2014 09:57 PM, vicamo(a)gmail.com wrote:
>
>> Hi all,
>>
>> I happen to find a strange property "IPv6.Settings" in
>> ConnectionContext. According to DBus specification [1], dbus member
>> names can only be consisted of character set "[A-Z][a-z][0-9]_" and may
>> not begin with a digit. Any plan to get rid of it? Or is a patch to this
>> welcomed? It will certainly break compatibility to existing programs.
>>
>> [1]:
>> http://dbus.freedesktop.org/doc/dbus-specification.html#
>> message-protocol-names
>>
>>
> Properties are not member names, so the restrictions you mention do not
> apply.  See the DBus Specification:
>
> "Strictly speaking, D-Bus property names are not required to follow the
> same naming restrictions as member names, but D-Bus property names that
> would not be valid member names (in particular, GObject-style
> dash-separated property names) can cause interoperability problems and
> should be avoided. "
>
> Since the oFono DBus API is currently frozen, there are no plans on
> "fixing" this particular property.
>
> Regards,
> -Denis
>

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 2143 bytes --]