webhoster VS native-messaging-deno

It's way simpler than it sounds. This is a < 100 line implementation, server-side.

I had written my own in-house framework to fully support HTTP2 and performance is slightly better than Koa.

I have an extremely similar setup, but not 100% to spec because I wrote a HTTP server in node and it has some expectations of being used for HTTP requests. But most of Response is built into the API, with expectation that you would interface with an HTTP request in the same fashion as a service worker. The public version is out of date, but the internal version I have used has the stream consumers. I use it for HTTP2 Push setup.

You can use a Native Messaging host to run local code controlled from the browser. See native-messaging-deno for a general purpose and extensible solution and deno-server where Deno's serveTls is dynamically started to run a local application, stream stdout from the application to the browser, then stop the local server.

I'm basically trying to do this https://github.com/guest271314/native-messaging-deno/blob/local-server-dynamic/local_server.js without the issue with deno executable increasing CPU to over 90% when streaming, and without carrying around the rest of Deno that I will not be using. Building deno requires using Rust toolchain which is over 1GB to install before we even begin building anything, which is non-trivial to do.

https://github.com/guest271314/native-messaging-deno/tree/local-server-dynamic.

Python https://github.com/guest271314/native-messaging-python, Deno https://github.com/guest271314/native-messaging-deno, Bun https://github.com/guest271314/native-messaging-bun, Node.js https://github.com/guest271314/native-messaging-nodejsNative Messaging hosts

I'll check in a few minutes. This is the source code I use that shows N GB "VSZ" https://github.com/guest271314/native-messaging-deno and the server I will be using https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/deno_server.js.