Re: Maximum AllWatcher frame size?

Wouldn't that feel like a breach of contract where the first response is supposed to get you in sync with the system? I could definitely see doing a different code path for the first response because you know there aren't any objects you have to compare against, etc. Or because you can reasonably

Re: Maximum AllWatcher frame size?

On 14 June 2017 at 17:14, Cory Johns wrote: > So, I'm not sure if this resolves the issue. The python websockets library > supports fragmented messages but I think that is separate from the maximum > message size that it's enforcing. I think that maximum is for the

Re: Maximum AllWatcher frame size?

So, I'm not sure if this resolves the issue. The python websockets library supports fragmented messages but I think that is separate from the maximum message size that it's enforcing. I think that maximum is for the final payload, which would be the entire AllWatcher JSON response. If the

Re: Maximum AllWatcher frame size?

Do we know what size the gorilla/websocket library uses for automatic chunking? On Wed, Jun 14, 2017 at 11:35 AM, John Meinel wrote: > In 2.1 we did not chunk, in 2.2 we switch to gorilla/websocket which does > support chunking into frames. I don't think we do any

Re: Maximum AllWatcher frame size?

In 2.1 we did not chunk, in 2.2 we switch to gorilla/websocket which does support chunking into frames. I don't think we do any internal "well that would be too much information so we wont send it all". John =:-> On Wed, Jun 14, 2017 at 7:11 PM, Cory Johns wrote: >