PubSub response parsing on JSON output

[dmvass]

Hi @tidwall! Can you please suggest the proper way for parsing pubsub messages on JSON output, in the telnet messages are not have a length prefix or CRLF.

telnet localhost 9851
Trying ::1...
Connected to localhost.
Escape character is '^]'.
OUTPUT json
$31
{"ok":true,"elapsed":"40.9µs"}
subscribe warehouse
{"ok":true,"command":"subscribe","channel":"warehouse","num":1,"elapsed":"73.7µs"}{"command":"set","group":"5da490312471ae00015fa4a2","detect":"inside","hook":"warehouse","key":"fleet","time":"2019-10-14T16:24:08.9040845Z","id":"bus","object":{"type":"Point","coordinates":[-112.26034343,33.46]}}{"command":"set","group":"5da490312471ae00015fa4a2","detect":"inside","hook":"warehouse","key":"fleet","time":"2019-10-14T16:24:10.0358781Z","id":"bus","object":{"type":"Point","coordinates":[-112.26034343,33.46]}}{"command":"set","group":"5da490312471ae00015fa4a2","detect":"inside","hook":"warehouse","key":"fleet","time":"2019-10-14T16:24:10.7501405Z","id":"bus","object":{"type":"Point","coordinates":[-112.26034343,33.46]}}{"command":"set","group":"5da490312471ae00015fa4a2","detect":"inside","hook":"warehouse","key":"fleet","time":"2019-10-14T16:24:11.4309711Z","id":"bus","object":{"type":"Point","coordinates":[-112.26034343,33.46]}}

[tidwall]

I don't recommend using OUTPUT json with PubSub. All geofence are in JSON already.
It's best to use a standard Redis client. They all support PubSub.

If you must use telnet then simply issuing a SUBSCRIBE warehouse, without the OUTPUT command, will give you a better response.

[dmvass]

Agree with you but why the server provides a different OUTPUT json contract for commands and PubSub?

[tidwall]

I just fixed the bad formatting for JSON PubSub. Thanks for letting me know.