All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: "IPv6.Settings" in interface "org.ofono.ConnectionContext" is not a valid name
Date: Mon, 15 Dec 2014 23:12:33 -0600	[thread overview]
Message-ID: <548FBF41.3030806@gmail.com> (raw)
In-Reply-To: <CAJ-KqdzPe=-phOwH4Eh52jWRWmT-CLrL5OV9RTF_N3nFt8nAQw@mail.gmail.com>

[-- 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

  reply	other threads:[~2014-12-16  5:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  3:57 "IPv6.Settings" in interface "org.ofono.ConnectionContext" is not a valid name vicamo
2014-12-16  5:12 ` Denis Kenzior [this message]
2014-12-16  5:40   ` vicamo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=548FBF41.3030806@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.