Fwd: IceBreak as an alternative to Apache? -- WEB400

Hi Kevin;

When you say QtmhRdStdin and QtmhWrStout you can almost feel the pain your IBMi is going through trying to convert the static stuff apache only deals with. Going through the CGI layer finally to give you an API so you pop and push data to the stdin and stdout streams. Also struggling by stacking you url / forms parameters in environment variables etc etc ... there are IMHO to many moving parts

The idea behind IceBreak was to start from scratch - not introducing either CGI not apache - but rather find the closest distance from A to B .. the closest distance from the web to your RPG program. It is true, we were inspired by the IIS from Microsoft, So getting the parameter from the URL in icebreak RPG is:

myVar = qryStr('StuffFromTheURL');

same goes for the form:

myVar = form('StuffFromaForm');

and if XML is posted - it supports X-path:

myVar = xmlValue('/xmlroot/anXmlElemet@myAttribute');

Yes - I know you can wrap all the CGI into better looking API's - but it is just lipstick on a pig. All the layers remains the same in a CGI / apache environment.

When people says that ICeBreak runs 10 times faster that apache/ CGI - the I would like to rephrase it, since you can not let nine women produce a child in one monht, but rather you can have 10 times more workload on the same box - which again gives you a much better performance when it is not heavy loaded...

Try this ( Or rather - don't try this) : 1000 users on an old crappy 170 ver 5.1? With apache/CGI I would no expect cool performance. But for one of our customer it was the reality with IceBreak

... OK seeing is believing - read the full story at:

http://systeminetwork.com/article/developers-save-system-icebreak-modernisation

Best regards

Niels Liisberg

Chief Technology Officer

System & Method
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@xxxxxxxxxxxxxxxxx
Web: www.system-method.com and www.Icebreak.org

Den 30/12/2010 kl. 17.49 skrev Kevin Turner:

Bent

I have changed the thread title for this. I was also slightly misled by the examples into thinking it was an ASP approach and nothing else, so maybe the examples could do with an update? I say that in the full knowledge that it is easier said than done and we don't manage to do it very well either!

That aside, is it possible to use the IceBreak HTTP server as a replacement for Apache for applications that have already been written? To be more specific, if I have an RPG program that reads from stdin using QtmhRdStin and returns output via QtmhWrStout can I call that program via the IceBreak HTTP server and have content returned to the browser? Even if it is not possible now, would it be possible after a little bit of pain on my part?

Is it really 10 times faster than Apache as was claimed earlier by Jim?

Rgds
Kevin

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Bent Rønne
Sent: 30 December 2010 15:00
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] 5250 programmer to web programmer

Hi Maurice

With IceBreak, you can choose which path you will go with your web development. You are not bound by any methods or mask programs, but can freely choose from all shelves. All the freedom which IceBreak makes available means of course that you must find the method that suits you best.

Some choose the ASP route, while others choose to split HTML, JavaScript (JS) and RPGLE in different files. Eg. I have recently programmed an "edit system value" maintain application - in ExtJs by the Way. I have divided the pieces into html, JS and RPGLE source in three different files.

You can find all sources here http://www.icebreak.dk/sysvaledit.zip

First there is my HTML (sysValEdit.html) who is just used to link things together with references to my JS and of course the primary link to the application (http://myserver:8080/sysValEdit.html) from the URL in the browser.

Eg.:

<html>
...
<script type="text/javascript" src="sysValEdit.js"> </ script> ...
</ Html>

sysValEdit.js is a larger file that is written in 100% JS and it is the one that contains the ExtJS code. It uses AJAX to retrieve my data from my System i. When the browser is ready for showing, it calls my RPGLE program SYSVALEDIT directly on my System i and returns data to the browser. The RPGLE program is written in pure RPGLE except for the first line of code in this example. This line is used by the IceBreak pre-compiler to switch to RPGLE. But if you like to have your RPGLE isolated in a source file in a library, you simple make your own 100 % RPGLE code and compile the source without the IceBreak pre-compiler - use whatever you like, WSDL, RDi, SEU to edit and compile - I don't care. All you need is a binding directory and guess what - it is called ICEBREAK.

This is just one way to use IceBreak on! You can choose the path that you yourself seem to suit you.

You should also know that there is an IceBreak community where you can find lot more information:

http://www.icebreak-community.com/

I hope that you can use my information in your quest for the perfect solution for Web and System i.

Regards

Bent Ronne
Technical Manager
System & Method A/S

NOTICE: The information in this electronic mail transmission is intended by CoralTree Systems Ltd for the use of the named individuals or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone, so that the sender's address records can be corrected.

--------------------------------------------------------------------------------

CoralTree Systems Limited
25 Barnes Wallis Road
Segensworth East, Fareham
PO15 5TT

Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton, UK
SO15 2EA
VAT Registration Number 834 1020 74.
--
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.