MaxMessageSize@LogonMsg negotiated

Imported from previous forum

[ original email was from Ryuji Okada - okada@quick.co.jp ]
My question is how to use MaxMessageSize.
I think this as follows.
MaxMessageSize@LogonMsg should be negotiated in each sides.
Company A send Logon MaxMessageSize=99999
===>
Company B send Logon reply MaxMessageSize=9999
<===
Company A sending Maximum data size is 9999
because Company B can’t receive 10000 byte data

Company A and Company B could have different MaxMessageSize limits and thus Company B does not need to echo back the exact same value that Company A specified. This field specifies the maximum size of messages you can receive. You can obviously control the size of messages that you construct and send. FIX 4.2 introduced the concept of fragmentation for specific messages (e.g. MassQuote) in which a very large repeating group can effectively be split in to several individual messages linked together each with a repeating group. Recognizing that there are maximum limits as to how large messages can be and that those limits will vary, this field could be used by a sender of messages which can be fragmented to control their fragmentation rules.

> My question is how to use MaxMessageSize.
> I think this as follows.
> MaxMessageSize@LogonMsg should be negotiated in each sides.
> Company A send Logon MaxMessageSize=99999
> ===>
> Company B send Logon reply MaxMessageSize=9999
> <===
> Company A sending Maximum data size is 9999
> because Company B can’t receive 10000 byte data
>