RE: http_url_post speed concerns

["Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>]

Sender: "Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>

Good explanation on the POST steps.  I had no idea that a receive was done
before the actual POST data was sent, interesting.

<Snip>I'd like to help with that project.  I've upgraded my system to V5R2,
and
one of the reasons was that I wanted to try out your XML stuff.
Unfortunately, I'm working on too many things already, so it may take me
a while to get to it.
</Snip>

Sweet!  I would love to have your help or anyone else that is on this list
for that matter!  Currently I am compiling to V5R1, but hopefully will be
upgrading to V5R2 in the next couple months.  BTW, for anybody that doesn't
know about the RPG XML Parser, it can be found at
http://sourceforge.net/projects/rpg-xml-parser/.  A new version is coming
out soon.

Thanks to all that have responded to my questions,
Aaron Bartell


-----Original Message-----
From: Scott Klement [mailto:klemscot@xxxxxxxxxxxx]
Sent: Friday, June 13, 2003 3:49 PM
To: 'ftpapi@xxxxxxxxxxxxx'
Subject: RE: http_url_post speed concerns


Sender: Scott Klement <klemscot@xxxxxxxxxxxx>

On Fri, 13 Jun 2003, Bartell, Aaron L. (TC) wrote:
>
> I am not sure if it is safe to write it this way, because you could
> potentially have that sequence of characters in the content of the POST
> response.

The recvresp() doesn't read everything, Aaron, it only reads the HTTP
header information.  The part that you're calling the "POST response" is
read by recvdoc().

>
> >...and on average, will be reading less than 200 bytes.
>
> How did you come up with that average?  I may be an exception, but I am
> passing XML back and forth, and I am easily past 1000 bytes going out and
> coming into each web service.

Yes, but that part is read by recvdoc().

> Oh, don't you just love XML;-)  It looks like I would have to have my
> program that is hosting the web service specify that info was chunked
> for it to come across as a "document" per your comment about recvdoc()
> being much faster?

No, when it's chunked, it's received by RecvChunk() normal documents,
including those generated by CGI scripts in response to a POST are
received by recvdoc().  (or SSL_recvchunk() and SSL_recvdoc())

There are 5 parts of a POST conversation:

      1) request a URI:  handled by SendReq() or SSL_SendReq().
      2) receive HTTP response (HTTP protocol data or "headers" not
           the returned document itself)  handled by recvresp() or
           SSL_recvresp()
      3) send the actual POST data.  handled by SendDoc() or
           SSL_SendDoc();
      4) receive HTTP response to POST data (again, just HTTP protocol
           data, not the document itself)  handled by recvresp()
           or SSL_recvresp()
      5) receive the returned document.  handled by recvdoc() or
            SSL_recvdoc.

A GET conversation is almost the same, except that you omit steps 3 & 4,
and send slightly different data to the server in step 1.

>
> I hear ya on wanting to get help, I haven't had one ounce of outside help
> yet for the RPG XML parser I am working on, of course I have only had that
> open for a couple months and I don't have it in CVS yet (as you pointed
out
> Scott :-).  I wont have time to punch out any helpful code for a couple
> weeks (conferences) but will give it a shot after I am done with those.

I'd like to help with that project.  I've upgraded my system to V5R2, and
one of the reasons was that I wanted to try out your XML stuff.
Unfortunately, I'm working on too many things already, so it may take me
a while to get to it.

At any rate, this is what iSeries/400 people are like.  They don't
understand open source.   They think it's the same thing as freeware or
shareware.   They don't understand that they're supposed to help.

In the FreeBSD or Linux community that's not as much of a problem.  There
are still people who just use the products, but there are also lots of
people who help with development.

But I think, slowly (very slowly) people are coming around.   iSeries
people are always behind the times...   they think TCP/IP is the new way
to do things :)  (it was created in the 60's and 70's)  they still refer
to ILE RPG as "new".  (it's been around for almost a decade now) They
think Java is the future (a sentiment that died out everywhere else around
1999) they'll get there eventually.

-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------