Re: Overwhelming a Web Application Server

[Nathan Andelin <nandelin@xxxxxxxxx>]

> From: Walden H. Leverich
> Why? Because of the "if all goes well" comment?

Well, yes actually.  I honestly thought that Thorbjoern was making a joke - no offense intended.

> Think about it. I serialize an object, now I do an upgrade of my
> application, and then I deserialize the object, that's a non-trivial
> deserilization since the new object might look different than the
> old object.

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.

> Remember, you may be deserializing the object many hours
> later, one of our applications run session times around 24 hours.

I admit that I don't understand much about OO deserialization.

> We have many users that leave there browsers up overnight and
> expect to still run in the same session the next day.

Now that's something I can relate to.  You definitely want to keep users happy, and I know that in a lot of cases they expect their web applications to behave like desktop applications.  In some cases, you don't want sessions to expire, or be "serialized".

Nathan.