webserver-c VS native-messaging-espeak-ng

This is one example webserver-c, more examples rsenn/qjs-modules.

Right now I am working on a single-page source code C server that I compile to a shared library and import into QuickJS https://github.com/guest271314/webserver-c/tree/quickjs-webserver.

Not sure. This is the original code https://github.com/guest271314/webserver-c that uses getsockname().

Sure. https://github.com/guest271314/webserver-c/tree/quickjs-webserver, https://plnkr.co/edit/bK1BfoSgjFUDwkIV?preview, https://plnkr.co/plunk/qX5tepJ38BuDOSZj.

Because I am writing a Web server module for QuickJS https://github.com/guest271314/webserver-c/blob/quickjs-webserver/webserver.c. One use case is sending a command to a local server and streaming the stdout to the browser. I know the text will not be chunked because I am making the request.

I use the source code for Deno's serveTls https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/local_server.js and wrote a Web server module for QuickJS https://github.com/guest271314/webserver-c/tree/quickjs-webserver.

You can just send the data directly to the server, local server (that you can start and stop from the browser https://github.com/guest271314/webserver-c/tree/quickjs-webserver) or remote from the terminal or browser.

I finally cobbled together the C source code and QuickJS module heavily relying on existing C source code QuickJS module https://github.com/guest271314/webserver-c/tree/quickjs-webserver.

I'm just trying to use coqui-ai/TTS so I can stream speech synthesis output to the browser as I do with eSpeak NG https://github.com/guest271314/native-messaging-espeak-ng. I think the issue has been brought up before on GitHub. I have not read a solution. I am ready to try again if you can suggest a minimal build process.

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.

A single page Deno server can be found here https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/local_server.js. I have used this source code // https://github.com/chcunningham/atomics-post-message/blob/main/server.js, renamed to server.msj modified to use Ecmascript Modules instead of CommonJS, e.g.,

I've already achieved the requirement multiple ways, already; from using Native Messaging https://github.com/guest271314/native-messaging-espeak-ng, to using GNU Core Utilities tail, to Deno.watchFs() https://github.com/guest271314/fs, et al., see captureSystemAudio. The one approach I have not yet achieved is compiling to Emscripten - with SSML support.

Create a self-signed certificate. If you are on Chromium or Chrome launch with --ignore-certificate-errors-spki-list=.... Read this https://github.com/GoogleChrome/samples/blob/gh-pages/webtransport/webtransport_server.py#L42-L72. This is how I use HTTPS for Deno and Node local servers and WebTransport https://github.com/guest271314/native-messaging-espeak-ng/tree/deno-server.

I use the source code for Deno's serveTls https://github.com/guest271314/native-messaging-espeak-ng/blob/deno-server/local_server.js and wrote a Web server module for QuickJS https://github.com/guest271314/webserver-c/tree/quickjs-webserver.

This https://github.com/guest271314/native-messaging-espeak-ng/tree/deno-server is what I do using Deno

I created https://github.com/guest271314/native-messaging-espeak-ng which provides a means to send text or SSML to the eSpeak NG speech synthesis engine and parse the generated WAV in the browser. That bypasses waiting around another N years for Google to prioritize Web Speech API, which I see no evidence of Google doing - except for its cloud service.

I merely read the article to see how the author was implementing "Text-to-Speech"; how they implemented "Text-to-Speech"; e.g., native-messaging-espeak-ng to overcome or avoid the multiple issues and limitations with using the specified Web Speech API in the browser.