[prev in list] [next in list] [prev in thread] [next in thread] 

List:       velocity-user
Subject:    Re: memory problem with display table export options
From:       Daniel Dekany <ddekany () freemail ! hu>
Date:       2006-09-11 23:17:44
Message-ID: 1566917344.20060912011744 () freemail ! hu
[Download RAW message or body]

Monday, September 11, 2006, 11:28:18 AM, Steve O'Hara wrote:

> Correct me if I'm wrong, but Velocity doesn't stream it's output
> until the whole template has been satisfied.

Come on, not even Velocity can be that lame... If that happens, it's
rather that some frameworks chose to buffer the output, because that's
needed for nice error pages, or for implementing page layout stuff.

> Therefore, if you are creating a very large response with a
> template, then it builds the whole response in memory before sending
> it out.  Therefore, it doesn't matter what you set your VM memory
> constraints to, you will always stand a chance of exhausting the memory.
>
> Steve

-- 
Best regards,
 Daniel Dekany


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]