From: Mikel Astiz <mikel.astiz@bmw-carit.de>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC obexd 05/10] client-doc: replace parameter dict with conventional ones
Date: Fri, 25 Nov 2011 14:41:35 +0100 [thread overview]
Message-ID: <4ECF9B0F.7040907@bmw-carit.de> (raw)
In-Reply-To: <CABBYNZ+T_j_4340NXefxH833tr-zdiy446yJnFDp58SoqDLnZw@mail.gmail.com>
Hi Luiz, Vinicius,
> IMO it is better to leave as it is because then some parameters can be
> omitted such as adapter and target, and it also easier to extend if we
> need other parameters e.g. WHO header without breaking the signature.
This might be a matter of personal preference, but IMO using a
dictionary to make an API more flexible is just hiding the problem. I
don't see why this method has more reasons than any other method to use
a dictionary instead of well-defined formal parameters.
If the point is that some of the input parameters are optional, I would
rather propose using empty strings. Again, it's a matter of personal taste.
Besides, I don't understand how the target could be omitted. Could you
further elaborate on this?
Cheers,
Mikel
next prev parent reply other threads:[~2011-11-25 13:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 14:08 [RFC obexd 00/10] Major API changes in obex-client Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 01/10] client-doc: reformatted to fit in 80 columns Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 02/10] client-doc: copyright statement added Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 03/10] client-doc: minor formatting changes Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 04/10] client-doc: wrap OPP into specific session type Mikel Astiz
2011-11-24 14:08 ` [RFC obexd 05/10] client-doc: replace parameter dict with conventional ones Mikel Astiz
2011-11-24 18:24 ` Vinicius Costa Gomes
2011-11-25 11:52 ` Luiz Augusto von Dentz
2011-11-25 13:41 ` Mikel Astiz [this message]
2011-11-24 14:08 ` [RFC obexd 06/10] client-doc: remove agent in favour of transfer signals Mikel Astiz
2011-11-25 12:01 ` Luiz Augusto von Dentz
2011-11-24 14:08 ` [RFC obexd 07/10] client-doc: ObjectPush sessions return transports Mikel Astiz
2011-11-24 14:09 ` [RFC obexd 08/10] client-doc: FileTransfer " Mikel Astiz
2011-11-24 14:09 ` [RFC obexd 09/10] client-doc: PhonebookAccess " Mikel Astiz
2011-11-24 14:09 ` [RFC obexd 10/10] client-doc: Synchronization " Mikel Astiz
2011-11-24 18:11 ` [RFC obexd 00/10] Major API changes in obex-client Vinicius Costa Gomes
2012-01-13 14:24 ` Luiz Augusto von Dentz
2012-01-13 15:53 ` Mikel Astiz
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=4ECF9B0F.7040907@bmw-carit.de \
--to=mikel.astiz@bmw-carit.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=vinicius.gomes@openbossa.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).