RE: RPG as a Web Service Consumer

> 1. The stuff comes back HTTP-ized.  I'm tired, I can't think of the name
> for it, but it's when an angle bracket gets changed to < or >.
> I'll have to deal with that.

I know that this comment isn't very helpful, but... that's HTML, not HTTP.
It's not part of the HTTP standard in any way.  If it were HTTP, it would
look like "%3c"

I would assume that the web service is doing it this way so that it will
display the text in a web browser rather than try to interpret it, but,
IMHO that's incorrect behavior.  It should, instead, return a different
content-type than TEXT/HTML.

> 2. There's a limit to the size of the data that can be held in an RPG
> variable.  I should have thought of this right off the bat.  I'll have
> to expand the API to use a user space instead.  Scott, what do you
> think?  This can't be all that hard, right?

It's your program (or perhaps Alex's?) that is putting the data into an
RPG variable, not HTTPAPI.   HTTPAPI has two ways of returning data -- it
can return it as a stream file (which is even less limited than a user
space) or it can return it by doing a callback to an RPG subprocedure in a
loop.

My guess is that Alex's code (possibly based on an earlier example that I
wrote) is saving the data that it gets from the callback into a buffer.
You could just as easily make that same routine write it to a user space,
or even to teraspace (which can go much larger than a user space)

HTTPAPI should be able to return as much as 4gb in a single transfer, I
haven't had any problems with that limit yet.