Comments (4)
A receiver should compare the schema version in the received message header to the version that the decoder was built with.
If the received version is greater than or equal to the decoder's version, then all fields known to the decoder may be parsed.
If the received version is less than the decoder's version (that is, the producer encoder is older than the consumer decoder), then only the fields of the older version may be parsed. This information is available through metadata as "sinceVersion" attribute of a field. If sinceVersion is greater than received schema version, then the field is not available.
How the decoder signals a calling application that a field is unavailable is an implementation detail.
from fix-simple-binary-encoding.
We can state that changes to metadata that do not change wire format are compatible, e.g. change of description or correction to spelling of a name.
from fix-simple-binary-encoding.
Hi Don,
Would you recommend schema version change when need to correct semantic type from String to Int for a field using Int32 binary type (SecurityID in this case)? We didn't find any rules describing rule regarding this type of correction. We don;t see how mismatch of Semantic type in this case may create an issue with decoding.
from fix-simple-binary-encoding.
We discussed a closely related use case in the FIX Orchestra working group ("machine readable rules of engagement"): the FIX datatype (application layer) of SecurityID may be dependent on SecurityIDSource, string in one case or numeric in another. We are making a provision for that in the Orchestra schema.
In my view, change of application layer datatype is a significant change, even if the wire format doesn't change, and therefore, should result in a version bump. However, we should get others' views on this. Rosa, please enter this as a new issue to be considered for any future SBE versions.
from fix-simple-binary-encoding.
Related Issues (20)
- Version 2 XML schema proposal HOT 1
- Invalid character in the v2-0-RC3\resources\xsd\sbe-2.0rc3.xsd HOT 1
- Possibly redundant "description" attrubute in the "semanticAttributes" attributeGroup HOT 5
- Decimal number representation for monetary amounts
- Version 2 RC schema does not allow semanticType on encoding types
- Clarify offset and length related types HOT 5
- How extension mechanism is supposed to work when dimension type is unknown? HOT 7
- Improve variadic-length field specification HOT 1
- Why is nullValue not allowed for required field? HOT 4
- Questions about common field attributes HOT 2
- How unique should message member's `id` be? HOT 3
- Why `symbolicName_t` is limited to 64 chars? HOT 3
- Can enum/set be optional? HOT 2
- Question: Forward compatibility between encoder code and schema version HOT 1
- Can `<field>` override presence of its type? HOT 2
- Schema extension mechanism violation
- SBE 2.0 features in 1.0 spec HOT 1
- Should `ref` use custom offset of the referred type?
- Better version constraints
- Ownership
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fix-simple-binary-encoding.