Extend FIX

, ,
1

Imported from previous forum

2

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

3

Hi,

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:
http://www.fixprotocol.org/specifications/fields/5000-5999

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.

Cheers,
George.

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

4

Further extending what George has said. The standard was extended to say that previous versions of FIX can incorporate fields and messages from later versions of FIX. In addition to the custom fields, you should check FIXimate and/or FIXwiki for fields in the latest versions of FIX. There is a FIXimate available for the latestEP (Extension Pack) which has the most up to date list of fields.

You can also post in the General Q/A questions about specific fields that you require. The community can then advise you as to the best approach.