You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.
(Firstly, great module! Aside from this issue, it's working great)
When I initiate an RPC call that returns a large amount of data (>2MB), I get a TimeoutError from the call. I recreated the exact sequence with standard a Autobahn implementation and had no issues. Also, I note the timestamp that the server finishes transmitting the data. For the standard Autobahn implementation, the result is available on the client very soon after the server says it has finished. For the autobahn-sync implementation, nothing happens and the timeout occurs.
I've looked through Autobahn and Twisted's code to see if there is a max transimission size parameter somewhere and I can't seem to figure that out.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
(Firstly, great module! Aside from this issue, it's working great)
When I initiate an RPC call that returns a large amount of data (>2MB), I get a TimeoutError from the call. I recreated the exact sequence with standard a Autobahn implementation and had no issues. Also, I note the timestamp that the server finishes transmitting the data. For the standard Autobahn implementation, the result is available on the client very soon after the server says it has finished. For the autobahn-sync implementation, nothing happens and the timeout occurs.
I've looked through Autobahn and Twisted's code to see if there is a max transimission size parameter somewhere and I can't seem to figure that out.
The text was updated successfully, but these errors were encountered: