Sorry, not had to do it in a web app, and where I have done it - memory wasn't an issue. I don't know any more than using the buffered input/output streams performance wise.
I'm still on java 1.3.1, but they have done quite a bit on IO in 1.4, maybe theres help there http://java.sun.com/j2se/1.4.2/docs/guide/nio/index.html Also there is an IO package in commons - doesn't seem to have anything performance wise for reading - but there is a DeferredFileOutputStream which stores in memory until a specified threshold is reached - how that differs from a BufferedOutputStream I can't really see. http://jakarta.apache.org/commons/io/ http://jakarta.apache.org/commons/io/apidocs/index.html Anyway, this might be an issue for me soon, so I hope someone else jumps in that has experience. Niall ----- Original Message ----- From: "Mark Lowe" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, February 26, 2004 1:24 PM Subject: Re: need help converting from session to request scope > Niall > > Any opinions on read and writing to flat files to avoid additional ram > use? Or you reckon that the reading and writing would consume similar > amounts of ram? I'll get around to trying it when i get a moment. > > On 26 Feb 2004, at 14:04, Niall Pemberton wrote: > > > Given your scenario, it sounds like a good candidate for a session > > scoped > > form. > > > > I agree with what Mark Lowe said - usually/often "...theres no more > > work > > invloved scoping to request" - thats been the case for my app. I would > > also > > do what you said in a previous post - which is "clean up" the session > > stuff > > when they navigate away to another part of the app. > > > > I'm in the "do it in request unless you have good reason(s) to use the > > session" camp - rather than the "anti-session" camp as it may have > > appeared > > in previous threads. > > > > Niall > > > > ----- Original Message ----- > > From: "Paul McCulloch" <[EMAIL PROTECTED]> > > To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]> > > Sent: Wednesday, February 25, 2004 4:13 PM > > Subject: RE: need help converting from session to request scope > > > > > >> My application has an Asset search form. The user can enter many > >> criteria > > to > >> search on. > >> > >> Most of these criteria themselves are looked up from the database > >> (e.g the > >> Person associated with the Asset search). When the user selects a > >> search > >> criteria (e.g. the Person) I store the DTO for that person on my > >> search > >> form. The view element displays details about that Person on the > >> search > > form > >> until the search form is cleared. > >> > >> Many requests will be made to find the criteria before the Asset > >> search > >> itself is performed. > >> > >> To do this using a request scope form would require that I transfer > >> all of > >> the details I want to display about that person in hidden inputs on > >> the > >> form. If the details I want to display about a Person change then I'd > >> also > >> need to change the hidden fields. In addition once I ship the > >> application > > to > >> my customers they may have their own JSP developer show extra > >> prpoerties > > of > >> the selected Person. > >> > >> So, that's my justification for using session scoped form beans. Any > >> comments gratefully recieved. > >> > >> Paul > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]