- From: Nilsson, Claes1 <Claes1.Nilsson@sonymobile.com>
- Date: Wed, 24 Apr 2013 09:22:30 +0200
- To: 'Tomoyuki SHIMIZU' <tomoyuki.labs@gmail.com>, Laszlo Gombos <laszlo.gombos@gmail.com>, "public-sysapps@w3.org public-sysapps@w3.org" <public-sysapps@w3.org>
- CC: Ke-Fong Lin <ke-fong.lin@4d.com>, Jonas Sicking <jonas@sicking.cc>, "Edenbrandt, Anders" <Anders.Edenbrandt@sonymobile.com>, "Ekberg, Björn" <Bjorn.Ekberg@sonymobile.com>, "Falk, Mattias" <Mattias.Falk@sonymobile.com>, "Isberg, Anders" <Anders.Isberg@sonymobile.com>
Fine, thanks. Claes > -----Original Message----- > From: Tomoyuki SHIMIZU [mailto:tomoyuki.labs@gmail.com] > Sent: den 24 april 2013 03:03 > To: Laszlo Gombos; public-sysapps@w3.org public-sysapps@w3.org > Cc: Ke-Fong Lin; Jonas Sicking; Nilsson, Claes1; Edenbrandt, Anders; > Ekberg, Björn; Falk, Mattias; Isberg, Anders > Subject: Re: [sysapps/raw socket api]: New version based on Madrid > meeting comments and comments from Ke-Fong Lin > > Hi, > > > It seems to me that enumerating the local interfaces will be > provided by the Network Information API which is a planned as a Phase2 > items, so perhaps we should postpone this use-case for Phase2. > > +1. > I have added this in SysApps Wiki[1]. > > Best regards, > Tomoyuki > > [1] > http://www.w3.org/wiki/System_Applications_WG:_Network_Interface_API > > > On Apr 24, 2013, at 9:59 , Laszlo Gombos <laszlo.gombos@gmail.com> > wrote: > > > Hi, > > > > > > On Tue, Apr 23, 2013 at 3:41 PM, Ke-Fong Lin <ke-fong.lin@4d.com> > wrote: > > Hi Jonas, > > > > > It's still not clear to me how to use the localAddress/localPort > arguments for TCPSocket and UDPSocket. > > > What are the use cases for these options? > > > > Local address is needed to select which network interface to use. On > mobile device, that would be WIFI, 3G, Bluetooth. > > Local port is needed for multicast receiving mainly. With TCP, client > almost always use a random port selected by OS. > > > > >How will the app know what values to specify for those arguments? > Are you expecting that we'll have some additional spec that will > provide information about which local addresses are available and where > they are connected? > > > > Yes, we've avoided that question currently. No localAddress set, > means "default" network interface. > > A way to enumerate available interface(s) would be helpful. > > > > > > It seems to me that enumerating the local interfaces will be > provided by the Network Information API which is a planned as a Phase2 > items, so perhaps we should postpone this use-case for Phase2. > > > > Regards, > > Laszlo
Received on Wednesday, 24 April 2013 07:22:59 UTC