question

Upvotes
Accepted
301 10 24 33

Enhanced Symbol Lists require Provider support?

Within RFA 8.x, the Enhanced Symbol List functionality states:

"When data is requested along with names on the symbol list, RFA opens the items listed in the symbol list response for the consumer application."

From this, we can clearly see that the RFA API will provide the convenience of opening the items automatically within the symbol list when it returns from the Provider. This is a nice convenience as the RFA client doesn't have to code for this. In fact, a nice diagram is outlined here describing exactly that.

However, for reasons not exactly clear to me, the Provider needs to support this as indicated in the Login Response message (search for SupportEnhancedSymbolList on that page). In fact within this question, part of the answer also explains the Provider has to support this capability i.e.

"Even then not all providers may support the "enhanced" concept of sending all the symbol list constituents from the single request..."

Yet, the description (and diagram) of what an Enhanced Symbol List clearly states the API at the client side will do all the work for you.

Can someone clear up the confusion. Exactly what support does a Provider need to provide for Enhanced Symbol Lists?

treprfarfa-apisymbology
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Upvotes
Accepted
11.3k 25 8 14

The "SupportEnhancedSymbolList" is generated by RFA consumer to indicate that the version of RFA supports the Enhanced Symbol List feature. This means that an RFA8 consumer application always receives SupportEnhancedSymbolList=1 in Login refresh message‘s AttribInfo.Attrib.

With this feature, RFA sends request for items from the symbol list on the consumer application's behalf. If the back end server supports batch feature, RFA will send the item requests as batch. Otherwise, RFA will send the item request as individual request.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Thank you - this makes sense. Yet, I don't know why the documentation states "Provider", not "RFA" when discussing "SupportEnhancedSymbolList". This is the source of confusion.

I think the point here is that if the Provider does not support the Enhanced function then RFA will provide the functionality on the developers behalf.

A Provider (e.g. ADS) could support 'Enhanced Symbol List request' whereby it sends the data for the items in the Symbol List and it would indicate this in the Login response when the consumer connects to it. And if it did support it, then RFA would not need to individually request each item in the list.