Re: Best practice for exporting big data...
Re: Best practice for exporting big data...
- Subject: Re: Best practice for exporting big data...
- From: "Jerry W. Walker" <email@hidden>
- Date: Tue, 5 Dec 2006 11:11:19 -0500
Hi, James,
I haven't used D2W all that extensively for public facing apps, but I
think I would try to find a way to limit the data they can receive on
a single fetch, whether they apply filters or not.
Few people really want to slog through more than 100 records or so.
Typically, when they see even that volume, they realize they need to
filter and don't even inspect the result, so dumping a few thousand
rows on them is seldom helpful.
Limiting the fetch is easy to do for custom apps or for EOModeler
generated fetches. I haven't time to confirm that it's possible with
D2W right now, but I think it is.
Regards,
Jerry
On Dec 4, 2006, at 9:53 PM, James Cicenia wrote:
Hello -
I have created a nice custom report generator based upon D2W and it
works
like a charm except for the occasional bad problem.
If a person doesn't filter the selection and pulls all the data
with all the attributes
it can cause my server to basically deny others.
Do I have to put this process in a different thread? Do I have to
use a long response
page?
Thanks
James Cicenia
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com
This email sent to email@hidden
--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial
Strength Internet Enabled Systems
email@hidden
203 278-4085 office
_______________________________________________
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