Documentation question

[abusalaa7]

If I understand it correctly, the NodeJsProcessOptions configures the singleton service that communicates with the out of process node service via http. Is that correct? The name "NodeJsProcessOptions" implies that this is an alternative way to spawning an out of process node instance by running an in-process one. Which I'm assuming is not correct? This library doesn't have a way of running node in process?

[JeremyTCD]

OutOfProcessNodeJSServiceOptions configures the service. NodeJsProcessOptions configures Node.js processes.

Anyway you're right, this library doesn't provide a way to run Node.js in process. The reason for the naming scheme is that we intend to provide an in-process alternative if/when Node.js gets an official embedding API.

There is a library, Edge.js, that allows you to run Node.js in process. It's a valiant attempt, unfortunately we had issues with it:

• It's stuck on an old Node.js release because it uses customized Node.js binaries.
• It limits you to one Node.js instance (not safe to host several in a process). Coupled with the dated Node.js binaries, options for concurrency are limited.
• Only supports .NET Framework for invoking in Node.js from C#.

If those aren't issues for you, do consider it.

Thanks for bringing this up, will add a note in the documentation.

[abusalaa7]

Thanks for clarifying.