Re: IceBreak as an alternative to Apache?

Hi Jack

The source can be placed in the IFS or as normal source files if you like. If you decide to place the source in the IFS (default) there is a number of advantages you must remember:

. Just in time compilation
. The IceBreak pre-compiler
. RPGLE, JaveScript, .css, .html etc. can be located together
. and more...

I recommend that you use the IFS method because of all the advantages!

If you decide to place the source in a SRC-PF you must remember to add bind directory "IceBreak" to your source and include source member HTTPXSERV from file icebreak/qasphdr like:

DEBUG:
The debug is very simple because of the Job Persistent way IceBreak handle sessions. Again there is more than one way to do it! You can use both the System i debuggers. The GUI debugger and the 5250 service job debugger.

From 5250: work with active jobs for subsystem IceBreak like wrkactjob sbs(IceBreak). Scroll and find the job needed to be debugged and use command StrIceDbg like:

STRICEDBG MYJOBNAME MYPROG

The first parameter is the unique IceBreak generated jobname and the name of the program to be debugged. Now you simply add breakpoints jump back to you browser and execute what ever needed. Jump back again to the debugger and step, evaluate etc. etc.

For the GUI debugger check out this link:

http://www.agentdata.com/BlueSeries/Help/index.html?ex01debug.htm

I hope this can help you understanding more

Regards,

Bent

-----Oprindelig meddelelse-----
Fra: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] På vegne af Jack Kingsley
Sendt: 5. januar 2011 14:24
Til: Web Enabling the AS400 / iSeries
Emne: Re: [WEB400] IceBreak as an alternative to Apache?

Couple of questions on this, where is the source code, traditional IBM
libraries or IFS. How do you debug these programs, does ICEBREAK have it's
own debugger/studio client side program??


On Tue, Jan 4, 2011 at 5:36 PM, Maurice O'Prey <Maurice.Oprey@xxxxxxxxx>wrote:

Oh And Aaron

Sorry about misspelling your name :-)

Maorice O'Pery

Aarron

I take your point and it is well made.

Regards

Maurice

>>With the amount of confusion that comes with IceBreak's mention of it
being
"like ASP", I wish they would discontinue the phrasing. It confused me
when
Neils first described it. In the end it creates immediate debate that
takes
away from discussing the cool features of the framework.

There's my $.02,
Aaron Bartell
www.MowYourLawn.com/blog <http://www.mowyourlawn.com/blog>
www.OpenRPGUI.com <http://www.openrpgui.com/>
www.SoftwareSavesLives.com <http://www.softwaresaveslives.com/>



On Tue, Jan 4, 2011 at 3:25 PM, Richard Schoen
<richard@xxxxxxxxxxxxxxx>wrote:

My two cents:

The only way IceBreak or any other toolset could support ASP.Net would be
to run under the Microsoft .Net Framework stack and support Microsoft
Code-Behinds, Event Model, etc...

Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
----------------------------------------------------------------------

message: 1
date: Tue, 4 Jan 2011 21:11:44 -0000
from: "Maurice O'Prey" <Maurice.Oprey@xxxxxxxxx>
subject: Re: [WEB400] Fwd: IceBreak as an alternative to Apache?

Henrik

Who is using fancy buzzwords, either IceBreak supports Microsoft

ASP.NETpages or it doesn't (and from what I've read so far in these
responses) it

doesn't?

Please stop mixing the term ASP with ASPX (they are completely different
technologies). The rest of the echo stuff is complete crap.

- Maurice O'Prey



Let me try to explain this without fancy buzzwords:

In Icebreak you place your sourcecode in an IFS files. This file looks

and

behaves like an ASP or PHP page where you with a special syntax can

switch

between server side code and client code (HTML etc.) so the sourcecode

can

hold both.

What Icebreak does, is that it translate this IFS file to a RPGLE
sourcemember where all client code (HTML etc.) is imbedded in procedure

call

like WrtNoSection('bla bla bla') in CGIDEV2 or echo('bla bla bla') in my
frame- work that both write the embedded client code into the HTTP output
buffer.

The smart thing is that you do not have to code ...

echo('<html>');
echo('<body>');
echo('hello world');
echo(</body>');

but can code large sections of client code like this

some rpgle serverside code
%> // start client code
<html>
<body>
hello world
</body>
<% // end client code
*inlr =on;


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

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