Can/has this been compiled to WASM to handle frame reading/writing?

[guest271314]

Can/has this been compiled to WASM to handle frame reading/writing?

[uNetworkingAB]

Very strange question but yes you can compile WebSocketProtocol.h into WASM if you feel like it. It has no benefit.

[uasan]

@guest271314 As far as I know, TCPServerSocket is supported only in the Chrome browser, so I ask what is the use case of the websocket server in Chrome?

[guest271314]

To use the server... For various purposes, just like any other server or technology. What's the use case of WebSockets now that there's QUIC over HTTP/3? See where that type of question leads?

Re

is supported only in the Chrome browser,

Chromium Project source code is the source for Chromium browser, Chrome, Chrome For Testing, Brave, Microsoft Edge, Opera.

So when you say "Chrome" you are saying at least 6 browsers; over 60% of market share, easily.

• Because the runtime agnostic JavaScript WebSocket server has not been done, yet, and is there to do
• To facilitate streaming to and from local and/or remote applications; for testing and other novel usages
• To substitute WHATWG Streams for JSON over IPC that Native Messaging implementation uses
• Standard usages such as TTS and STT given no browser is currently shipped with a built in speech synthesis or speech recognition implementation
• Et al.

[guest271314]

@USAN My current implementation cobbles together different parts of different gists, and doesn't really process over 65536 message length to/from server/client consistently. I'm close, not there, yet.

I'm trying to use somebody's frame parsing work, rewrite to runtime agnostic JavaScript so the same code can be run in the browser, using node, deno, bun, and even qjs, tjs, and other JavaScript engines and runtimes.

My question here is the source code modularized sufficiently enough to extract just the frame parsing and accumulation and writing parts so I can port your code to JavaScript in a runtime agnostic way?

[uNetworkingAB]

https://github.com/uNetworking/uWebSockets/blame/master/src/WebSocketProtocol.h

[guest271314]

Hmm

./llvm-project/build/bin/clang WebSocketProtocol.h -target wasm32 -o WebSocketProtocol.wasm
WebSocketProtocol.h:21:10: fatal error: 'cstdint' file not found
   21 | #include <cstdint>
      |          ^~~~~~~~~
1 error generated.

[uNetworkingAB]

This error is for you to figure out. Of course I know what is wrong but you need to figure it out otherwise this endeavour is a dead end.

[guest271314]

Fair enough.

[guest271314]

emsdk$ ./upstream/bin/clang++ $HOME/bin/WebSocketProtocol.h 
clang++: warning: treating 'c-header' input as 'c++-header' when in C++ mode, this behavior is deprecated [-Wdeprecated]
/home/user/bin/WebSocketProtocol.h:401:29: error: use of undeclared identifier 'LIBUS_RECV_BUFFER_LENGTH'
  401 |         for (int i = 0; i < LIBUS_RECV_BUFFER_LENGTH; i += 16) {
      |                             ^
/home/user/bin/WebSocketProtocol.h:433:39: error: use of undeclared identifier 'LIBUS_RECV_BUFFER_LENGTH'
  433 |                     if /*constexpr*/ (LIBUS_RECV_BUFFER_LENGTH == length) {
      |                                       ^
2 errors generated.

[guest271314]

@uNetworkingAB I found some code originally written for Node.js that I could work with and modified that code to a JavaScript runtime agnostic WebSocket server https://gist.github.com/guest271314/d330c7cea513f12ef7bf523c56431453.