Skip to main content

[jsr360-observers] [jsr360-experts] Re: Accesspoint identification

  • From: roger riggs < >
  • To:
  • Subject: [jsr360-observers] [jsr360-experts] Re: Accesspoint identification
  • Date: Tue, 26 Nov 2013 11:29:28 -0500
  • List-id: <jsr360-experts.jsr360.java.net>
  • Organization: Oracle Corporation

Hi Thomas,

It was observed that APNs are operator specific and in many cases provisioned by the operators and may have names that if left unqualified would be ambiguous. Since the of() method needs to be able to select a unique AccessPoint it seemed that the name of the operator is required.

I'd be happy to be corrected to simplify the interface.

Thanks, Roger

On 11/26/2013 11:09 AM, Lampart Thomas wrote:

Dear specleads, experts,

today I stumbled over something in the AccessPoint class spec which confused me a bit.

To find or create a 3GPP AccessPoint usingAccessPoint.of <../../../javax/microedition/io/AccessPoint.html#of%28java.lang.String,%20javax.microedition.io.ConnectionOption...%29>the type is"3GPP"and the ConnectionOptions are:

  * apn - required, aConnectionOption<String>;apnsmany apns are
    predefined and provisioned by the network operator and additional
    APNs can be created as needed
  * apnoperator - required, the name of the operator providing the APN

What would this "apnoperator" as required parameter be ? What relevance would it have ?

To me this seems to be just some random text which does maybe not make sense when you CREATE an AccessPoint.

Wouldn't it make more sense here to have a "name" as required parameter here. A name which can be used to clearly identify the Accesspoint. THE name which can be queried with getName() method ?

Best regards

Thomas


------------------------------------------------------------------------
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus



[jsr360-observers] [jsr360-experts] JSR 360 EG call notes - Tuesday Nov 12th

Michael Lagally 11/12/2013

[jsr360-observers] [jsr360-experts] Re: JSR 360 EG call notes - Tuesday Nov 12th

Werner Keil 11/12/2013

[jsr360-observers] [jsr360-experts] JSR 360 EG call notes (revised) - Tuesday Nov 12th

Michael Lagally 11/12/2013

[jsr360-observers] [jsr360-experts] Accesspoint selection for Ping and DNS

Lampart Thomas 11/19/2013

[jsr360-observers] [jsr360-experts] Re: Accesspoint selection for Ping and DNS

Michael Lagally 11/19/2013

[jsr360-observers] [jsr360-experts] Re: Re: Accesspoint selection for Ping and DNS

Lampart Thomas 11/19/2013

[jsr360-observers] [jsr360-experts] Re: Re: Accesspoint selection for Ping and DNS

Michael Lagally 11/25/2013

[jsr360-observers] [jsr360-experts] Accesspoint identification

Lampart Thomas 11/26/2013

[jsr360-observers] [jsr360-experts] Re: Accesspoint identification

roger riggs 11/26/2013

[jsr360-observers] [jsr360-experts] Re: Accesspoint identification

Lampart Thomas 11/26/2013

[jsr360-observers] [jsr360-experts] Re: Accesspoint identification

roger riggs 11/26/2013

[jsr360-observers] [jsr360-experts] Re: Re: Accesspoint identification

Lampart Thomas 11/27/2013

[jsr360-observers] [jsr360-experts] Re: Re: Accesspoint identification

Werner Keil 11/27/2013

[jsr360-observers] [jsr360-experts] Re: Re: Accesspoint identification

roger riggs 11/27/2013

[jsr360-observers] [jsr360-experts] Re: Re: Re: Accesspoint identification

Lampart Thomas 11/27/2013

[jsr360-observers] [jsr360-experts] Re: Accesspoint selection for Ping and DNS

Michael Lagally 11/19/2013
 
 
Close
loading
Please Confirm
Close