Any suggestions for using TREP for a request/response application where the requests are too complex to encapsulate in a RIC? IE the request should carry arbitrarily large structured payload.
The idea is to build a publisher that can be deployed and operated like any other TREP publisher to handle parameterized analytical queries. Mostly snapshot but streaming may be used for some purposes.
Idea 1: Can an OMM REQUEST message field msgKey.name contain arbitrary content? Is there a size limit?
Idea 2: Can an OMM REQUEST message field “Payload” be used for arbitrary purposes? I see in documentation how to use this for specific purposes such as Batch Request under various RDMs. But with existing domains or if you build your own can you load up the Payload of an RSSL_MC_REQUEST with whatever you want? Any examples?
Idea 3: Are private streams with Generic messages a good way to do this? If used, can the ADH’s load balancing features be used to dole out private stream requests to several identical publishers? Does this effectively provide load balancing? Does it do failover too, i.e. if a consumer is connected to a private stream provider that fails will ADH reconnect it to a different one? This would allow the consumers and infrastructure/operations to be handled in familiar ways.
Any different suggestions?