Major Description
I made a modification to messenger.c to configure the maximum frame size on transports (there is no API access to this configuration) and then ran a point-to-point test between a sender and a passive receiver using messages larger than the frame max.
The receiver crashes with the following assertion after several dozen messages are transferred successfully.
python: /home/ross/svn/proton/proton-c/src/message/message.c:653: pn_message_decode: Assertion `msg && bytes && size' failed.
Another observation:
When the max-frame-size is specified only by one side of the connection, there is no negotiation. Frames larger than the specified max are transferred. It is not clear from the specification (2.7.1) whether max-frame-size is intended to be symmetric and apply to transfers in both directions on the connection.