From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 5/5] cell-info: Documentation
Date: Tue, 28 Dec 2010 09:13:54 -0800 [thread overview]
Message-ID: <1293556434.9439.70.camel@aeonflux> (raw)
In-Reply-To: <1293542847-24248-6-git-send-email-antti.paila@nokia.com>
[-- Attachment #1: Type: text/plain, Size: 2423 bytes --]
Hi Antti,
> doc/cell-info.txt | 124 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 124 insertions(+), 0 deletions(-)
> create mode 100644 doc/cell-info.txt
>
> diff --git a/doc/cell-info.txt b/doc/cell-info.txt
> new file mode 100644
> index 0000000..b288e69
> --- /dev/null
> +++ b/doc/cell-info.txt
> @@ -0,0 +1,124 @@
> +Cell Info hierarchy
> +===================
> +
> +Service org.ofono
> +Interface org.ofono.CellInfo
> +Object path [variable prefix]/{modem0,modem1,...}
> +
> +Methods a{sv}aa{sv} GetNeighborCellInfo()
> +
> + Calling this procedure returns properties of serving
> + and neighbouring cells in GSM or WCDMA networks. This
> + information can be used to determine current location
> + using triangulation over neighbouring cell tower
> + locations and estimated distances.
> +
> + The return value consists of two parts: 1) dictionary
> + of common information about network and serving cell 2)
> + array of dictionaries containing measurement results
> + of neighbouring cells. The contents of the dictionaries
> + follow the specification OMA-TS-ULP-V2_0-20100816-C for
> + user plane Location and is described in properties
> + section.
> +
> + a{sv} GetProperties
> +
> + Calling this procedure returns properties of serving
> + cell in GSM or WCDMA networks. Effectively the data
> + returned is the part 1 of the data returned by
> + GetNeighborCellInfo.
why do we bother here with two methods calls. What is the use of getting
only half of the information. You are making the same call to the
hardware, so why not return the same information.
The method name org.ofono.CellInfo.GetNeighborCellInfo is also not
really good. I duplicates the CellInfo information. So I would just have
called this GetNeighbors.
What is the reason behind a{sv}aa{sv} here? Wouldn't it be simpler to
just go with aa{sv} and declare that the first dict is always the
current serving cell? Are the information from the current cell really
that different than from the neighbors?
One other think that I don't really like with the GetProperties part is
that we could expect a PropertiesChanged signal. However that is not
really going to happen since the query should only be done on demand. So
I would prefer if we then don't have properties at all in this case.
Regards
Marcel
next prev parent reply other threads:[~2010-12-28 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 13:27 [PATCH 0/5] Neighboring Cell Info Antti Paila
2010-12-28 13:27 ` [PATCH 1/5] cell-info: Header file for cell info atom Antti Paila
2010-12-30 9:33 ` Wei, Jun
2010-12-28 13:27 ` [PATCH 2/5] cell-info: Atom for ECID info of neighb cells Antti Paila
2010-12-28 13:27 ` [PATCH 3/5] cell-info: Interface declaration for cell info Antti Paila
2010-12-28 13:27 ` [PATCH 4/5] cell-info: New files included for compilation Antti Paila
2010-12-28 13:27 ` [PATCH 5/5] cell-info: Documentation Antti Paila
2010-12-28 17:13 ` Marcel Holtmann [this message]
2010-12-29 7:18 ` Antti Paila
2010-12-29 10:39 ` Aki Niemi
2011-01-03 20:42 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2011-02-14 14:56 [PATCH 0/5 v4] Neighbor Cell Info Atom Antti Paila
2011-02-14 14:56 ` [PATCH 5/5] cell-info: Documentation Antti Paila
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=1293556434.9439.70.camel@aeonflux \
--to=marcel@holtmann.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox