Escape Characters in RTO WebSocket Fields

Nathan.Harris · 2024-11-21T13:16:31+00:00

There was an error rendering this rich post.

When processing page data we see some fields contain escape characters - which we have discovered means Partial Update - so update from character 14.

\u001b[14` 19-Nov-24

I was unable to find any documentation on these escape characters and would like to know if these are the only case or if we should handle others ?

Find more posts tagged with

Accepted answers

All comments

jason.ramchandani01

@Nathan.Harris Thanks for your question - in terms of websockets i think you are covered with just the '/' or '\' characters - this can be the case especially with passing delayed RICs which all have a prefix of '/' eg '/TSLA.O' (which is a 15 min delayed RIC) however i did a quick search on the portal and there are other RDP services which might have issues with other characters - please check here. I hope this can help.

Nathan.Harris

Thanks but I am not sure that answers my question about the ANSI control codes used for partial updates. There's a reference to page data in this JAVA documentation - is there something similar for WebSockets ?

https://developers.lseg.com/en/article-catalog/article/how-to-parse-page-based-data-using-elektron-sdk-java

Jirapongse

@Nathan.Harris

Partial update formats are the same for both Real-Time SDKs and WebSocket API so you can refer to that article.

For example:

The syntax of an intra-field positioning sequence is as follow:

<CSI>n<HPA>

<CSI> is 1B5B. In Websocket, it is \u001b[. 5B is the '[' character.
n is 14
<HPA> is 0x60. In Websocket, it is the '`' character.

Therefore \u001b[14` represent an intra-field positioning sequence.

EXPLORE OUR SITES