Re: [Quickfix-users] Duplicate EncryptMethod field in Logon Message

[Oren M. <or...@qu...>]

Because field 98 is not a header field.  It is a body field of the  
Logon message.  If you had set the field on the body of the message,  
you would not see a duplicate.

--oren

> My followup question is: Why does quickfix allow a duplication of such
> a field? From the API, I assumed that "setting" a field means setting
> a field to a certain value, not adding another copy of the field if
> already present. It seems that this method would be better named
> "addField", not "setField".
>
> Are there times when there needs to be two copies of the same field in
> a message header? If not, would you consider modifying the code so
> that "set" methods behave in this way, as opposed to behaving like an
> "add" method?