The only downside to using the session is that the object remains in memory until the session is invalidated. Depending on your session timeout, this could be problematic. If you're good about removing objects from the session that are no longer needed, you shouldn't have a problem.
On 18 Feb 2005 14:29:08 -0000, mfaine <[EMAIL PROTECTED]> wrote: > > On Fri, 18 Feb 2005 08:04:27 -0600, Heath Borders <[EMAIL PROTECTED]> > wrote : > > > If this document object is large, saving it in the session, or back to > > temporary database tables might be your best option. > > > > We're doing a lot of similar things to this right now with our apps. > > We create an object on the first page, and then make modifications > > (usually adding relationships and other objects) to it as we move > > along. This, in turn, can make the amount we store in session really > > large, but currently, we only have a very small concurrent user base, > > so its ok. > > > > I'm starting to think I need to get busy modifying the code to place the > document object in the session. I guess I'll just have to be sure to clear > the session at appropriate places in the process. Isn't there some > drawbacks to using session? I know I originally had a reason for giving up > on session scope in the first place. We are fortunate like you at the > moment and do not have that many concurrent users. I'm afraid though that > this might change quickly if the application is sucessful. Hopefully by > then we will be able to throw more hardware at it if necessary. > > Thanks, > -Mark > > -- -Heath Borders-Wing [EMAIL PROTECTED]
