Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

message formats #59

Open
uwezukwechibuzor opened this issue Apr 11, 2023 · 2 comments
Open

message formats #59

uwezukwechibuzor opened this issue Apr 11, 2023 · 2 comments

Comments

@uwezukwechibuzor
Copy link
Contributor

According to the FIX protocol specification, FIX messages are represented in a raw format using a tag=value syntax, where tags represent field names and values represent the corresponding field values. However, the FIX protocol also supports message encapsulation, which allows FIX messages to be transported in different formats, such as XML or JSON.

The FIX specification provides for three different message formats, which are:

FIX Tag=Value format - This is the traditional raw format for FIX messages, where each field is identified by a numerical tag and its value is specified as a string.

FIXML - FIX Markup Language (FIXML) is an XML-based format that represents FIX messages as XML documents. It provides a more flexible and extensible representation of FIX messages and is commonly used in web-based trading applications.

JSON - JSON (JavaScript Object Notation) is a lightweight, text-based format for data exchange. It can also be used to represent FIX messages in a more human-readable format than raw FIX messages.

In summary, while the traditional FIX message format is represented in a raw format using a tag=value syntax, FIX messages can also be encapsulated in other formats such as FIXML or JSON. However, regardless of the format used, the content and structure of the FIX messages must conform to the FIX protocol specification to ensure interoperability between different trading systems

@uwezukwechibuzor
Copy link
Contributor Author

Research more on how the raw format using a tag=value syntax could be implemented in the query for each message type

@uwezukwechibuzor
Copy link
Contributor Author

This is currently the implemented format(JSON - JSON (JavaScript Object Notation)) on Re

{
"MsgType": "D",
"SenderCompID": "ABC",
"TargetCompID": "DEF",
"MsgSeqNum": 123,
"SendingTime": "2022-04-11T12:34:56.789Z",
"OrderID": "ABC123",
"Symbol": "AAPL",
"Side": "1",
"OrderQty": 100,
"Price": 150.50
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant