@__apf__ nice chrome dev summit talk. Will the chrome.sockets.tcp api from chrome apps come to the web as well?
-
-
Replying to @tankredhase
@tankredhase I'm not sure what the timeline/prioritization is for porting that api /cc@slightlylate1 reply 0 retweets 0 likes -
Replying to @__apf__
@__apf__@slightlylate that's what I suspected. The only use cases for sockets in chrome apps right now are email and IRC clients :/1 reply 0 retweets 0 likes -
Replying to @tankredhase
@tankredhase@__apf__ There's a W3C API draft in this are and it looks good. Permission model is the sticky wicket.1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@__apf__ permission could be granted after install to homescreen in app manifest. Our shim for W3C api https://github.com/whiteout-io/tcp-socket …1 reply 3 retweets 0 likes -
Replying to @tankredhase
@slightlylate@__apf__ I understand the permission is just as sensitive as bluetooth. Maybe after bluetooth is solved other apis will follow1 reply 0 retweets 0 likes -
Replying to @tankredhase
@tankredhase@__apf__ : it's perhaps even more sensitive -- it totally breaks the origin model. It's a Super Power (TM).1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@__apf__ yeah. That's why I fear tcp-sockets will always stay a privileged api for packaged apps and not make to the web :(2 replies 0 retweets 0 likes
@tankredhase @__apf__ : well, that it's privileged and only available on some sites isn't the same thing as not being available.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.