It helps with getting it off the server faster and puts the burden on the
client's computer. Has I have said and some of you guys keep forgetting...
the problem is not getting the data with the SQL statement. The problem is
reading the large amount of data. So to use the suggestion of "not" using
the temp table doesn't help. Cursor read or regular I/O doesn't make a
difference.

For some reason, I thought that in V5R4, or another version, you were given
the ability to do a SELECT ... FOR XML (or something similar to that). But
I haven't found any documentation on it.


Michael Schutte
Admin Professional
Bob Evans Farms, Inc.
"The Secret's the Sauce! Enjoy our new Bob-B-Q Pulled Pork Knife & Fork
Sandwich!"




"albartell"
<albartell@gmail.
com> To
Sent by: "'Web Enabling the AS400 /
web400-bounces+mi iSeries'" <web400@xxxxxxxxxxxx>
chael_schutte=bob cc
evans.com@midrang
e.com Subject
Re: [WEB400] Faster HTML Output.

10/30/2007 09:45
PM


Please respond to
Web Enabling the
AS400 / iSeries
<web400@midrange.
com>






Sending XML instead of HTML will certainly improve your throughput, but it
still needs to be rendered to a readable format somewhere.

How exactly is XML vs. HTML improving throughput? It sounds like you are
more referencing the bloat of using tables for formatting vs. CSS. I would
have to guess that CSS would allow for a smaller document than XML - but I
suppose that depends how bloated the XML tags are.

Aaron Bartell
http://mowyourlawn.com


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Pete Hall
Sent: Tuesday, October 30, 2007 5:25 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Faster HTML Output.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sending XML instead of HTML will certainly improve your throughput, but it
still needs to be rendered to a readable format somewhere. I have a captive
IE shop (good and bad in that) where I can rely on msxml3 to give me
consistent rendering, so I us client side rendering. It offloads a lot of
processing from the server side, and is certainly friendlier to network
bandwidth. Still can take a while to render a document with xslt though,
and
that's entirely dependent on client horsepower. BTW, if you go this route,
use attributes instead of nested elements where possible.
It makes for a much smaller datastream, and do NOT worry about indenting
nested elements. That's a big-time throughput hog with large documents.

Pete Hall
pbhall@xxxxxxxxxxxxx
http://pbhall.us


--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.