Skip to content
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.

Timing out on receipt of large data from RPC call #4

Open
lterry-t opened this issue Sep 14, 2016 · 0 comments
Open

Timing out on receipt of large data from RPC call #4

lterry-t opened this issue Sep 14, 2016 · 0 comments

Comments

@lterry-t
Copy link

(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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant