You'll find *everything* is a no-go if that's their concern. On Wed, Oct 19, 2011 at 9:49 AM, Charles Godfrey <cha...@gmail.com> wrote:
> Sorry, let me clarify. > > I meant loading all those objects into the action class vs. lets say > loading > 50 at a time and doing out.println() in your servlet, then repeating this, > so you are only ever loading 50 (or whatever number) into memory. > > I know you can always throw more memory at it, or paginate long lists of > data so you don't have to load all at once, but the question I'm being > asked > is how does Struts2 perform if I do need to present a large amount of data > to the user? > > I had the same reaction you did, but is there any memory/session/advanced > feature, anything at all, that even relates to this? > Until I can show this won't be an issue, Struts2 is a no go, so I'm > reaching > out to you all. > > -Charles > > > > On Wed, Oct 19, 2011 at 9:21 AM, Dave Newton <davelnew...@gmail.com> > wrote: > > > I don't understand; what does this have to do with Struts 2 *or* MVC? You > > load a thousand objects into memory, you load a thousand objects into > > memory--that's pretty much framework, design pattern, and > language-neutral. > > > > Dave > > On Oct 19, 2011 9:18 AM, "Charles Godfrey" <cha...@gmail.com> wrote: > > > > > Hello everyone, > > > > > > Not sure if this is the right forum for this question. > > > > > > I made a presentation to my dev team to use Struts2 and the issue of > > "uses > > > too much memory" came up. If I need to retrieve 1000 rows from a > database > > > and have a JSP present those to the user, how does one handle having > that > > > many objects in memory. (Yes I know this many rows should be paginated, > > > etc, > > > but assume the above is a requirement for now). Is there anything in > > > Struts2 > > > that addresses large amounts of data that need to be kept around until > > the > > > JSP is done presenting it? Is this more an "MVC" issue instead? > > > > > > Thanks, > > > -Charles > > > > > >
