Sample doesn't show how to deal with chunked messages about gitter-node-stream

[MadLittleMods]

@webOS101 Pull request welcome!

[webOS101]

Understood... but, I'm actually not sure what the proper way to resolve this is. I resolved it myself by try/catch around a JSON.parse(msg) and building up the chunk if it fails, but that seems horrific. I didn't have time to look for a more elegant solution

[MadLittleMods]

I think you may be able to delimit based on \n

The JSON stream returns messages as JSON objects that are delimited by newline (\n). Space + newline (\n) are sent as periodic "keep-alive" messages to tell clients and NAT firewalls that the connection is still alive during low message volume periods.

https://developer.gitter.im/docs/streaming-api

But you can also look to see if the last character is a }(maybe }\n) as a way to tell it is a full message

---

• ☝️ August 14, 2016 6:04 PM
• ☝️ March 14, 2016 4:22 PM
• ☝️ August 11, 2015 4:27 PM

[webOS101]

There may be some assumptions about whether more than one object can be sent in a single stream that need some testing. I may give it a try to see if I can come up with something robust.