× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I would tend to agree with Aaron here.

With CGI you're going from DB to HTML. Throw XML in the mix and you're
doing DB to XML to HTML, another added step.

The root of the problem is the user wants what they want. If they want
that, then it's going to take the time it does. I do see how you could
change your application to not use a temp file, though. Instead of using
SQL INTO to create a temp file, use the SQL and read from the result set
directly.

The time it takes to render 200+ pages of HTML dynamically most likely will
not be able to be made any faster.

Bradley V. Stone
BVSTools - www.bvstools.com
eRPG SDK - www.erpgsdk.com

-----Original Message-----
From: web400-bounces+bvstone=bvstools.com@xxxxxxxxxxxx
[mailto:web400-bounces+bvstone=bvstools.com@xxxxxxxxxxxx]On Behalf Of
albartell
Sent: Tuesday, October 30, 2007 8:46 PM
To: 'Web Enabling the AS400 / iSeries'
Subject: Re: [WEB400] Faster HTML Output.


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 ...

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.