From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC 2/19]: patch set to update the git reference policy
Date: Thu, 03 Feb 2011 22:43:32 +0100 [thread overview]
Message-ID: <1296769412.2942.5.camel@tesla.lan> (raw)
In-Reply-To: <20110203001820.80983f9echanzo8w@webmail.tuffmail.net>
Hello Martin !
On Thu, 03/02/2011 alle 00.18 +0000, Martin Orr wrote:
> On Mon 31 Jan 23:15:14 2011, Guido Trentalancia wrote:
> > The DBus send_msg issue is the probably the main change introduced by
> > the set of patches that I am proposing.
> >
> > The issue is very wide and needs careful approval. It's not limited to
> > this [2/19] patch/thread at all. It is mainly a style issue, but it's an
> > important one.
> >
> > In any case, [2/19] and [8/19] are perhaps the most relevant places
> > where you can provide a definite direction on this (in short, can we
> > really talk about an hypothetical DBus "chat" throughout all refpolicy
> > and model interfaces accordingly to such assumption when on the other
> > hand the elementary data-flow in DBus is constituted by a
> > uni-directional message called "signal" ?).
>
> I think that it is often better to think about "chats". Often one
> process A (e.g. consolekit or setroubleshoot) provides a service which
> many other processes B can use by sending a DBus message to A. A only
> sends messages to B after getting messages from B.
>
> In this case, I think it is likely to be more maintainable if each
> module B uses A_dbus_chat, instead of putting a big list of all the
> possible B into module A. I do not care strongly about it however.
Yes, it is possible to do it that way if the majority of people prefer
it like that.
Any other technical comment ? So far I have only applied some
improvements from Dominick Grift. If you think there is something else
to improve please let me know as I am waiting for further comments.
Thanks for your time !
Regards,
Guido
prev parent reply other threads:[~2011-02-03 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 0:43 [refpolicy] [PATCH/RFC 2/19]: patch set to update the git reference policy Guido Trentalancia
2011-01-24 14:24 ` Dominick Grift
2011-01-31 18:52 ` Christopher J. PeBenito
2011-01-31 23:15 ` Guido Trentalancia
[not found] ` <4D48132F.7070705@tresys.com>
2011-02-01 20:03 ` Guido Trentalancia
[not found] ` <4D48649C.70000@tresys.com>
2011-02-01 20:59 ` Guido Trentalancia
2011-02-03 0:18 ` Martin Orr
2011-02-03 21:43 ` Guido Trentalancia [this message]
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=1296769412.2942.5.camel@tesla.lan \
--to=guido@trentalancia.com \
--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.