[jsr360-observers] [jsr360-experts] Re: NetworkInterface class
- From: Michael Lagally <
- To: "
- Subject: [jsr360-observers] [jsr360-experts] Re: NetworkInterface class
- Date: Fri, 8 Nov 2013 07:20:54 +0700
- List-id: <jsr360-experts.jsr360.java.net>
thanks very much for your feedback. Let's discuss in the next EG call.
Sent from my mobile.
> Am 07.11.2013 um 16:52 schrieb Lampart Thomas
> Dear specleads, experts,
> I did look a little bit closer at the new class “NetworkInterface” and
> would like to ask for some clarification how this class is supposed to work
> and how it is supposed to be used by a midlet.
> As the documentation states: “In most cases, applications will need to use
> only the AccessPoint API to select to connect and disconnect AccessPoints
> connections. The NetworkInterface APIs are needed in cases where more
> detailed management of connections is required.”
> What could this “detailed management” be ? The class does not offer any new
> (“exciting”) methods which give additional functionality to AccessPoint ?
> Or am I missing something ?
> Also the example seems a bit confusing to me, as it looks for “unused”
> NetworkInterfaces to connect an AccessPoint. Why does it need to be used ?
> Can you please give a real live example where it makes sense to have the
> NetworkInterface class.
> Best regards
> From: Michael Lagally
> Sent: Montag, 4. November 2013 11:09
> Subject: [jsr360-observers] [jsr360-experts] JSR360 EG call notes -
> Wednesday, Oct 30th
> Dear JSR 360 experts,
> Dear JSR360 EG members,
> Here are the notes from the last JSR 360 call on October 30th, 14:00-14:40
> Thomas Lampart, Gemalto
> Michael Lagally, Oracle
> Roger Riggs, Oracle
> Yiming Zhao, Nokia
> Call Notes:
> SpecLead Draft 4
> The SpecLead Draft 4 which was provided to the expert group last week
> bug fixes and clarifications that were added to the spec after the PR
> Roger and Michael walked through the changes one by one and explained
> the reasons for these updates.
> The list of changes was sent to the EG reflector last week and is included
> again for reference.
> The draft is very close to the PFD version, which will be provided in the
> next two weeks.
> EG members are encouraged to review the draft and the changes and provide
> about all issues to the spec leads before Nov 12th to allow for
> consideration in the PFD.
> Proposed Final Draft schedule
> We plan to submit the Proposed Final Draft on or before November 29th.
> A follow-up EG call is scheduled for Tuesday, Nov 12th, 2pm CET to discuss
> any potential issues
> as reported by the EG.
> The PFD version of the spec will be provided for final EG review shortly
> after that and we will
> seek EG approval for the PFD by November 27th.
> New EG member
> Yiming Zhao took over the EG representation for Nokia from Irvine Ye.
> Best regards,
> Michael + Roger
> 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