Re: IceBreak as an alternative to Apache?

The way I have kept state in the past is to have batch jobs listening to
data queues that are waiting for requests. Then you have a "mother router"
program that sits under Apache listening for requests and marrying them up
with the correct data queue based on the session id passed up from the
client.

I am not sure if that is the same thing being described by IceBreak/Niels,
so I would be interested to hear how they are doing it.

To my knowledge you can't put an activation group to sleep and bring it back
to life when YOU want to (the OS might do it, but not on your command). Nor
do I believe you can inject values into variables within a *MODULE object
(though you can now with RPG Open Access which is one of the main features I
am wanting to try as soon as they get the licensing figured out).

Aaron Bartell



On Fri, Dec 31, 2010 at 2:03 PM, Maurice O'Prey <Maurice.Oprey@xxxxxxxxx>wrote:

OK Joe

Thanks for the clear introduction to 'State'. I understand that the
'session
id' is stored in a cookie or in a cookieless environment it is included in
the request or query string.

My question really is how do people using the i store the information that
is related to that session ID, e.g. in server memory (by Session ID),
written to disk (out of state storage) or is there an application level of
State, again stored in server memory?.

Can 'State Objects' be stored in the Server Cache and retrieved from there,
if so what types of objects can be stored and how are they retrieved and
re-instantiated?. Is there an equivalent of ViewState as used in .NET? Of
course there is a painful overhead but that can't really be avoided.

I guess the answer differs depending on whether your using, RPG(le), PHP,
EGL or other.

- Maurice