native-messaging-c VS native-messaging-cpp

Ultimately what I am trying to do is test the simplicity and efficiency of using a local server versus using Native Messaging, which I have working https://github.com/guest271314/native-messaging-c, https://github.com/guest271314/captureSystemAudio/blob/master/native_messaging/capture_system_audio/capture_system_audio.c.

Yes. I use Native Messaging to do that as well https://github.com/guest271314/native-messaging-c. Far less overhead cf. HTTP. Nonetheless I am trying to improve the implementation.

I would suggest sending valid JSON. Here is a Native Messaging host written in C which sends JSON to the client https://github.com/guest271314/native-messaging-c.

I will probably adjust the variable names in your code and publish here https://github.com/guest271314/native-messaging-c including link to your answer.

For the C version which is now just an echo of input https://github.com/guest271314/native-messaging-c/tree/main repeat steps 1.-6. Instead of pinning the icon to address bar, navigate back to chrome://extensions, click "service worker" which will open a DevTools window for the background MV3 ServiceWorker context, then run this code in the console

Working C++ version: https://github.com/guest271314/native-messaging-cpp/blob/main/nm_cpp.cpp

C++ Native Messaging host https://github.com/guest271314/native-messaging-cpp does not have that problem.

Technically you can launch and control the Qt and C++ (and any other programming language) applications from the browser, pass input as stdin and get stdout from the native application using various means, including Native Messaging https://github.com/guest271314/native-messaging-cpp.