< Previous Next >
Re: Extend FIX
George Macdonald / MACD
25 May 2012 7:51AM ET
One of the advantages of FIX is that it is extendable and possible to use it in ways that were not originally thought of.
Having said that, I would recommend always trying to stick to the standards where possible.
If the fields that you require are not present, try looking here to see if someone has already created a user defined field that could suit your purpose:
If you need to create a new field, you can register it here - ideally give it a generic name (i.e. not including your company name) so that other people can use it later.
I would recommend not to create a new message because it would probably be more work for your counterparty in the long run.
> Hi all,
> Sorry, if this is not the appropiate thread (but didn´t find the correct one) The question is about "how to extend FIX N.n protocol?" I have an example:
> Imagine I have a "RequestInfo" service (with fileds) and there is not a FIX message to fit this services...and then I see, at least, 3 options:
> - Use an existing (which fit better) FIX message using their fields (only having in mind the field type)
> - Use an existing (which fit better) FIX messages BUT extending/creating new fields
> - Build a new message
> Which is the best way of extending in terms of following "best practices"
> All the ideas, around this is appreciate. Or even books, url´s, webs, recomendation
> Thanks in advance
Re: Extend FIX
George Macdonald / MACD 25 May 2012 7:51AM ET
Re: Extend FIX Jim Northey / The LaSalle Technology Group 25 May 2012 7:54AM ET