Re: Summing up the Icebreak discussion

Icebreak has it own implementation of HTTP - and Niels wrote it, and how do
I know that ?

Well, I have Icebreak running on my server, niels and I are less the 1 mile
from each other and we have
known each other in +20 years - and still agrees and disagrees - in a manner
of and like the melody:

"You say either and I say either, You say neither and I say neither
Either, either Neither, neither, Let's call the whole thing off.

You like potato and I like potahto, You like tomato and I like tomahto
Potato, potahto, Tomato, tomahto, Let's call the whole thing off"

During 2008 we started a project together, with Bent, Niels, I and another
initialled called PUPFISH. Later it became PORTFOLIO - and the goal was
to create a grapical UI based ERP system based on two systems - my financial

standard system (that has been the financial system in more than 100
installions
in DK out of 3000 AS/400) and the third party's commercial solution.

Late 2008 this project was abandoned due to lack of efficiency in the
methods of
modernization and Niels and Bent went forward with IceCap - a new screen
scaper -
and I went back to the drawingboard and comming up with the blueprint for
powerEXT
in early 2009 based on month of analysis before writing a single statement.

And we do integrate - no, I don't run powerEXT under Icebreak (even it is
prepared for it),
but I do run IceCap under powerEXT, what becomes at mixed environment of
statefull
5250 emulation and powerEXT stateless environment - in a single logon.

The most interesting part in IceCap vs. powerEXT is that IceCap provides a
fast solution
into RIA (by providing 5250 intelligent screen scaping) while powerEXT
brings you into at
resuable SOA solution for 95% of your programs - without any steap learning
curve - and
still delivers a RIA and SOA in most commen areas.



On Wed, Jan 5, 2011 at 7:28 PM, jim t <jim_t_59@xxxxxxxxx> wrote:

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.




--
This is the Web Enabling the AS400 / 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 AS400 / 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.