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
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.