Why does the attrib returned in the RFA login refresh not match features of the connected provider?

Akechi Sato

The attrib in login response of RFA always support
PauseResume, OMMPost, View, and Batch although the connected provider doesn’t
support these features.

ElementList: standard data count = 10
        Entry: 'ApplicationId' -> "256"
        Entry: 'Position' -> "10.42.85.80/net"
        Entry: 'SingleOpen' -> 1
        Entry: 'AllowSuspectData' -> 1
        Entry: 'SupportPauseResume' -> 1
        Entry: 'SupportOptimizedPauseResume' -> 1
        Entry: 'SupportOMMPost' -> 1
        Entry: 'SupportViewRequests' -> 1
        Entry: 'SupportBatchRequests' -> 7
        Entry: 'SupportEnhancedSymbolList' -> 1

Why does RFA return this attrib in the login refresh and how
can I verify whether the provider really supports these features?

Jirapongse

The attrib in the login response received the application is created internally by RFA to indicate the features which are supported by RFA. Except SingleOpen and AllowSuspectData which is controlled by the login request, other features are always supported by RFA C++.

However, if RFA connects to the provider that doesn’t support these features, RFA will report it via RFA Application logger. For example:

(ComponentName) Static: (Severity) Warning: Connection "Connection_RSSL" does not support batch. Batch requests will be converted to individual item requests for this connection.

(ComponentName) Static: (Severity) Warning: Connection "Connection_RSSL" does not support views. View requests will be converted to full item requests for this connection.

(ComponentName) Static: (Severity) Warning: Connection "Connection_RSSL" does not support posting. Posting requests for this connection will not succeed.

(ComponentName) Static: (Severity) Warning: Connection "Connection_RSSL" does not support Pause/Resume. Pause and Resume requests for this connection will be ignored.

(ComponentName) Static: (Severity) Warning: Connection "Connection_RSSL" does not support optimized Pause/Resume. Optimized Pause/Resume requests will be converted to individual item Pause/Resume requests for this connection.

The severity of these logs are Warning so the application can retrieve them by setting the minimum severity of AppLoggerInterestSpec to Warning, Information, or Success.

AppLoggerInterestSpec appLoggerInterestSpec;
appLoggerInterestSpec.setMinSeverity(Success);

Each log will indicate which feature that the connected provider doesn’t support. It also indicates how RFA will handle it. For example, if the item requests use view but the provider doesn’t support view, RFA will be converted to full item requests, as shown below.

Warning: Connection "Connection_RSSL" does not support views. View requests will be converted to full item requests for this connection.