Storing Large Objects in Session

[jamie....@googlemail.com]

I'm writing an MVC framework using Classic ASP which needs to place
large disconnected recordsets and dictionary objects into the session
object so that they are available after a Server.Execute.

The Session contents are being removed with a
Sesion.Contents.RemoveAll() after use and do not persist to the next
request. I'm wondering however if this a good idea in terms of
scalability. I've read a lot of conjecture about memory fragmentation
when storing large objects inside the session object and i wonder has
anyone else used a similar approach with success/failure

I've asked this elsewhere and been flamed as an "Classic ASP Hater" of
some kind. I can assure you i'm not :-)