|
On Jun 16, 2021, at 12:32 PM, midrangel@xxxxxxxxxxxxxxxxx wrote:
I'm trying to use RPGLE to build a call to a web service, and using the
client API's I have Nadir's example in front of me, and it make sense, sort
of.
Example from :
https://developer.ibm.com/technologies/systems/articles/i-send-receive-user-
defined-soap-rest-messages-trs/
I use Scott Klement's YAJLDTAGEN along with DATA-GEN to build the JSON.
Looks OK.
This is a POST request.
Then in one example the code:
// Flush transport so request is sent and receive response.
rc = axiscTransportFlush(tHandle);
if (rc = -1);
checkError ('TransportFlush()');
else;
receiveData();
endif;
Says it sends the request. In another example Nadir uses
axiscTransportSend():
rc = axiscTransportSend(tHandle: %ADDR(message):
%LEN(%trim(message)): 0);
if (rc = -1);
checkError('TransportSend()');
else;
flushAndReceivedData();
ENDIF;
So the question is, does axiscTransportFlush send the POST or do I need to
use axiscTransportSend?
If I read the information correctly the sequence should be:
Set the various properties as needed
Use axiscTranspoortSend()
Use axiscTransportFlush()
Use axiscTransportReceive()
One example just uses Flush the other one uses both.
So which is it?
--
Jim Oberholtzer
Agile Technology Architects
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.