Re: IceBreak as an alternative to Apache?

Yes it does. It's called a job. That is the state management on the i. It's built for that, because all the jobs share the same program space. The i is a non-von Neumann design in that jobs share an essentially non-modifiable program space. Thus when you run hundred of order entry jobs, they don't need to duplicate the program space. They each have their own area for data, called the Process Access Group or PAG. The PAG is the state of the job and the i manages it very nicely.

We did stateless. That was the CCP model. We outgrew it in the 70s and moved on. We now have stateful architecture, both in the green screen and the web.

You can still do anonymous stateless processing, but eventually you want a stateful connection and we have that, either through persistent CGI or through the Java AS400 connection object.

Joe

Kevin

I don't think the correct term is session management as that only relates to
an individual session and ends when the user closes their browser. State
management persists beyond that and I hear again the horrible term 'home
grown' ... (how many versions of that are there?)

I'm really hoping that the i would have some kind of state management built
in to the operating system.

Has it?

- Maurice