Re: [go-nuts] Streaming deflate - can't reliably read chunks as they arrive instead of the entire stream

2016-07-20 Thread Adam Keeton
You're right. It wouldn't have worked without the 0x. However, the test data was being dumped from an existing codebase handling websockets that was already appending that to each message. For reference (and since other people have asked me for it), here's the entire sample code with a lin

Re: [go-nuts] Streaming deflate - can't reliably read chunks as they arrive instead of the entire stream

2016-07-15 Thread Adam Keeton
continue } if err != nil { break } compData.Reset() } Is there a different implementation of deflate that you think I should try? On Thu, Jul 14, 2016 at 9:30 PM, Nigel Tao wrote: > On Fri, Jul 15, 2016 at 9:14 AM, Adam Keeton wrote: > > A

Re: [go-nuts] Streaming deflate - can't reliably read chunks as they arrive instead of the entire stream

2016-07-14 Thread Adam Keeton
> but then it sounds like you're concatenating all of the messages together, I should have mentioned that I reset the websockets buffer after reading from the deflater. A small self-contained example with this code would be tricky with all of the websocket handling stuff in the way. Regardless,