Re: IceBreak as an alternative to Apache?

Interesting comments about using DB2 tables for state information. I have
done both - though never a larger site with the DB2 tables. Might have to
try it again.

The one thing I don't like about *USRIDX and *USRSPC is that it is much
harder to debug, but storing stuff in DB2, even temporarily, can make
debugging much easier.

That's probably my least favorite aspect of stateless web programs is trying
to debug them. Sure I can use SEP's from RDi, but unless I am the only one
using a particular instance of Apache, then I could be spawning a lot of RDi
SEP sessions on my desktop. That's one of the downfalls of not having the
entire stack, including UI, controlled by one entity - it necessitates more
fancy tool above and beyond STRDBG (which I still use quite a lot).

Aaron Bartell
www.MowYourLawn.com/blog
www.OpenRPGUI.com
www.SoftwareSavesLives.com



On Fri, Dec 31, 2010 at 2:42 PM, Kevin Turner
<kevin.turner@xxxxxxxxxxxxxxx>wrote:

In an rpg environment we have tried user indexes to store session data - we
have also used user spaces. However, these days nothing seems to beat a good
old fashioned physical file. A lot made of the overhead involved in
maintaining state this way, but I believe it to be slightly misleading. The
IBMi does this extremely quickly, and the amount of session data stored even
in our most complex apps is small enough for it to be a non-issue.

I would like to try a stateful web app, but with so much code already
written for a stateless environment it is difficult to justify the
experiment.