Minor Description
We currently set the maxFrameSize value in Proton using the WireFormat maxFrameSize value. This not the correct application of this property as it is meant to control the max size a frame we will accept before we disconnect a client whereas in AMQP this control how large a frame is before the transport starts splitting the data into multiple frames.
Setting this value on Proton has other side effects like increased memory utilization and decreased performance. Instead of linking these we should introduce an additional property on the AMQP WireFormat class to allow for setting the maxAmqpFrameSize which defaults to no max.