× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Bent,

so what you are saying is - that Icebreak is a complety
*proprietary*<http://www.google.com/search?hl=da&rls=com.microsoft:da:IE-SearchBox&&sa=X&ei=atAkTbbTCoi54ga685HoCQ&ved=0CBcQvwUoAQ&q=proprietary&spell=1>
product
only own by, developed and mantained by Niels ;-)

On Wed, Jan 5, 2011 at 9:05 PM, Bent RÃnne <BRO@xxxxxxxxxxxxxxxxx> wrote:

Gents

As part of the IceBreak development team with Niels, let me clarify a
couple of things.

IceBreak does not in any way use other server technologies. IceBreak is a
100% ILE native HTTP server - and that is it. No Apache! IceBreak was
developed by a team of OS/400 developers with broad backgrounds.

IceBreak has absolutely nothing to do with Apache, CGI2DEV, Tomcat - or
anything else for that matter. When the IceBreak HTTP server is running it
listens directly to TCP/IP and waits for a HTTP request from the browser.

When Niels mentioned that Apache is involved, that was a misunderstanding.
Niels meant that internally at System & Method we use an Apache server as a
relay in front of IceBreak and other servers in house. This is done ONLY
because of all our internal server traffic between different servers
installed in our complex server farm! This has absolutely nothing to do with
IceBreak!

Regards,

Bent

-----Oprindelig meddelelse-----
Fra: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] PÃ
vegne af Nathan Andelin
Sendt: 5. januar 2011 19:29
Til: Web Enabling the AS400 / iSeries
Emne: Re: [WEB400] Summing up the Icebreak discussion

Kevin, thanks for the reply. If you don't see an IBM i HTTP server running
that
does add a new twist. Maybe Niels wrote his own HTTP server based on
Apache,
like IBM did. If he did, that would clear up a lot of confusion about this
thread.

-Nathan




----- Original Message ----
From: Kevin Turner <kevin.turner@xxxxxxxxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Wed, January 5, 2011 10:46:07 AM
Subject: Re: [WEB400] Summing up the Icebreak discussion

All I know is that I am running Renaissance on a test machine with IceBreak
with
no Apache server running anywhere at all.
There are no IBM Apache functions/programs in the stack at all that I can
see.
If Apache is being used, then it is well embedded and hidden - but I doubt
it.

The statement about front-ending IceBreak apps with Apache just tells me
that
they can run as IceBreak app behind an Apache server as an alternative to
an
IceBreak server, or they can link an Apache server to Icebreak as a remote
proxy
device or something like that. It doesn't mean that all IceBreak apps are
running with Apache running the show on the front end.

I am sure they will correct me if I am wrong.



--
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.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.