How to handle page updates decryption using WebSocketAPI ?

guillaume.chatel

Hello,

We are currently implementing the page subscription using WebSocketAPI.

We managed to handle the first response of the page subscription, we now we are blocked with the encrypted page updates.

We wonder what is the best solution for us :

- build our own decoder parser (we would like to implement this one in order to not depend on a third party library).

- reuse a Refinitiv library : (com.reuters.rfa) or (com.thomsonreuters.upa)

Our questions are the below :

- for the first solution : will we be notified if the page encryption is changed ?

- for the second solution : can we use the API ? Will it be maintained ? Will we be also notified once there are some updates on this API?

Regards,

Jonathan Haruni - Refinitiv

Thank you for the example. These are “positioned updates”. They are used in records like this one containing unstructured text to avoid sending the entire text field for small updates. You said you’d prefer to parse these yourself so here is the encoding in JSON:

\u001b[n`text

where

\u001b[

is that literal sequence. You use that to detect this encoding.

n

is a decimal number, one or more digits, representing the starting character within the field for the update, 0 being the leftmost position.

`text

is the backquote character followed by the text to replace the old value.

Example: Using your example above, in ROW80_1 the update says to put "19:11 25NOV20" at position 0. So after the update ROW80_1 will be

"19:11 25NOV20 TULLETT PREBON (AUSTRALIA) PTY LTD AU28812 ASWAP"

The pattern may be repeated in the same update, as you can see in your example in Row 12 where the update replaces a single character at both positions 34 and 43 each with an "8".