Thanx Aaron
Clustering might be an option – however i was hoping to get two birds with one shot – namely a java project as well which suffer from the same "one-process-no-fallback-desease".
So i was hoping that someone could point in a to a generic solution for multi process/job listening on the same socket port…
BTW - thanx for the node.js presentation you gave me. I beefed it up and gave people a full evening (four hour) tutorial – Some in the audience even survived…
Best regards
Niels Liisberg
Chief Software Architect
sitemule.com
System & Method A/S
Håndværkersvinget 8
DK-2970 Hørsholm
Phone: +45 70 20 30 10
Fax: +45 70 20 30 11
Direct: +45 45 166 135
Mobile: +45 31 158 861
E-mail: nli@xxxxxxxxxxxx<mailto:nli@xxxxxxxxxxxxxxxxx> or nli@xxxxxxxxxxxxxxxxx<mailto:nli@xxxxxxxxxxxxxxxxx>
Web:
www.sitemule.com
www.system-method.com
www.Icebreak.org
“Everything should be made as simple as possible, but not simpler.”
— Albert Einstein
From: Aaron Bartell <aaronbartell@xxxxxxxxx<mailto:aaronbartell@xxxxxxxxx>>
Reply-To: AS400 iSeries <web400@xxxxxxxxxxxx<mailto:web400@xxxxxxxxxxxx>>
Date: Thu, 15 Oct 2015 15:03:29 +0200
To: AS400 iSeries <web400@xxxxxxxxxxxx<mailto:web400@xxxxxxxxxxxx>>
Subject: Re: [WEB400] Hosting a Large Number of Node Apps on the IBM i
Glad to have you enter the conversation, Niels!
Have you checked out the clustering built into Node.js?
https://nodejs.org/api/cluster.html#cluster_how_it_works
I have not delved into it (yet). I don't know if this feature is available
in the IBM i version because Node.js just jumped from v0.12.x to v4.x.x
(still doesn't make sense to me :-| ).
Aaron Bartell
litmis.com - Services for open source on IBM i
On Thu, Oct 15, 2015 at 6:40 AM, Niels Liisberg <NLI@xxxxxxxxxxxxxxxxx<mailto:NLI@xxxxxxxxxxxxxxxxx>>
wrote:
Greetings,
Sorry for just jumping into the discussion rather late. However we have
the same issues here where we alternatively are using node.js as the
frontend for IceBreak ILE application server.
Node.js has ( as you all know) one disadvantage: the one ( single)
process listening/binding to the port.
I know you can do some trix with a "fork" so it shares the same socket or
you can set up a "reverse proxy" front-end. IMHO it its to many moving
parts…
What is was looking for, was a feature in the core of the IBMI that let me
share the the socket between jobs – not only forked process. But more the
data-queue style where each process/job can listen the the next incoming
"connect". This will eventually mean that i can submit any number of
node.js jobs listening on the same port.
It seams that windows has a similar (but not exactly) feature
WSADuplicateSocket i am looking for
BTW: This will also enable me to "upscale" java jobs where "fork" is not
an option
Thanx in advance…
Best regards
Niels Liisberg
Chief Software Architect
sitemule.com
System & Method A/S
Håndværkersvinget 8
DK-2970 Hørsholm
Phone: +45 70 20 30 10
Fax: +45 70 20 30 11
Direct: +45 45 166 135
Mobile: +45 31 158 861
E-mail: nli@xxxxxxxxxxxx<mailto:nli@xxxxxxxxxxxx><mailto:nli@xxxxxxxxxxxxxxxxx> or
nli@xxxxxxxxxxxxxxxxx<mailto:nli@xxxxxxxxxxxxxxxxx><mailto:nli@xxxxxxxxxxxxxxxxx>
Web:
www.sitemule.com
www.system-method.com
www.Icebreak.org
“Everything should be made as simple as possible, but not simpler.”
— Albert Einstein
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx<mailto:WEB400@xxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx<mailto:WEB400-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/web400.
midrange.com
