All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jukka Rissanen <jukka.rissanen@linux.intel.com>
To: ell@lists.01.org
Subject: Re: [PATCH v2 2/3] dbus: Add disconnect watch support
Date: Mon, 16 Feb 2015 12:22:03 +0200	[thread overview]
Message-ID: <1424082123.4196.40.camel@linux.intel.com> (raw)
In-Reply-To: <54DE12BD.7000403@gmail.com>

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

On pe, 2015-02-13 at 09:05 -0600, Denis Kenzior wrote:
> Hi Jukka,
> 
> On 02/13/2015 08:23 AM, Jukka Rissanen wrote:
> > On pe, 2015-02-13 at 08:01 -0600, Denis Kenzior wrote:
> >> Hi Jukka,
> >>
> >> <snip>
> >>
> >>   >>> +struct filter_data {
> >>>>> +	struct l_dbus *dbus;
> >>>>> +	l_dbus_message_func_t handle_func;
> >>>>> +	l_dbus_watch_func_t connect_func;
> >>>>> +	l_dbus_watch_func_t disconnect_func;
> >>>>> +	char *name;
> >>>>> +	char *owner;
> >>>>
> >>>> What is the exact difference between name and owner?  I don't see a
> >>>> distinction...
> >>>
> >>> name is something like "org.foobar" and owner is ":1.101"
> >>>
> >>> User registers watch using a name and dbus-daemon sends its
> >>> notifications about NameOwnerChanged signals using the owner format so
> >>> we need to track both formats.
> >>
> >> Yes, but you don't actually handle that anywhere.  So I don't see a
> >> distinction in the current code.  If this is TBD, then simply don't
> >> include this and mention somewhere that only unique bus names are supported.
> >
> > Hmm, owner and name are handled differently in the code. For example see
> > the format_rule() function.
> >
> 
> Then help me understand.  You have:
> 
> in format_rule you have:
> +       offset = snprintf(rule, size, "type='signal'");
> +       sender = data->name ? : data->owner;
> +
> +       if (sender)
> +               offset += snprintf(rule + offset, size - offset,
> +                               ",sender='%s'", sender);
> 
> in filter_data_get you have:
> +       if (sender) {
> +               if (sender[0] == ':')
> +                       owner = sender;
> +               else
> +                       name = sender;
> +       }
> 
> So why not replace everything by simply sender?  Right now none of this 
> makes sense to me since you're not traking the well-known-name -> unique 
> name mapping.
> 
> If you only support unique names, just say so and make the code reflect 
> that.  Don't try to sneak code in that is part of some future 
> functionality.  I'm not a mind reader.

The owner/name distinction is indeed needed only for watching dbus
connects, and as we do not implement the connect support yet I will
remove this code.


Jukka



  reply	other threads:[~2015-02-16 10:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12 11:48 [PATCH v2 0/3] Add DBus disconnect watch support Jukka Rissanen
2015-02-12 11:48 ` [PATCH v2 1/3] dbus: Add AddMatch and RemoveMatch support Jukka Rissanen
2015-02-13  3:00   ` Denis Kenzior
2015-02-12 11:48 ` [PATCH v2 2/3] dbus: Add disconnect watch support Jukka Rissanen
2015-02-13  3:25   ` Denis Kenzior
2015-02-13  8:26     ` Jukka Rissanen
2015-02-13 14:01       ` Denis Kenzior
2015-02-13 14:23         ` Jukka Rissanen
2015-02-13 15:05           ` Denis Kenzior
2015-02-16 10:22             ` Jukka Rissanen [this message]
2015-02-12 11:48 ` [PATCH v2 3/3] unit: dbus: Add test for disconnect watch API Jukka Rissanen
2015-02-13  3:36   ` Denis Kenzior
2015-02-13  8:40     ` Jukka Rissanen
2015-02-13 14:10       ` Denis Kenzior
2015-02-13 14:29         ` Jukka Rissanen
2015-02-13 15:09           ` Denis Kenzior
2015-02-16 10:53             ` Jukka Rissanen
2015-02-16 15:58               ` Denis Kenzior

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=1424082123.4196.40.camel@linux.intel.com \
    --to=jukka.rissanen@linux.intel.com \
    --cc=ell@lists.01.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.