question

Upvotes
Accepted
1 0 0 0

How to simulate RSSL_STREAM_UNSPECIFIED?

How can we simulate receiving the RSSL_STREAM_UNSPECIFIED message? What should the client application behavior be when receiving that message? From this post, https://community.developers.refinitiv.com/questions/46630/rssl-state-message-and-how-do-we-handle-rssl-strea.html, it seems that the correct response is to ignore/not process RSSL_STREAM_UNSPECIFIED. Are there any cases where RSSL_STREAM_UNSPECIFIED should be processed or acted on?

elektronelektron-sdkrrteta-apielektron-transport-api
icon clock
10 |1500

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

Upvote
Accepted
20.3k 73 10 20

Hi @hari

Please see this existing post - as stated it does not require processing.

icon clock
10 |1500

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

Upvotes
1 0 0 0

Thank you. What's the best way to simulate receiving RSSL_STREAM_UNSPECIFIED?

icon clock
10 |1500

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

Upvotes
20.3k 73 10 20

Hi @hari,

Not tried this but I expect you could modify one of the Provider examples (not NIProvider) that are supplied in the ETA subfolder to encode a message in the desired format and publish it.

You could then connect your Consumer directly to your provider and consume it.

icon clock
10 |1500

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

Click below to post an Idea Post Idea