Besides the options pointed out, it would also be possible to use the Node-Webkit
embarking the Node.js + Chrome engine.
Runs as a normal program, but looks like a Browser, limited only to the application you want to show.
This way you can control both the javascript client and the C++ backend and package everything as one application. The only limitation is that your user would have to install the executable, but if that’s not a problem, I believe it is the option that gives you the most flexibility with the least possible headache, compared to Nacl(Learning overhead) or Emscripten(Runtime overhead)
I think the way is through Nacl (Google Native Client). Although I’ve never used it, I’ve only heard of it, they say it’s possible to run native code on the client yes. I hope someone who used it can say something about it.
– Wakim
Are you talking about something like QT or are you even considering calling a C++ program from a javascript site? ( I guarantee that most browsers will not authorize this second option).
– Mansueli
@Wakim,
Google Native Client
does not run on the customer side as requested in the question.– Mansueli
@Kyllopardiun, are you sure? Check out the description: https://developer.chrome.com/native-client.
– Wakim
If you see the tutorial will see that it generates a microservice for this and so I would not classify it as on the client side.
– Mansueli
Native Client is just for running native code on the client, directly in the browser. It is probably the solution in this case, although it is limited to Chrome. I’m not going to write an answer because I’ve never used it, I hope someone will turn up already. @Kyllopardiun The tutorial server is only for sending the page and binary code to the client, it does not execute anything.
– Guilherme Bernal