owt-sdk-quic
C++ server and client APIs for WebTransport. (by open-webrtc-toolkit)
owt-sdk-quic | proposal-common-minimum-api | |
---|---|---|
1 | 7 | |
116 | 206 | |
0.9% | 3.4% | |
2.3 | 4.7 | |
12 months ago | 30 days ago | |
C++ | Bikeshed | |
Apache License 2.0 | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
owt-sdk-quic
Posts with mentions or reviews of owt-sdk-quic.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-08.
-
All all Web API interfaces actually JavaScript objects?
WebTransport in C++ https://github.com/open-webrtc-toolkit/owt-sdk-quic.
proposal-common-minimum-api
Posts with mentions or reviews of proposal-common-minimum-api.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-10.
-
Can you make your own JavaScript by implementing ECMAScript standard?
If you are considering building a modern JavaScript runtime I would suggest reading Minimum Common API.
-
All all Web API interfaces actually JavaScript objects?
Deno, CloudFlare Workerd, VM Labs WASM Worker Server, and others use some semblance of the ServiceWorker onfetch pattern as a server implementation. Why? Because onfetch of a ServiceWorker with Response() used to send a response to the client is ergonomic. Web API's being implemented by JavaScript runtimes that do not target the browser. In order to try to normalize implementation of Web API's for compatibility there is https://github.com/wintercg/proposal-common-minimum-api.
-
Simple requirement: Bundle dependencies into a single script. esbuild, webpack, bun build throw errors. Solution?
I guess you do not support Minimum Common API even though Node.js does?
-
JavaScript Standard Input/Output: Unspecified
Common I/O (stdin/stdout/stderr) module specification #47.
-
Node.js fetch() vs. Deno fetch(): Implementation details...
My goal for one part of this project was to use the same fetch() code in a Node.js and Deno Native Messaging host, respectively, in the spirit of Minimum Common API
-
how to improve nodejs startup times
The premise of this question is precisely why I filed Single HTTPS server for QuickJS, Bun, Deno, Node.js - without reliance on either to build #33. Closed as
What are some alternatives?
When comparing owt-sdk-quic and proposal-common-minimum-api you can also consider the following projects:
native-messaging-bun - Bun Native Messaging host
native-messaging-quickjs - QuickJS Native Messaging host
AudioWorkletStream - fetch() => ReadableStream => AudioWorklet
native-messaging-nodejs - Node.js Native Messaging host
fetch - Fetch Standard
webbundle-plugins - A Webpack plugin for generating Web Bundles output.
node - Node.js JavaScript runtime ✨🐢🚀✨
native-messaging-deno - Deno Native Messaging Host
vite - Next generation frontend tooling. It's fast!
console - Console Standard
captureSystemAudio - Capture system audio ("What-U-Hear")
native-messaging - Native Messaging Host Protocol for Browser Extensions
proposal-common-minimum-api vs native-messaging-bun
proposal-common-minimum-api vs native-messaging-quickjs
proposal-common-minimum-api vs AudioWorkletStream
proposal-common-minimum-api vs native-messaging-nodejs
proposal-common-minimum-api vs fetch
proposal-common-minimum-api vs webbundle-plugins
proposal-common-minimum-api vs node
proposal-common-minimum-api vs native-messaging-deno
proposal-common-minimum-api vs vite
proposal-common-minimum-api vs console
proposal-common-minimum-api vs captureSystemAudio
proposal-common-minimum-api vs native-messaging