W3C home > Mailing lists > Public > public-sysapps@w3.org > May 2013

Re: [sysapps/raw socket api]:Proposal for resolution of remaining issues.

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 7 May 2013 09:45:18 -0700
Message-ID: <CA+c2ei_-PUPkvn4uFGufkD+DK8dBqe=dsm2jDovgk6PL1VVWeg@mail.gmail.com>
To: "Nilsson, Claes1" <Claes1.Nilsson@sonymobile.com>
Cc: "public-sysapps@w3.org" <public-sysapps@w3.org>, "Isberg, Anders" <Anders.Isberg@sonymobile.com>, "Edenbrandt, Anders" <Anders.Edenbrandt@sonymobile.com>, Isaksson, Björn <Bjorn.Isaksson@sonymobile.com>
On Tue, May 7, 2013 at 8:08 AM, Nilsson, Claes1 <
Claes1.Nilsson@sonymobile.com> wrote:

> **
>
> https://github.com/sysapps/raw-sockets/issues/11: Devices have more than
> one network interface. However, the issue is whether web applications
> should be able to select a specific local network interface to use for a
> socket or if always the “default interface”/the configured interface should
> be used. My view is that we should provide this possibility by an optional
> field in the constructor’s options attribute. I must admit that I have
> difficulties in motivating this by tangible use cases but I haven’t seen
> any existing TCP or UDP socket API that  does not provide the possibility
> to bind a socket to a local address. So there must be use cases and I
> propose that we keep this possibility in the specification. Objections?
>

I definitely think we need use cases for all features of the spec. The fact
that all existing libraries support an outgoing IP number might be an
effect of that they are commonly used on servers rather than just clients.

/ Jonas
Received on Tuesday, 7 May 2013 16:46:20 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 1 July 2021 16:04:42 UTC