What about Batched Invocations about capnp-vs-ice

[kentonv]

Hi Ben,

As I understand it, ICE's "batched invocations" allow you to send multiple messages in one batch but still do not allow the second message in the batch to depend on the response to the first message. This can reduce the number of network packets sent but does not reduce the number of round trips required.

(I could be wrong on this, but I did ask one of the ZeroC authors if they have anything like promise pipelining and they told me they did not.)

Some systems (not ZeroC ICE, AFAICT) support a concept of "batched invocation chaining" which is very close to promise pipelining, but still requires that all the calls be made in a single batch. Promise Pipelining is more flexible in that you can kick off the first call before you're ready to make the second, and you also receive the responses when they're ready rather than all at once. This also tends to mean you can keep your code much cleaner, because the code responsible for filling out the first request does not necessarily need to know whether anyone plans to pipeline on its result.