webtransport

WebTransport is a web API for flexible data transport (by w3c)

Webtransport Alternatives

Similar projects and alternatives to webtransport

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better webtransport alternative or higher similarity.

webtransport reviews and mentions

Posts with mentions or reviews of webtransport. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-16.
  • WebGPU – All of the cores, none of the canvas
    7 projects | news.ycombinator.com | 16 Jul 2023
  • Firefox 114 released
    2 projects | /r/linux | 6 Jun 2023
    WebTransport is now enabled by default and will be going to release with 114. As the original Explainer notes, it enables multiple use-cases that are hard or impossible to handle without it, especially for Gaming and live streaming. It covers cases that are problematic for alternative mechanisms, such as WebSockets. Built on top of HTTP3 (HTTP2 support will be coming later). The current implementation in Firefox is passing 505 out of 565 Web-Platform Tests.
  • Alternatives to WebSockets for realtime features
    1 project | dev.to | 6 Jan 2023
    WebTransport is still an emerging technology. As of November 2022, WebTransport is a draft specification with W3C, and there’s always a chance that aspects related to how it works may change.
  • Librespeed - a Foss speedtest
    2 projects | /r/linux | 25 Oct 2022
    Sort of. The browser will re-use the connection if you have a bunch of resources in the HTML. When rendering it sees that it needs 2 images and 3 javascript files from the same server, so it pipelines all of those. But for requests initiated from javascript, you're going to get a new connection for each one unless you're using a library that implements the long-polling hack. SocketIO can use the long-polling hack as a fallback if websockets is not supported. HTTP/2 (formerly SPDY) gets part of the way to replacing websockets, but it's not a synchronous link. Only the client can send messages to the server and the server can only respond to those message (with websockets, either side can send messages once the connection is open). FWIW, less than 50% of websites use HTTP/2. HTTP/3's webtransport looks like it could replace websockets, but it also looks like it'll live along side websockets.
  • The WebSocket Handbook
    14 projects | news.ycombinator.com | 11 Jan 2022
    If it's streaming data like dashboard statistics the new WebTransport API might be a much better base: https://github.com/w3c/webtransport/blob/main/explainer.md
  • We Got to LiveView
    19 projects | news.ycombinator.com | 22 Sep 2021
    Are you guys looking into the Web Transport protocol for the future? Right now you have to tunnel the websocket connections over http2 and it will probably be the same for http3 afaik.

    I know there is this work in progress (https://w3c.github.io/webtransport/) and websockets are probably fine for a long time but sooner or later (unless there is an update to websockets) it will probably be faster to just do normal http requests and listen on server sent events.

    What are your thoughts for Liveview for the future? Will it forever stay on websockets or would you be open to change the underlying technology if / when new stuff becomes available?

  • WebTransport is a proposed API to expose QUIC's datagrams and streams to JavaScript clients
    1 project | /r/programming | 5 Jul 2021
    The W3C draft is here: https://github.com/w3c/webtransport
  • The History and Future of Socket-level Multiplexing
    3 projects | dev.to | 6 May 2021
    It's taken nearly 10 years for QUIC to be refined and adopted in the wild and we're basically there. There's even a new browser API in the works called WebTransport.
  • Show HN: PSX Party – Online Multiplayer Playstation 1 Emulator Using WebRTC
    6 projects | news.ycombinator.com | 30 Dec 2020
    tl;dr using WebRTC just for realtime client<->server data sucks, but WebTransport[1] is coming soon to serve that exact usecase with an easy API

    WebRTC has data channels, which are currently the only way to achieve unreliable and unordered real-time communication (UDP-style) between the browser and other browsers or a server. This is pretty essential for any networked application where latency is critical, like voice and video and fast-paced multiplayer games.

    As other commenters have noted, it's a royal pain in the ass to set up WebRTC if all you want is UDP-style communication between a server and browser, since you need to wrangle half a dozen other protocols in the process.

    However! A new API, WebTransport[1], is actively being developed that will offer a WebSockets-like (read: super simple to set up) API for UDP-style communication. I am extremely excited about it and its potential for real-time browser-based multiplayer games (which I'm working on).

    https://github.com/w3c/webtransport

  • A note from our sponsor - SaaSHub
    www.saashub.com | 19 Apr 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic webtransport repo stats
11
800
9.1
4 days ago
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com