All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Do we need to keep "aliased" interfaces?
Date: Thu, 29 May 2014 18:57:45 +0200	[thread overview]
Message-ID: <20140529165745.GA10882@siphos.be> (raw)

Hi all

We need a gnome_dbus_chat_gconfd interface, but if I were to follow the same
development pattern as for instance gnome_dbus_chat_gkeyringd then I would
need to create a gnome_dbus_chat_gconfd(<prefix>, <userdomain>) and a
gnome_dbus_chat_all_gconfd(<userdomain>) interface.

Now, the one with prefix support is to work on the *_gconfd_t types. These
are all aliases to gconfd_t, so there is no need to have different
interfaces.

Is it ok to just have a gnome_dbus_chat_gconfd(<userdomain>) method?

I really dislike the "all_gconfd" one as, in my opinion, it implies that
there are multiple gconfd domains "tied" together with some attribute, which
isn't the case.

Wkr,
	Sven Vermeulen

             reply	other threads:[~2014-05-29 16:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 16:57 Sven Vermeulen [this message]
2014-05-30 10:29 ` [refpolicy] Do we need to keep "aliased" interfaces? Dominick Grift
2014-05-30 10:48   ` Sven Vermeulen
2014-05-30 10:54     ` Dominick Grift
2014-06-02 15:12       ` Christopher J. PeBenito
2014-05-30 11:01     ` Dominick Grift

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=20140529165745.GA10882@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --cc=refpolicy@oss.tresys.com \
    /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.