Samir Talwar 2b3cf1b3c0 ledger-api-client: Rename maxInboundMessageSize to maxInboundMetadataSize. (#7290) ... * ledger-api-client: `maxInboundMessageSize` -> `maxInboundMetadataSize`. CHANGELOG_BEGIN - [Scala Bindings] Rename a field in the ``LedgerClientConfiguration`` to ``maxInboundMetadataSize``, to match the builder Netty channel builder. It was incorrectly named ``maxInboundMessageSize``, which is a different channel property that configures the maximum message size, not the header size. CHANGELOG_END * ledger-api-client: Introduce a `maxInboundMessageSize` config property. We use this a lot; easier if it's in the configuration. CHANGELOG_BEGIN - [Scala Bindings] Replace the ``LedgerClientConfiguration.maxInboundMessageSize`` property with a new one that represents the maximum size of the response body. CHANGELOG_END		2020-09-02 08:41:34 +00:00
..
daml	Add queryContractId to DAML Script (#7289)	2020-09-01 10:31:34 +00:00
runner	ledger-api-client: Rename maxInboundMessageSize to maxInboundMetadataSize. (#7290)	2020-09-02 08:41:34 +00:00
test	Add queryContractId to DAML Script (#7289)	2020-09-01 10:31:34 +00:00