You are not going to incur too much overhead from using WDDX and pushing it
down to the browser using ACTION="CFML2JS" because in this case the packet
is not pushed down as XML it is pushed down as a JS array with all possible
white space removed. All in all its pretty compact.
-eric
------------------------------------------------
If to please people we offer what we ourselves disapprove, how can we
afterwards defend our work.
-George Washington
Eric Barr
Zeff Design
(p) 212.714.6390
(f) 212.580.7181
-----Original Message-----
From: Dick Applebaum [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 05, 2001 12:00 PM
To: CF-Talk
Subject: Re: LARGE QUERY RETURNS
Bill
If you absolutely must return that many rows to the browser at one
time (you can't page it)...
Then one way to limit both the CF processing and bandwidth is to
offload the formatting of the data to the browser as follows, (kind
of a pseudo WDDX):
1) in CF loop through the query and append each data column to a
string separated by some unique separator, e.g. the pipe | character
and each row by some other unique character, e.g. tilde ~
2) you return this string to the browser, along with a short
JavaScript routine... possibly in a hidden frame
3) when the page/frame is loaded by the browser it kicks off an
onLoad JavaScript routine which does a split of the string into an
array (rows of the original query).
4) Then you loop over this array doing another split of each row into
a subarray (columns of the original query).
5) You loop over this subarray and format the output as desired
You can do the same thing with WDDX but the WDDX packet is very large
due to the veberose format of XML,
Since all the data is fixed-field format, you don't need this overhead.
It is actually easier to write than to describe.
HTH
Dick
At 10:52 AM -0500 1/5/01, William J Wheatley wrote:
>Ok I have found that when i return alot of returns to a page, 5000+ it adds
>quite a bit of time to the processing on the CF side with displaying the
>information as opposed to it being database bottleneck.
>
>In Fact the database is Hustling returning the 70,000 records in about 4
>seconds but it takes CF quiet a bit of time to display them. Now is there
>anything i can do to cut down on the time it takes to show those, other
then
>doing a Next Previous system??
>
>
>Bill Wheatley
>Director of Development
>AEPS INC
>Allaire ColdFusion Consulting Partner
>Allaire Certified ColdFusion Developer
>http://www.aeps.com
>ICQ: 417645
>http://www.aeps2000.com
>954-472-6684 X303
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
