KX Community

Hi Roni Looks like this changed in 3.6, in 3.5 they seem to encode differently, but the keyed table doesn’t decode properly: q).j.j flip (`col1`col2)!(`a`b`c`d;til 4) "[{\"col1\":\"a\",\"col2\":0},\n {\"col1\":\"b\",\"col2\":1},\n {\"col1\":\"c\",\"...

I believe cryptoq [https://github.com/asatirahul/cryptoq] has been updated with SHA512 support recently, it may now be possible to use it to do your encoding? Jonathon From: personal-kdbplus@googlegroups.com On Behalf Of jakedigitalmarketing@gmail....

So there was a bug in my ws.q library – I didn’t realise that kdb+ already adds a number of WebSocket-related headers to requests to ws:// or wss:// URLs; my library added some of these headers as well, which caused problems on some hosts (I guess a...

Correct URL is wss://www.bitmex.com/realtime Using https://github.com/jonathonmcmurray/ws.q seems to work fine: jmcmurray@homer ~/git/ws.q (master) $ q ws.q KDB+ 3.5 2017.11.30 Copyright (C) 1993-2017 Kx Systems l64/ 8()core 16048MB jmcmurray homer....

I was able to create a very minor modification to json.k that makes it parse these JS objects $ diff js.k json.k 13c13 < c:{$["{"=*x;(`$c's'n#'x)!c'(1+n:x?'":")_'x:d x;"["=*x;.Q.fc[c']d x;q=*x;$[1<+/v x;'`err;"",. x];"a">*x;"F"$x;"n"=*x;0n;"t"=*x]} ...