MNC/MCC as string?
Denis Kenzior
denkenz at gmail.com
Wed Jun 10 10:41:59 PDT 2009
Hi Remi,
Well, the point is that leading zeroes are meaningful (much like with phone
> numbers in fact). The API, not just the implementation, must distinguish
> network "xy" from network "0xy", so that manual selection remains
> unambiguous.
> A D-Bus string is probably nicer to use than an integer using ISI's BCD
> scheme
I understand perfectly. But remember, oFono does not expose the user to
such details. Manual registration is accomplished by using Register()
method (with no arguments) of the NetworkOperator interface. The internal
storage representation is never exposed. Thus it doesn't matter whether
internally it is a string or short, etc.
The attributes are really only for informational purposes only. The user
would not base his decision on the mcc/mnc, but on the operator name.
So before we start changing the D-Bus APIs, we need to answer these two
questions:
- Can a country/administrative domain have both 001 and 01 MNCs such that
the use of string for the MNC is actually necessary.
- What does the user find easier to use, a string or a short?
Regards,
-Denis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ofono.org/pipermail/ofono/attachments/20090610/894f5689/attachment.html>
More information about the ofono
mailing list