× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I guess your question is rhetorical because you probably know the answer - and yes it does kinda depend on your definition of "application". I don't really like the statement "node.js has a built in http server capability" even though I may have said it myself. This gives the noob reader the impression that every time they write a node.js function it is "http server" ready but of course it isn't. A node.js module is only capable of handling http requests if it "requires" the other modules it needs and is then coded to do so. It is only built-in because you don't have to have previously installed any extra packages using npm. It's a bit like saying that RPG has built in SQL capability - that doesn't mean that every RPG program you write uses SQL.

For my sins I completely rewrote the server side element of our Renaissance Framework in node.js and only one part of that deals with http requests from the client. You can plug in any number of applications and all they deal with is the handling of inbound and outbound data in JSON format. When a programmer develops a CRUD application/function for the customer master file, they only care about two things - the receipt and handling of the inbound JSON data and the creation and return of the outbound JSON data. The fact that this eventually gets delivered to an http client is of zero consequence. These functions/applications have no http server capability at all.

Sent from my iPad

On 16 Dec 2016, at 05:07, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Aaron and Kevin, it appears my question may have come across as facetious,
or perhaps even disrespectful. It was not intended that way. I understand
from a resource consumption perspective why you might not want to run a
Node instance per application, and an HTTP server per application. But
that's precisely the type of examples that one finds on the Internet - Node
instances which are handling perhaps a few to a dozen types of requests
(i.e. Express applications which handle perhaps a dozen "routes") which is
typical of a basic CRUD application.

In all seriousness, I can't be the only person who might be interested in
learning how Node might be used to handle hundreds of applications. My
definition of an application may be different than others. I tend to scope
"applications" to handle 3-12 types of requests.

On Thu, Dec 15, 2016 at 5:01 PM, Kevin Turner <
kevin.turner@xxxxxxxxxxxxxxxxxxxx> wrote:

But why would anyone do that unless they are a lunatic?

Sent from my iPad

[https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
On 15 Dec 2016, at 23:22, Nathan Andelin <nandelin@xxxxxxxxx> wrote:


I've wondering the same thing about apps implementing their own HTTP
service. It seems to me you'd have each app listening on its own
port. Is
that good?


Say you have 500+ CRUD applications for maintaining the 500+ tables in
your
DB. 500+ Node instances? 500+ TCP/IP ports allocated?
--
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,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.




________________________________
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.
--
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,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


--
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,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



________________________________
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-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 by midrange.com 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.