×
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.
Hi Scott,
yes "http_url_post_stmf()" maybe should fit better because the full XML message is first prepared into a stmf and then sent. I suppose that the procedure sends the stmf as is, without any conversion.
The whole transaction is syncronous and after we sent the XML message we have to wait for the ack from the counterparty; this could take some time because thay have to parse and validate the message, including the decode of the pdf from base64; i think that the time out parameter should be set to an adequate value to avoid dropping connection before the transaction completed.
Thanks for your suggestion (and your api).
Giuseppe.
--- Mar 21/10/08, Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> ha scritto:
Da: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
Oggetto: Re: HTTPAPI xml size limit
A: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Data: Martedì 21 ottobre 2008, 23:41
Yes, post_raw does do EBCDIC/ASCII translation. However, there's an
http_url_post_raw2() that does not. Or perhaps http_url_post_stmf()
would be more appropriate to your situation? It sends a stream file
instead of data supplied in your program.
I don't understand the 'DEPRECATED' comment. Http_url_post_raw()
is
certainly not deprecated. (Though, there's one named
http_DEPRECATED_url_post_raw() which is deprecated -- but that's a
different procedure from http_url_post_raw)
beppecosta wrote:
does the "http_url_post_raw" convert the data from ebcdic to
ascii before sending ?
The srvpgm says that this method is DEPRECATED. What should we use instead
?
midrange.com
