We curently have a single Client instance that is registered to receive login callback responses via the
loginHandle = ommConsumer.registerClient((EventQueue)null, ommItemIntSpec, client, null);
However my login client is unable to receive callbacks for the Event.OMM_CONNECTION_EVENT.
Question (1) Can the same login Client also register an interest to also receive Connection Events ?
Question (2) Or should we use a different client instance to handle Connection Event callbacks separately ?
Please refer to one of our examples which demonstrate the use of the same client class to handle multiple types of Interest Specifications.
e.g. C++ and C# examples of StarterConsumer use a single Client class to register both Item and Connection interest specs.
You will find the above examples in the Examples\StarterConsumer folder of your RFA SDK.
The choice of whether you use single or different client classes is an implementation choice for you - e.g. separate client classes can make the code more readable if you are not having to process multiple event types within the single class....
One other thing to note - if you are developing a new application and are able to code in C++ then I would recommend the Elektron Message API of the Elektron SDK - much easier to learn, and much less code to implement and maintain etc...