Re: Overwhelming a Web Application Server

["Dean, Robert" <rdean@xxxxxxxxxxxx>]

------------------
I guess that's an OO thing.  My perspective was more in line with Brad Stone's idea of storing session data in a DB record, keyed by session ID.  The session ID is stored in a cookie that goes back and forth between a browser and server.  Use the key to fetch a DB record to restore session data.  In that context the "if all goes well" comment sounded hilarious.  RPG programmers don't think twice about "chaining" to a record, and hardly concern themselves about it's reliability or performance.
------------------

In a nutshell, the situation on the Java side is analogous to a level check on the RPG/DB2 side.  You should normally only have to worry about it if code changed, or the object/file being accessed isn't the one the running code was compiled against.