On Mon, Mar 9, 2015 at 6:21 PM, Andrew Sutherland <[email protected]> wrote: > On Mon, Mar 9, 2015, at 08:23 PM, Jonas Sicking wrote: >> One interesting question to ask here is, would we be interested in >> adopting Tizen's API for, for example, SD card access? Or Chrome-app's >> API for TCPSocket? > > Apologies if you mean these generically without wanting specific > discussion.
I actually chose that one intentionally, since I know there's a standardization effort. So thanks for starting this thread. > But if it's helpful, I think TCPSocket is an interesting > real situation to discuss in this scope because besides it being a > dangerous API, there is: > > 1) A standardization effort is being made at > http://www.w3.org/2012/sysapps/tcp-udp-sockets/ (with issues tracked > under the github project at https://github.com/sysapps/tcp-udp-sockets). > I've been under the impression we intend to convert our implementation > to this spec. I've certainly been providing feedback to the spec from > experiences developing our email app. Has Google given any indication that they are actually planning on implementing the "standard"? Note that a standard is not a standard because someone wrote a document with a W3C logo on it. It's not even a standard if Google, Mozilla and other companies worked on that document together (which was the case here). It's a standard once there are multiple interoperable implementations. So, has Google given any indication that they are going to implement the API in that document and make it available to Chrome Apps or Chrome extensions? If not, we'd just change one FirefoxOS specific API for another. Which could still be worth it if the new API is sufficiently superior. / Jonas _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
