Client APIs, axiscTransportFlush() vs. axicTransportSend()

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