Nathan

Well I guess you have a number of options:

1/. Give everyone a 5250 terminal

2/. Write your own super efficient Browser

3/. Redesign your application

Number 3 is my preferred option ;-)

Maurice


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Nathan Andelin
Sent: 03 August 2012 20:49
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] XMLSERVICE with .Net

From: Maurice O'Prey
Nathan
If you are experiencing performance issues have you explored the types
of server side data caching offered by the IBMi? Are there any?

I'm getting GREAT performance on IBM i!

But now I'm wondering why anyone might be thinking otherwise. Maybe I'm
unable to communicate coherently ;-)

The ONLY performance issues I have experience in the course of this thread
are entirely on the client side, parsing and loading SQL result sets into
client objects. An SQL result set may be returned in 1/10th of a second
(that includes download time over a LAN), then it may take 8 seconds to
parse and load it into a client object (a Visual Foxpro table or an IBM i
Access View object).

Why would we be concerned about differences between IBM i CGI/XML and
QZDASOINT/ODBC? The differences in performances are TINY in comparison to
the performance of Windows clients!

-Nathan

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