dataDictionary | This repository is the container for the openETCS data | Dictionary library

Some thoughts.

You are making the variable static, which not the same as creating a Singleton. Singleton pattern involves a unique instance that is static, but what you do I would call it make the variable static.

You don't need to make the variable static to grant access from outside. Property with public getter is fine.

Making the variable static in c# means that the property value will be the same in all VectorData instances(if more than one) . Meaking it a class property instead of an instance property, so part of the class template itself.

Regarding your points 1 and 2, the amount of code in a class has no relation with how big your data structures are. Logic or arquitecture will be written according to readability and logic functionality, not to data structures size use.

Point3. Check the usage of scriptable objects in the docs. Large amount of raw data is OK as you have it in a class variable.

Point4 Singleton pattern or making the property static seems overkill to me. To access one class property, public get is fine, or a public variable.

Finally you should not worry about performance due to large amount of data when a class instance is passed around, because class instances are passed by reference, so you are no making any copies of your huge dictionary.

Hope that makes sense :)

You can try something like this. Flattening your dictionary into simple IEnumerable and then batching it according to your batch size.

QF does not automatically do this for you.

You will need to implement your own logic to create the ack message and send it.

And yes, you are correct that you will need to add BN and its fields to your DataDictionary. I would then recommend that you re-generate the QF/j source and rebuild the library so that you can have proper BN message/field classes. (The QF/j documentation should be able to guide you with this.)

Firstly, you are getting below error

Firstly

You should use setCheckUnorderedGroupFields(false) to disable the validation of the ordering in repeating groups. However, this is only a workaround.

I would suggest to approach your counterparty about this because especially in repeating groups the field order is required to follow the message definition, i.e. the order in the data dictionary.

FIX TagValue encoding spec

Field sequence within a repeating group

...

Fields within repeating groups must be specified in the order that the fields are specified in the message definition.

the problem was that in linux Directory.GetFiles is Case Sensitive, so DefaultMessageFactory:LoadLocalDlls() wasn't able to find the local dlls in Linux. I created the pull request in github https://github.com/connamara/quickfixn/pull/663 and with this change it worked perfectly in Linux.

You'll need to import several things to configure a basic API view:

When you click on the map, it triggers a call on :