RsslMap not sent as encoded

I encode a RsslMap in a particular order, e.g.
912810RN0=TWEB
912810RP5=TWEB
912810RQ3=TWEB
912810RS9=TWEB
I feed this into a value-add payload cache (rsslPayloadEntryApply) and extract (rsslPayloadEntryRetrieve) on each client request.
With RSSL tracing enabled though the ordering is different:
<mapEntry flags="0x0" action="RSSL_MPEA_ADD_ENTRY" key="912810RS9=TWEB" >
</mapEntry>
<mapEntry flags="0x0" action="RSSL_MPEA_ADD_ENTRY" key="912810RP5=TWEB" >
</mapEntry>
<mapEntry flags="0x0" action="RSSL_MPEA_ADD_ENTRY" key="912810RQ3=TWEB" >
</mapEntry>
<mapEntry flags="0x0" action="RSSL_MPEA_ADD_ENTRY" key="912810RN0=TWEB" >
</mapEntry>
Please explain? Is it possible to send out an ordered symbol list? This looks like walking through a red-black tree underlying a "map" implementation. Is should be possible to publish an ordered list say through an RsslVector instead of a RsslMap.
On Elektron, similarly the symbol list .AV.HK for example does not match the ordering of the chain .AV.HK, consuming after hours.
This implies the ordering is an artifact of the TREP payload cache and thus cannot be avoided.
Best Answer
-
It is Value-Add cache that re-order the map content.
The data model for symbol lists and maps is already
chosen and I believe it can’t be changed at this point. Besides, keeping these sorted denotes
we effectively have to refresh the entire record everytime the ranking
changes.You should consider requesting to extend the exist symbol list map data model to allow for ranking such that client side APIs will be able to sort all symbol lists reliably.
0
Answers
-
Hi Steven,
I have run a quick test using rsslProvider example and it give a correct order.
What's your setup?
Do you connect to ADH with cache enable (cachelocation = ssl)?
Have you tried enable UPA tracing on your provider app and see if the order is correct?
0 -
UPA 8.0.0.L1 provider with Value-Add Cache and UPA tracing enabled on a client connection.
0 -
A RsslVector is required for an ordered list, however the RDM guide mandates only use of RsslMap for the Symbol List domain.
Enhancement request posted to product management for feedback.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛