- From: Jonas Sicking <jonas@sicking.cc>
- Date: Sun, 28 Apr 2013 20:17:14 -0700
- To: Alexandre Morgaut <Alexandre.Morgaut@4d.com>
- Cc: Claes1 Nilsson <Claes1.Nilsson@sonymobile.com>, Ke-Fong Lin <ke-fong.lin@4d.com>, Ekberg, Björn <Bjorn.Ekberg@sonymobile.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>, "Edenbrandt, Anders" <Anders.Edenbrandt@sonymobile.com>, "Isberg, Anders" <Anders.Isberg@sonymobile.com>, "Falk, Mattias" <Mattias.Falk@sonymobile.com>
On Sun, Apr 28, 2013 at 7:22 AM, Alexandre Morgaut <Alexandre.Morgaut@4d.com> wrote: > >>>>> 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. >>> >>> Yup. So the question is what's the use case for, on a client side >>> device, setting up a socket connection specifically from wifi, 3G or >>> Bluetooth rather than the "default" connection? > > On client-side, the API won't be used only on mobiles. > As far as I know sysapps also target packaged apps for desktop applications which can run on computers with several IP addresses including physical ones and virtual ones (in Virtual Machine contexts) The app platform is definitely targetted at desktop applications and mobile alike. I agree. However this still doesn't really answer the question. When do you in a client side app, for mobile or desktop, need to create a connection on a particular interface or IP address? / Jonas
Received on Monday, 29 April 2013 03:18:16 UTC