Re: out of memory error / best practices for pushing out large data
Re: out of memory error / best practices for pushing out large data
- Subject: Re: out of memory error / best practices for pushing out large data
- From: Jaime Magiera <email@hidden>
- Date: Sun, 28 Aug 2005 01:03:09 -0400
On Aug 27, 2005, at 11:37 PMGMT-04:00, email@hidden wrote:
Depending on the content-generation infrastructure of your system,
you could make a "component action" or "direct action" that returns
a WOResponse instance where you have used the "setContentStream
(...)" [see API docs] method to get the response to stream out the
data rather than deliver it from data or a string. This seems to
work well for me in situations where large quantities of data need
to be moved over HTTP without timing out the request or consuming
all the memory resources of the virtual machine.
Andrew,
That works perfectly. Thank you. I had never paid attention to
setContentStream before. Looks pretty useful.
thanks,
Jaime
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden