Perversely for quite some time we used a little node.js application (using node-http-proxy) to act as a reverse proxy to Apache running on the IBMi - effectively allowing each of us to develop and test our UI locally while still executing server code on the IBMi. It works well and the app was tiny - but of course it is equally simple to create a local instance of Apache (XAMPP) and configure that as a reverse proxy too.
[
https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Aaron Bartell
Sent: 15 December 2016 18:27
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] Using Node w/ Apache
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?
It can be used to great advantage, and messes can also be created. Let me give my perspective: Imagine if an Apache configuration used RPG syntax to define the various settings and routing rules. In short, it would require one less syntax to learn and keep up to speed with, and also one less piece of software in your stack to keep up to date; when a new release of RPG came out then so did a new version of the web server.
Also note that a single Node.js web server could front many Node.js apps; essentially playing the same role as Apache. The cool thing about this approach is you could have the Node.js web server implement core tenants of app infrastructure (i.e. authentication) so the other Node.js apps didn't have to.
I am not poo-pooing Apache/Nginx because I still use them and like them.
I am just loving how simple web servers are in Node.js. One thing I
haven't tried is putting a Node.js web server in front of other web servers (i.e. Ruby's Puma).
[10 minutes later] Ok, so I went looking and found this:
https://github.com/nodejitsu/node-http-proxy So it's definitely possible.
Aaron Bartell
IBM i hosting, starting at $157/month. litmis.com/spaces
On Thu, Dec 15, 2016 at 12:11 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
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?
-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Wednesday, December 14, 2016 11:31 PM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] Using Node w/ Apache
What is not to like about the HTTP server capabilities in node?
I find it very cool that applications can implement their own HTTP
server
- that Node makes that trivial. On the other hand, I question the
wisdom of every application implementing its own HTTP service.
--
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.
midrange.com
