Robert,
What there is the best solution; state-full or stateless depends very much on the design and what the purpose is. If we start with state-full; it is true that state-full will have a job per session, and the benefit here is that you can keep native OS/400 files and programs open for reuse, use QTEMP as well.
You should also know that IceBreak automatically keeps track of static objects and treats them stateless. With static objects I mean files like. . html,. js.. bmp,. gif ... which is processed by the server in a separate thread per session. It is when treating dynamic objects that the job becomes activated and thus run a request state-full. That is files with extensions. rpgle. aspx, etc. that are treated state-full by the independent job. So you could say that IceBreak runs both stateless and state-full automatically at the same time.
I can see only one reason to use stateless! And that is when your web site should be able to handle many simultaneous sessions. I can not answer you on how many sessions there will be talk about because it depends on several factors - but I mean a lot! With stateless, you must be sure you have full control over the sessions. And thus be sure that you can separate the data between the individual sessions as well. And here you simply tell IceBreak to run in stateless mode...
Regards,
Bent
-----Oprindelig meddelelse-----
Fra: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] På vegne af Dean, Robert
Sendt: 31. december 2010 18:54
Til: Web Enabling the AS400 / iSeries
Emne: Re: [WEB400] IceBreak as an alternative to Apache?
I think the concern is that stateful connections take up more resources. Where a stateful environment requires one job per client, a stateless environment can service many clients per job.
That being said, the IBM i platform is a good choice for a stateful environment because of the way resources are managed.
________________________________________
From: web400-bounces@xxxxxxxxxxxx [web400-bounces@xxxxxxxxxxxx] on behalf of Kevin Turner [kevin.turner@xxxxxxxxxxxxxxx]
Sent: Friday, December 31, 2010 11:18 AM
To: Web Enabling the AS400 / iSeries
Cc: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] IceBreak as an alternative to Apache?
Joe
I have always steered clear of persistent CGI because of a fear that it will not scale as well as a standard stateless environment. Is this fear justified? I have never had the opportunity to put it to the test.
Kevin
On 31 Dec 2010, at 16:05, "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> wrote:
There is nothing particularly special about stateful connections. In
traditional CGI processing this is known as persistent CGI, and has been
around since about 1998. Not only that, it's a built-in capability of
the IBM i that has been around for nearly as long on the IBM Apache
server. As far as I know, it goes back to V5R1 or V5R2, maybe further.
That's a decade or so. And with IBM, you control it by session, not by
server, so you can have persistent or non-persistent sessions on the
same server.
Also, this is a fundamental capability of WebSphere. Via the Java
toolkit you can have both persistent and non-persistent connections and
in fact, if you needed to you could have both persistent and
non-persistent connections in the same session! EGL supports this
capability out of the box; when you define a program (RPG, COBOL,
whatever) to be called you define whether it is stateful or stateless.
So you can have both stateful and stateless connections in the same
session! Stateful connections each have a persistent job, with
overrides and ODPs and a QTEMP - the job is named QZRCSRVS and runs in
QUSRWRK.
So, it's nice that IceBreak has this, but it's really not unique to the
tool.
Happy New Year!
Joe
P.S. For debugging, you might want to look into Service Entry Points.
It makes debugging web programs a breeze, even in non-persistent CGI!
Hi Kevin
"task switch feature"! This feature is a feature which is special in IceBreak. It is a feature that keeps track of your browser session and sends request on to an isolated job native under OS/400. This means that your programs can remain open with file pointers, variables etc. It also means that you might use the QTEMP to something practical - again. Further, you can work with the job through normal OS/400 interface such as WRKACTJOB. It also means that with this technique can debug programs without having to think about other jobs and sessions.
--
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.
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.
midrange.com
