Re: Flush response
Re: Flush response
- Subject: Re: Flush response
- From: Chuck Hill <email@hidden>
- Date: Tue, 14 Jul 2009 09:01:02 -0700
Hi Bjarni,
On Jul 14, 2009, at 7:51 AM, Bjarni Sævarsson wrote:
Hola.
I have a component that, in certain cases, returns a massive( up to
100.000) row table.
Now, I would like tell the users that patience is golden in those
cases but since its all in a single component I have two options,
ajax it or flush the response.
Now to the question, is it possible to flush a WOResponse object and
if so then how?
Regards,
Bjarni Sævarsson
I'd try and catch this before response time. One idea is to do a
count of the rows that will be returned for a qualifier, and if it is
greater than 2,000 (for example), then don't fetch them right away.
Instead, return a message to the user like "Your search matched 87,651
rows, showing these will take a long time. Click here to show these
rows. Click here to change your search criteria". And if they
decided to go ahead, they already know it will be slow.
Another, much better, idea is to use ERXBatchingDisplayGroup. This
fetches and shows the data in batches, thus avoiding the entire very
large response issue. It is also much kinder to server memory usage.
Chck
--
Chuck Hill Senior Consultant / VP Development
Learn WO at WOWODC'09 East in Montréal this August!
http://www.wocommunity.org/wowodc09/east
http://arstechnica.com/apple/news/2009/07/webobjects-sliced-from-106but-prognosis-of-death-premature.ars
_______________________________________________
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