Bear in mind that there is no requirement for an application running in a separate process to be using http. There are more efficient ways for it to communicate with an http front end.

[] ƕ
On 16 Dec 2016, at 18:11, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

​Some good commentary on how to organize larger Node projects: ​

Thanks for your reply, Aaron. However, my question was in regards to having
a separate Node process for each "application". The Stack Overflow
discussion (in contrast) offered tips about organizing code within a single
Node process.

I'm interested in hearing the pros and cons of running multiple Node
processes (i.e. one per application) vs. having a single Node process which
may organize the code by dispatching individual requests to various
in-process modules (JavaScript files).

If each application were a separate Node process, a reverse proxy might be
used to route browser requests to individual Node processes (i.e. may be routed to a Node process which is listening on port
9001 while may be routed to a Node process which is
listening on port 9002, etc.).
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.