|
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@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
As an Amazon Associate we earn from qualifying purchases.
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.