Send Multiple Commands Per Incremental Upload

Inbound API allows sending multiple commands in the same SOAP request.

The SOAP Client application therefore should not send each command individually but should accumulate them for some period of time (e.g. several seconds) and then send the whole batch.

Sending multiple commands per request dramatically increases performance, in part because the network latency overhead can be as high as 0.5 seconds per request, so without batches sending more than 1-2 commands per second, per client thread will not be possible.

As a general rule, a SOAP request containing one activity is processed in approximately the same time as the request containing multiple activities.

Example SOAP request containing 5 commands:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:toatech:InboundInterface:1.0">

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:toatech:InboundInterface:1.0"> 
	<soapenv:Header/> 
	<soapenv:Body> 
	<urn:inbound_interface_request> 
	<!-- 'user' and 'head' nodes skipped --> 

	<data> 
	<commands> 
	<command> <!-- command payload --> </command> 
	<command> <!-- command payload --> </command> 
	<command> <!-- command payload --> </command> 
	<command> <!-- command payload --> </command> 
	<command> <!-- command payload --> </command> 
	</commands> 
	</data> 
	</urn:inbound_interface_request> 
	</soapenv:Body> 
</soapenv:Envelope>