Regarding WebSocket Streaming of NSE Indices

sekharrockz

I noticed that while streaming NSE-Indices instruments, i get 28 bytes of data.

Is there any reason behind sending only 28bytes of data for NSE-indices based instruments.
eg: you can use this token to test: 256265

Kailash

@sekharrockz The index packet doesn't come with a number of fields that accompany other packets, that's why.

sekharrockz

i didt understand your reply.

i can better understand if you can send me a response of this "256265" when you have subscribed it in full mode.

Kailash

@sekharrockz Here's the structure.

// InstrumentToken					0-4
// LastTradedPrice					4-8
// HighPrice						        8-12
// LowPrice							12-16
// OpenPrice						        16-20
// ClosePrice						        20-24
// NetPriceChangeFromClosingPrice	24-28

sekharrockz

Got it..

sekharrockz

Can I know the byte allocation of each one..

sekharrockz

Ok it's already there..

sekharrockz

@Kailash
Don't you think this should be mentioned in your documentation

anupshinde

@sekharrockz Instead of scratching head against the documentation (which is not very clear in this case), just refer the KiteTicker javascript class from the Kite Application app.min.js. It uses the same api. You can then convert it to language that you use.

Or if you want further control, you can extract code from that class specific to decoding the frame - would be obfuscated, but doesn't mater as we can wrap it as a blackbox and it decodes the arraybuffers perfectly.
Example here: http://pastebin.com/XTEN9zSL

Vivek

@sekharrockz @anupshinde We also have python streaming client, you can use it as a reference for parsing. We will update our documentation to include indices parsing.

sekharrockz

@vivek
Thanks. python streaming client, is nice way to get started. Thanks Again.

Vivek

closing the thread.