Icebreak comes in 2 versions - one that only runs with the Apache server & one
that comes with the Icebreak HTTP server.
The difference in the 2 versions is the maintenance cost, with the Apache
version being a lower cost.
Jim T
----- Original Message ----
From: Nathan Andelin <nandelin@xxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Wed, January 5, 2011 12:26:28 PM
Subject: Re: [WEB400] Summing up the Icebreak discussion
From: Kevin Turner
IceBreak does not use Apache as a front-end - I am not sure
where that assertion comes from.
The assertion came from Niels. My understanding is that he's the author. See the
following quotes:
12-30-2010 "Actually, we also use Apache to "frontend" icebreak apps, just for
the reason that apache have some cool rewrite and reroute features...."
1-4-2011 "And the fact that IceBreak is the ILE servlet container also
underlines the misunderstanding of the title of this Thread: "IceBreak as an
alternative to Apache" - Well is Tomcat an alternative to Apache? no - not
really. Typically you use Apache and tomcat very closely together. We also use
Apache and IceBreak closely together."
I am using Icebreak with Renaissance (and therefore all the underlying
CGIDEV2 procedures) without any Apache server in the equation at all.
What makes you think that? I haven't tried Icebreak myself. So I'm just going
on Niels' comments. Well, maybe I wonder if anyone in their right mind would
write their own HTTP server given that Apache runs everywhere. But that's just a
subconscious thought ;-)
-Nathan.
midrange.com
