Re: 'green screen' not sellable --> WE(?) are the problem

Nathan



If you run stateless you need to have a mechanism to store (restore)
session and program variables from/to the stateless programs running in the
QZSRCGI jobs. I use some standardized DB tables that is shared between all
QZSRCGI jobs under the Apache domain.



This method also provides the security in the system not only to access the
CGI programs but also to store hidden values such as a customer number that
is bound to the session and thereby can’t be changed from the client’s
browser by manipulation/injecting the DOM or session Cookies.



PS. If you run Apache there is no such thing as persistent CGI but that is
another rather long story. If you like I could explain it.

On Wed, Jun 10, 2015 at 11:51 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Okay, that explains what you mean. Now, how might that be relevant? Seems
like every web application architecture has some method of saving and
restoring state, or anyone can easily roll their own. Or in a case like
persistent CGI, state for each individual user is managed in their own
individual "JOB". Or is your point that one method for saving and restoring
or otherwise managing state might be better than another?



On Wed, Jun 10, 2015 at 3:33 PM, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:

Nathan

no, you may have 6 QZSRCGI jobs running under a Apache server and they
serves
500+ users - you have no way to know where on request happens to be
processed -
so you need a mechanism that transfers server sides variables between the
jobs.

On Wed, Jun 10, 2015 at 11:27 PM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

Nathan,
powerEXT delegates states by passing specific states to each other in

the

stateless environment.

Okay, so what does that mean and why might it be relevant? By

"stateless

environment", are you referring to the IBM i HTTP server?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
Regards,
Henrik Rützou

http://powerEXT.com <http://powerext.com/>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.