RE: Serious speed issues... -- WEB400

Joel,

I doubt you'll hit this, but there is a slight logic error in your code.
Given a string of:

"ABCD    "

Your code will return 4 as the len, and you'll write the first 4 bytes and
get "ABCD" as the result, no? But what if your string contained:

"  ABCD  " (note the _leading_ blanks)

Your code will return 4 as the len and you'll write the first 4 bytes and
get "  AB" as the result, not what you want.

I think you need to change the %trim to a %trimR so in the second example
you'd get 6 as the len and write "  ABCD" which is what you'd expect to get,
no?

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)



-----Original Message-----
From: Joel R. Cochran [mailto:jrc@masi-brac.com]
Sent: Friday, August 09, 2002 09:11
To: 'web400@midrange.com'
Subject: FW: [WEB400] Serious speed issues...


Ooops... it was so late last night I didn't pay attention to where this was
going... I meant to send it out to the list.  Thanks to everyone who
responded, it really shows how cool this list is!

Joel R. Cochran
Director of Internet Services
VamaNet.com
(800)480-8810
mailto:webmaster@vamanet.com


-----Original Message-----
From: Joel R. Cochran
Sent: Friday, August 09, 2002 1:58 AM
To: 'Nathan M. Andelin '
Subject: RE: [WEB400] Serious speed issues...


Thanks Nathan,

Seeing that page size was the key.  The page size was simply way too big for
these simple pages and when I looked at the HTML source the spacing and
everything was seriously out of whack but I couldn't figure out why... until
I sat bolt upright from a dead sleep at 1AM knowing exactly what the problem
was.

Remember from my original post there were two things I did: the apache thing
and the QzhbCgi thing.

Well, I was messing with Brad Stone's new e-RPG(v2) book (must have, by the
way) and he had a great idea to put the NewLine character in the WrStout
wrapper, so while I was making the change over (so I could play with
CgiParse) I rewrote my WrStout sub-procedure.  When I did I missed one tiny
little step in setting the size of the Data Length parameter.

I had:
  WrtDtaLen = %len( WrtDta );

When I should have had:
  WrtDtaLen = %len( %trim( WrtDta ) );

Everytime I wrote to Standard Out I was writing 1024 characters, most of
which were blank!  That means super huge HTML files and super long
downloads.

Talk about shooting yourself in the foot!  Well, my sore foot and I are
going to bed since it's 2AM.

Thanks to everyone who responded, wouldn't you know it had to be something
silly?


Joel Cochran
Director of Internet Services
VamaNet.com

-----Original Message-----
From: Nathan M. Andelin
To: web400@midrange.com
Sent: 8/8/02 4:55 PM
Subject: Re: [WEB400] Serious speed issues...

> From: "Joel R. Cochran"
> http://www.vamanet.com/cgi-bin/ABOUT
> http://www.vamanet.com:1550/cgi-bin/ABOUT

That's weird.  Both links generate a 185KB page, mostly blank.  They look
fine in the browser, but a page that size takes a long time to download.

Nathan M. Andelin
www.relational-data.com



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