Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-63920

QNetwork for webassembly

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: P2: Important
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 5.12
    • Component/s: Network
    • Labels:
      None

      Description

      Applications running on the web platform are sandboxed, and this applies to network connectivity as well. Many standard protocols such as DNS and TCP sockets are not directly available (but see below):

      We are looking at several options:

      1) Use QNetworkAccessManager to make requests back to the origin server. This maps to the native XMLHttpRequest or Fetch APIs. Status: Pending for 5.12

      2) Use QWebSocket to make WebSocket connections to any host. Connecting by host name works; the browser will resolve the hostname. Status: merged for 5.12

      3) Use QTcpSocket to make a TCP connection to a forwarding server that runs e.g. websockify. This tunnels TCP traffic over WebSocket, which again means that connecting by hostname is OK. Status: under dev/testing, emscripten claims to have support.

      Future Tech 4) Look at WebRTC for peer-to-peer communication. We could possibly tunnel TCP connections to other application instances.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              lpotter Lorn Potter
              Reporter:
              lpotter Lorn Potter
            • Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

              • Created:
                Updated:

                Gerrit Reviews

                There are no open Gerrit changes