Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TCP and UDP Socket API #12

Open
olizilla opened this issue Apr 3, 2018 · 4 comments
Open

TCP and UDP Socket API #12

olizilla opened this issue Apr 3, 2018 · 4 comments
Labels

Comments

@olizilla
Copy link
Collaborator

olizilla commented Apr 3, 2018

  • What An API to provide interfaces to raw UDP sockets, TCP Client sockets and TCP Server sockets.
  • Why: To allow us to build out p2p protocols without having to work around the assumptions of HTTP or centralised authorities.
  • Workaround: Difficult. Provide support from an external app, and use connectNative api to share information with a WebExtension.
  • Status Needs a champion

    Members of this Working Group have agreed not to progress the TCP UDP Sockets API specification further as a Recommendation track document, electing instead to publish it as an informative Working Group Note under a permissive license with a view to enabling it to form the basis of further work by others, e.g. in a W3C Community Group.

    I think ideal steps would be:
    1. Create a new bug something like "WebExtensions API for client TCP sockets" (i.e., no UDP no server sockets)
    2. Make a proposal for how an extension uses this API and when and how users of such extensions are notified and grant permission (i.e., do they get a prompt when an extension is installed? Every time a socket is connected? Just the first time an extension connects to a specific address/port?)
    Once we have consensus on that, the implementation won't be completely trivial but it should be pretty straightforward.

@olizilla olizilla added the Topic label Apr 3, 2018
@lidel
Copy link
Member

lidel commented Apr 17, 2018

@olizilla
Copy link
Collaborator Author

@lgrahl
Copy link

lgrahl commented Dec 5, 2018

What is the goal here? Being able to access UDP/TCP APIs from within a page's JS or just as part of an extension?

@lidel
Copy link
Member

lidel commented Dec 6, 2018

A realistic goal would be to add it as a WebExtension API, like in libdweb experiments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants