W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2010

RE: ACTION-16 for SystemInfo API

From: SULLIVAN, BRYAN L (ATTCINW) <BS3131@att.com>
Date: Mon, 1 Mar 2010 07:13:28 -0800
Message-ID: <8080D5B5C113E940BA8A461A91BFFFCD10E09EB2@BD01MSXMB015.US.Cingular.Net>
To: "Max Froumentin" <maxfro@opera.com>
Cc: "Rotan Hanrahan" <rotan.hanrahan@mobileaware.com>, <public-device-apis@w3.org>, <public-uwa@w3.org>
MCC     = 3 digits // country code
MNC     = 2 digits // mobile network code

Thanks, 
Bryan Sullivan | AT&T
-----Original Message-----
From: Max Froumentin [mailto:maxfro@opera.com] 
Sent: Monday, March 01, 2010 6:45 AM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: Rotan Hanrahan; public-device-apis@w3.org; public-uwa@w3.org
Subject: Re: ACTION-16 for SystemInfo API

Hi Bryan,

On 01/03/2010 12:27, SULLIVAN, BRYAN L (ATTCINW) wrote:

> But if the same information can be derived from MCC and MNC (which
> presumably it can), then I agree a Boolean will suffice for roaming.
> But we need to be sure that the MCC/MNC (home and visiting) are
> things that the application can determine through the SysInfo API.

Is it safe to assume that both MCC and MNC are unsigned shorts?

Max
Received on Monday, 1 March 2010 15:14:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:06 GMT